Hi, first post here. Congratulations on the game it is amazing and I'm really enjoying it so far. First some background: Windows 10Home- 20H2 fully updated. Latest NVIDIA Drivers. Just formatted and fully updated. PC: i7-10700k-RTX3080-32GB DDR4 @3.6GHZ- NVME STORAGE-850w PSU. Displays: Samsung 49" Ultrawide and HP-Reverb G2. T300RS-Fanatec Clubsport V3 pedals-TH8A Shifter-Arduino Handbrake Next Level Racing Motion Platform V3 and 2 BodyShakers. The game runs great in VR unless I try to use motion and tactile feedback, if the Shared Memory is set to PC2 (with UDP in any value other than 0), which is necesary for the motion platform and body shakers to work (both motion and tactile feedback are provided by Platform Manager - ForceSeatPM - Motion Systems) the game crashes, the image freezes and kicks me out of the game. The system has generated several bugsplat reports which I have submitted. I formatted the PC and the problem persists. I love playing the game in VR but it feels incomplete without motion and tactile feedback. Could you please check whether there's a problem with shared memory?, I will ask in the MOtion Systems discord as well in case it is linked to their software, but I have checked and it is only when shared memory is enabled that the game crashes, otherwise I can play in VR perfectly well. Thank you in advance for your support. Mattforum
Does it also crash with UDP set to 9? FYI a value of 9 means network packets with telemetry info are sent every 9 frames so the value should be adjusted as per your FPS. What is your FPS?
Hi, Thanks for your response. I am getting 90fps (89,9 average over a 10minute race) with 100 Steam SS. I never had this problem with Project Cars2 back in the day and now it happens with AMS2 and PC2 only, not with AC/ACC/Dirt Rally... it's very strange.
Well if it didn't do that on pC2 before but now it does, considering the game didn't update in a couple years, I'd say it is either a OS update, a network card update or a software update for the program you use that causes the issue. Or some setting that was modified in your software.
I have a similar system to yours (G2, Next Level v3), but no body shakers. I have run VR and motion for more than a year now, never had any crashes or problems, so there must be something about your specific setup. I have shared memory setup like this:
Thank you very much for your input. Will try your settings later. Yesterday I did something differently and managed to get it working, for a while, until it crashed again. Rather than using the Tactile Feedback provided by the Motion Systems Software, I re-installed SimCommander 4 and used it instead to drive my shakers. But eventually it crashed as well. I am starting to think that it has to do with the latest windows 10 update (20H2) and that it broke something with regards to shared memory and audo devices. What is puzzling is that other driving games besides AMS2 and PC2 do not suffer from this problem, maybe they handle telemetry data differently.
This did the trick, the game no longer crashes and motion and tactile feedback work well. However the G2 is proving to be unreliable and sometimes SteamVR/WMR portal crash and "kick me out of the headset" which is most annoying... But at least this is an improvement. Thank you very much for your advice.
Hi Mate, I am curious how you can get 90fps with steamVR set to 100% as the resolution per eye. Are your in game settings very low? care to share them? also provide the your steamVR resolution per application res for AMS2. Cheers mate
Hi BNR!. Sorry for not replying earlier. I have (if memory serves me well) quite a number of settings on the low apart from textures (high), AA: (Medium), Anisotropic Filtering (16x), Car detail (high), Track detail (medium), Shadows (low), Grass (off) , particles (low/low). I should have clarified that I have my General SteamVR SS set at 80% and it is in-game that I keep that unchanged (thus 100%... of the General 80%). It is still looks and runs very good in my G2. My 3080 is OC'd @2.100 and runs quite cool (never above 70ยบ) so your system should be fairly close since I don't think that CPU would make much of a difference (my Ram specs and NVme are nearly identical).
Hi there! can someone explain how those options really works? and how affect info that the dashboards and telemetry receive? Can reiza confirm if the UDP version protocol on PC2 is updated and finished or is laggy and bugged and it is necesary to use PC1 protocol? In shared memory its better to use PC1 or PC2? for use for example simhub or second monitor. Thank you!
I have a different motion rig and using simtools. The way I solved my intermittent share memory issues (partial motion or haptic feedback stoppped, etc...) was to launch AMS2, start the Test day/Single Player/MP etc... then once I'm in the pit and the telemetry has started to be sent by the game, then I used ALT-TAB, open simtools and sim racing studio. Then I have no issues. It seems the order of running the software matters, perhaps that is your issue as well since they appear to fight over priority or control.
since when does Platform Manager need UDP with Madness Engine Games? I use it with SM: PC2 and UDP: deactivated since years.
