AMS1 working in VR

use a program called joy to key it worked for me for centre vr

 

Anyone having success with the Oculus Quest 2 ? Thinking of ordering one to play AMS 1 in VR. I'm looking for the best VR headset for racing. Any advise ?

 

best VR headset for racing is probably the Valve Index.

Do any Rift-S users have time to help us test? We have a some different maths approaches that all work perfectly on our headsets but we really need to know if there are differences on the Rift S

 

So no one else having issues with their CV1?
The game will exit for me straight after starting up AMS.
Is there any logs I can produce to see what the issue might be?

 

reverb g2

 

@Neawoulf has one and has posted in this thread, in case you missed it, page 4

 

@Bjarne Hansen @Eduardo which WMR headsets do you guys have? Interested in AMS VR at as cheap a price point as possible

 

Keep in mind that you really need to have a beefy pc to enjoy AMS1 in VR. It's not that it runs without flaws just because it's somewhat old. Similar to Raceroom in VR imo.

 

Thanks, I do already, GTX 1060 6GB with a 4670K, I have had a Rift before to use with rF2 and AC. I loved VR, however not enough to overlook those sims' flaws, so I sold the Rift. The immersion was great, but if the FFB is poor (AC) or the AI don't overtake (rF2) that immersion doesn't last long.
I only play AMS, so now I'm ready to dive back into VR.

 

Yes, Hud turned off in game will turn of in .ini too and come back

 

First generation WMR Lenovo Explore. Main downside are the LCD panel, very sharp display but a little bland in colors.

 

Thanks a lot Bjarne!
The blandness I guess could be improved by using a more vivid SweetFX filter?
I think I'll go for a used Lenovo Explorer then..

 

Deleting d3d9_2.dll in AMS root looks to have eliminated the freezing issue!
Still having HUD off in both game and CrewChiefVR.ini but believe the d3d9_2.dll was the issue

 

anyone having the issue once you get in the car the picture is dbld and overlapped

 

Probably helpful if you give as many details as possible, such as the headset you are using..

 

Hi folks,

We've been trying to track down the rendering issues some users are reporting but it's difficult and slow going. We've implemented 2 separate render transform approaches in the latest version, which you can toggle between to see the effect. The default approach works really well on our headsets but the alternate approach is worth trying if you're having tracking / distortion / convergence issues. The details are in the readme file.

Please re-download the package from http://crewchief.isnais.de/AMS_VR_beta.zip and replace the CrewChiefVR.dll and CrewChiefVR.ini files with the new ones.

Feedback is really important here - especially from Rift users.

Ta

 

Hi all, cv1 user here. First of all congrats for a great job. In my case I have no freezes when press "escape", I have to start the game with steamvr closed and then it works, the visual quality is good but the whole scene turns and deforms when I turn my head, and I see the track less wide than rfactor 2 vr for example. Thanks a lot.
PS. I've used both crewchiefvr.ini and the results are identical.

 

I'd like adding that it's absolutely playable and enjoyable anyway

 

to be clear, you tried using both rendering modes (and restarting the game between changes) and there's no difference? Does holding num-pad-0 down make any difference?

[edit]

Something I've not made particularly clear is that this VR stuff will only work in cockpit view. Chase view, bonnet view etc etc won't work

 

I am having the same problem that I thought had been solved yesterday. I reinstalled and ran several races yesterday and all seemed well. Then after loading F-Ultimate with custom skins from RD it crashed on trying to start the track session and nothing would make it work. As soon as the > is clicked to start the session after the track has loaded it immediately crashes to the Steam VR homeroom. I have tried running AMS from the executable and from Steam both. Steam method has always worked when it works and the shortcut, run as admin or not makes no difference. Reinstalling AMS and running both new beta and old doesn't seem to matter. Running on Win 10 X64Pro, 24 gigs 3600 ram, Intel I7-6700k, Samsung Odyssey + , RTX 2060, all drives NVME or SSD Samsungs.
The event viewer log shows:
Faulting application name: AMS.exe, version: 2.0.0.0, time stamp: 0x5d9b3d3b
Faulting module name: ntdll.dll, version: 10.0.19041.610, time stamp: 0xd49544eb
Exception code: 0xc0000005
Fault offset: 0x000489dd
Faulting process id: 0xad4
Faulting application start time: 0x01d6cc02b50da704
Faulting application path: F:\Games\steamapps\common\Automobilista\AMS.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d3d17af1-b68b-41e3-b52e-d56c8862730e
Faulting package full name:
Faulting package-relative application ID:
Any suggestions would be appreciated. It is awesome when it runs, just can't figure why it is so intermittent.