You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're working with the "Coupled Simulator for Research on Driver-Pedestrian Interactions" on Windows 11 systems and are facing performance challenges. This is consistent across a high-spec workstation and a laptop.
In Keyboard Mode (covering Driver, Automated Passenger, and Pedestrian modes), the FPS averages 20-25.
Outside the city scene, FPS increases to around 50 but suffers from noticeable lag spikes.
The issue is replicated on both workstation and laptop setups.
Notably, the simulation loads 20 million tris and 30 million verts in a stationary state, which appears unusually high.
We encounter this FPS even after building the sim. The FPS in Unity Editor is 4-5 fps slower.
For context, the same simulation on a MacBook yields approximately 40 FPS in the city area and 200 FPS outside the city.
Given these details, we're curious if there are established performance benchmarks for the simulator on Windows 11 systems, or if similar issues have been documented before. Are the high counts of tris and verts typical for this simulation? Insights on optimizing these aspects or suggestions for setting adjustments would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Hey there,
We're working with the "Coupled Simulator for Research on Driver-Pedestrian Interactions" on Windows 11 systems and are facing performance challenges. This is consistent across a high-spec workstation and a laptop.
System Specifications:
Performance Issue:
Given these details, we're curious if there are established performance benchmarks for the simulator on Windows 11 systems, or if similar issues have been documented before. Are the high counts of tris and verts typical for this simulation? Insights on optimizing these aspects or suggestions for setting adjustments would be greatly appreciated.
The text was updated successfully, but these errors were encountered: