Troubleshooting - Automobilista 2

C'mon, how you gonna race for 3hrs without chaging tyres and refueling? That would be a yes, pitstop refueling enabled, if that's the question.

Only custom AI and liveries exist in my install, no mod cars or tracks.

Not tried race weekend. Will try a vanilla 3hr LMP multiclass style race weekend later this week, see if it works... Then configure some custom AI, test, and finally put all that in a championship, should things work...

If I still get the crashes, guess I'll have to erase everything in the documents folder and install and start again fresh.

Sorry I can't help the sarcasm, I know you are trying to help. On a side note Rieza seems to expect expert industry standard testers to reply in bug reports/AI/physics discussion threads when in fact forum users are mostly just paying customers trying to help you folks iron out issues and bugs in the game. It is done out of passion and willingness a to help. We all would like the best experience possible. Not every one has the time and dedication for such detail, but we can highlight and point you in the right direction. I don't think you can realistically expect much more. Sure you can ask, but don't expect everyone to give all the details you need. That's what your testing team is for! Customers expect the advertised features of your software to be functional at least. High expectations come from the passion Reiza put into the game, and disappointment leads to frustration. Nothing personal, simply clarification.

 

So race weekend, lmdh, lmp2 2005, gt3 gen2. Vanilla, save John Ellis NaMeS and some deleted entries to give a custom grid. 12 lmdh 2x each car (12 total), gt3 gen 2 again 2x each car (16 total). All lmp2 2005 one of which I drove to give 16 cars. 43 opponents total. Game crashed to desktop in practice session at Road America at approx 1hr 15 into a 2hr session. Just entering the pit lane slip road at the time, not in pit lane. No bugslat appeared.

Tyre wear and fuel authentic, refuelling enabled. Limited setup off. Full Damage, medium.

 

Guys could anyone help here please.
Everytime I'm rebooting my laptop, my g29 stops showing any movement in GHUB. It is getting detected but no movement of wheels or pedals in ghub. In joy.cpl it is getting recognised but nothing on ghub.

 

Hello folks, I posted about this in another thread but haven't had a reply as yet there so thought I'd share here, too. Moderators, please remove if not appropriate.

General & Small Questions-topic

TL;DR is that the HUD isn't laid out properly on my 2D screen when using VR, making content capture difficult as the audience doesn't see it how I do, and attempts to move the elements to different locations on the screen don't work as the elements are misaligned versus where they actually appear. Any help would be massively appreciated!

 

I don't have an immediate solution for you, but I've encountered that misalignment as well in the past when editing the HUD in VR. The issue in my case was that the screen resolution set in game (which in VR is for the 'monitor view') was not identical to my desktop resolution in Windows, ie. I had set in game to 720p to save some resources, while the screen itself in Windows was set to 4K. Changing both of them to 1080p resolved the misalignment for me. Maybe this helps...

 

I'll give this a try, but I think I'd seen something similar written elsewhere and had made sure to have both resolutions the same, but I'll have a look!

 

Sorry for the late reply; sometimes I just don't have the time. Well, it seems that, for now, the stuttering and FPS drops at Sebring have disappeared. There's always a little stutter in some area or sector of the track, but it's mild or imperceptible—maybe once or twice per race—and it's even gone at other tracks like Road America. As for my current hardware, I’m using an RX 7600 GPU, Linux Mint 22.3 as my distribution, the Cinnamon desktop environment, the default X11 graphics server, and kernel 7.0.0-28. I’m using Steam’s default compatibility layer setting, which is Proton Experimental, and it works well. A day or two after I reported the issue, it seems to have been fixed; I don’t know if you released a patch or update, but for now it’s running normally, and I know that sometimes the camera movement can be even more confusing. In my case, since I race with the internal camera—the cockpit view, as it should be—the FPS drop was visible in the Steam graph and, consequently, was reflected on the monitor.