A10C does not reach Take off speed at Batumi in VR, fine in 2D screen

[Bob556a]

so not sure how to describe this but I use VR MT in DCS but recently the A10C takes a lot of time and needs a lot more runway to get to Takeoff Speed. 

I created a simple free flight runway takeoff at Batumi and then run the mission firstly in VR,  MT OpenXR , VR single thread, Open XR and then just on the monitor 2D,, what I  noticed was:\

it takes a lot more throttle to taxi in VR MT as opposed to, VR Single thread and 2D,   as I ran out of runway before being able to takeoff.

Both VR Single Thread or normal VR and 2D (monitor) all was what I considered normal was able to take off in about 50% of the runway length.

Now I also noticed I needed to reach in excess of 130 knots to take off,,

Now all controls are identical,, same mission same HOTAS so any ideas out there?

Now for clarity my system is

Intel 13900KF processor
RTX 4090
Corsair RAM (128Gb)
MSI MEG      Z790 Ace Motherboard
Thrustmaster HOTAS Warthog and pendulum pedals
Game has its own SSD (2TB) Samsung 990 

 

[Flappie]

Please attach two tracks: one in VR and one in 2D. We'll be able to compare and maybe understand what happens.

[Lange_666]

I saw the tittle of the post, read it and thought... let's have a go.

For me there is no difference in take-off distance between 2D or VR both ST and MT (tried the A-10C first, then a few others).

(latest OB version)

[MAXsenna]

Double check if you have "sync with HOTAS at mission start" enabled, in case controls are not set correctly. Also that relevant axis are set as sliders.

Cheers!

Sent from my SM-A536B using Tapatalk

[Bob556a]

ok so I found the issue,,, For some reason in MT the Thustmaster TPR Pendular pedals driver was holding the brakes on at about 20% in MT,, It did not occur in Standard VR and or 2D... I removed the drivers and just stayed with the Microsoft USB controller Driver for the pedals and all is well.... Not entirely sure how MT affects this driver but seems totally strange to me.. 

I guess the point is the issue is resolved... If Flappie you still want the two tracks can reinstall and do them for you if that is going to contribute to the development of this software. 

Thanks MAXSenna checked this setting and it was not flagged so have done this now.

Bob 

[Lange_666]

8 minutes ago, Bob556a said:

Thanks MAXSenna checked this setting and it was not flagged so have done this now.

It's best not to have it enabled to avoid issues when entering a mission. It can start with the values of the previous flight until you touch any of the controls. Only then they sync to your current mission.

Also, your controls setup is shared between ST and MT. If you set "sync with HOTAS at mission start" in ST it will also be set in MT and vice versa.

[Flappie]

46 minutes ago, Bob556a said:

I guess the point is the issue is resolved... If Flappie you still want the two tracks can reinstall and do them for you if that is going to contribute to the development of this software.

No, it's OK. I needed the tracks to check your axes (RCtrl + Enter) because I had the feeling it was about controls.

MT and ST are supposed to share the same Saved Games folder, so yes, your issue is unexpected. I'm not sure how to explain it. Unless you modified some files in the MT bin folder? (DCS World.../bin-mt/)

[MAXsenna]

It's best not to have it enabled to avoid issues when entering a mission. It can start with the values of the previous flight until you touch any of the controls. Only then they sync to your current mission.
Also, your controls setup is shared between ST and MT. If you set "sync with HOTAS at mission start" in ST it will also be set in MT and vice versa.

My point was that if it was checked, it could potentially lead to problems, unless one's aware.

Sent from my SM-A536B using Tapatalk

[Ephedrin]

vor 20 Stunden schrieb Flappie:

No, it's OK. I needed the tracks to check your axes (RCtrl + Enter) because I had the feeling it was about controls.

Maybe a suggestion to make it simpler for everyone: just formulate your assumption and recommend to check the axes instead of asking for tracks which takes a significant amount of time compared to a simple check advice. Keep in mind that 2D and VR requires changes outside the sim, restart, possibly different settings inside the sim etc.. Tracks are helpful if it becomes complicated, but really not if it‘s just to confirm a suspicion ^^

[Flappie]

I don't know this hassle, for I don't use VR at all.

[draconus]

On 10/20/2023 at 5:33 AM, Ephedrin said:

Keep in mind that 2D and VR requires changes outside the sim, restart, possibly different settings inside the sim etc..

No, saving a track is one click after quiting the mission, no matter VR or not.

[Ephedrin]

Am 27.10.2023 um 10:32 schrieb draconus:

No, saving a track is one click after quiting the mission, no matter VR or not.

That was not the point.

 

you need to fly it twice, in this case with a totally different setup, complete waste of time like in sooo many occasions here.. Then the receiving end needs to watch it, just to confirm the gear lever wasn't down... or the axes didn't work. That's completely pointless, just share your assumption and the problem would be solved.

[draconus]

1 hour ago, Ephedrin said:

you need to fly it twice

What? Why?

[silverdevil]

3 hours ago, Ephedrin said:

That was not the point.

 

you need to fly it twice, in this case with a totally different setup, complete waste of time like in sooo many occasions here.. Then the receiving end needs to watch it, just to confirm the gear lever wasn't down... or the axes didn't work. That's completely pointless, just share your assumption and the problem would be solved.

checking all the surfaces IRL is a thing. one cannot assume they are working. perfect example was a recent crash where the crew did not perform a checklist and the controls were locked. takeoff did not work that well.