Skip to content

[Toolkit bug]: lights can only be moved from certain camera position in the toolkit #1063

Closed as not planned

Description

@capybarych

Contact Details (Optional)

No response

Describe the bug

Lights can only be moved from certain camera position in the toolkit, this happens randomly and you can't really reproduce it. It's a very annoying thing because it fixes only with toolkit relaunch and this bug happens almost every toolkit new launch after some time. This bug also was a thing a year or so already

How do you reproduce the bug?

  1. You can't reproduce it since it happens randomly, but for me the bug happens almost every new toolkit launch after some time

What is the expected behavior?

Lights moving should be fixed so you could move them from any camera position

Version

1.5.2.0

Logs

No response

Capture and Project Files

No response

Media

I somehow can't upload the vid but here's the yt link https://www.youtube.com/watch?v=E88DYgIsQao

Activity

  1. nxkb commented on Jul 6, 2026

    @nxkb
    Collaborator

    Hi @capybarych, thanks for filing.

    Are you able to provide the kit logs from a session where this has started happening. ("Show Logs" button on the homescreen) If we get those we might be able to understand why its happening without a reproduction case. Also, If you do notice any steps or projects where this happens that would also be helpful.

  2. capybarych commented on Jul 6, 2026

    @capybarych
    Author

    Hi @nxkb. Heres the log, i got that bug at the end and then closed the project to get the log. Theres no steps to get this bug tbh, it happens to me when i place lights always and im currenly working on l4d2 lighting up all maps so its very annoying. Someone in the rtx remix discord said "i suspect sometimes this occurs if some invisible geometry is between the camera and the light gizmo, or if the light gizmo is too close to the camera and inside the nearclip plane" tho, but as you can see theres nothing but light in the open space in the vid i attached

    kit_20260707_014419.log

  3. nxkb commented on Jul 7, 2026

    @nxkb
    Collaborator

    @capybarych Thanks for the logs, very helpful in ruling some things out, though there's still not a perfect smoking gun. 2 more thoughts:

    • Do you have light manipulator visiblility turned off here? or are they just small?
    • About how long does it take for a session to become corrupt? and does it happen faster if you do many transform operations or lighting changes?
  4. capybarych commented on Jul 9, 2026

    @capybarych
    Author

    @nxkb idk why github didn notify me your message, but anyway, what is light manipulator? It happens faster when im just moving lights and creating new ones. Have you tried to recreate this bug on your end tho?

  5. nxkb commented on Jul 9, 2026

    @nxkb
    Collaborator

    @capybarych oh I just mean the yellow light shaping controls that you can turn on and off here:

    Image

    I have tried to reproduce on my side... but no luck yet. The transform controls work from all angles for me :/

  6. capybarych commented on Jul 10, 2026

    @capybarych
    Author

    @nxkb oh yeah i have this enabled

    Image

    Thats unfortunate. Xorxor4d, if you know him, told me that he had this bug in nfs carbon sometimes. I dont know if its game specific?

  7. added
    kit-sdkFeature or bug will need to be added or resolved in the upstream Omniverse Kit SDK.
    and removed on Jul 13, 2026
  8. nxkb commented on Aug 3, 2026

    @nxkb
    Collaborator

    @capybarych two more things for you to try:

    • try the latest (we just updated the kit sdk which might help with the buggy transform manipulators)
    • see if the issue still reproduces when light manipulators are not enabled (possibly this is blocking the ray check for selecting the xform)
  9. NV-LL commented on Aug 17, 2026

    @NV-LL
    Collaborator

    Hey @capybarych - checking in to see if you've been able to try the suggestions in the previous comment. We'd also like to inform you of our stale ticket policy, specifically that this ticket will be closed as 'went stale' if it does not receive a response in the next 2 weeks. Thanks!

  10. added
    went-staleNo response after more information was requested
    on Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingkit-sdkFeature or bug will need to be added or resolved in the upstream Omniverse Kit SDK.toolkitRTX Remix applicationwent-staleNo response after more information was requested

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions