Raycast Sensor Availability in Isaacsim Newton

[KEYL-PH]

Is there a new version of newton where the raycast sensor can be used or will the next update of isaacsim (newton physics) include a raycast sensor?

[Kxrma47]

Raycast support is already present on the current IsaacSim main branch for the Newton path. The implementation includes the experimental physics Raycast authoring class and RaycastSensor runtime class, while the Newton stage-update code handles raycast requests. See raycast.py and stage_update_functions.py. In a build containing those extensions, enable isaacsim.sensors.experimental.physics; for packaged releases, check that those files are included because main-branch availability does not guarantee an older binary build contains them.

[KEYL-PH]

I did try this already and the problem is the raycast sensor laser are phasing through object and reading max range depths under Newton Physics. When using Physx, they work normally.

[Kxrma47]

You're right—my earlier reply established that the API is present, but not that Newton's ray queries are working correctly.

This exact Isaac Sim 6.0.1 behavior is now tracked in issue #802: the official raycast example passes through colliders under Newton and the sensor reports maximum-range readings, while PhysX works. The issue is still open and assigned to the sensors team. The raycast documentation defines maxRange as the value returned when a ray misses, so this indicates that Newton reported no hit; it is not evidence of an uninitialized sensor.

There is no verified Newton-side configuration fix at present. The reliable workaround is to use PhysX for this workflow and switch before starting the simulation:

from isaacsim.core.simulation_manager import SimulationManager

if not SimulationManager.switch_physics_engine("physx"):
    raise RuntimeError("Failed to activate PhysX")

Isaac Sim's engine-switching documentation confirms that only one engine can be active and the switch must happen before simulation starts. If Newton dynamics are required, I would not use these raycast readings for obstacle or safety logic until #802 is fixed.

[PeterL-NV]

Let's close this and move the discussion to #802 if you have any inputs.