Bottebeitel

just this weekend I encounterd the same issue too. Inside the controls option the button bind is being recognized but it does work in the jet. Did it eventually got fixed with you?

So i was experiencing similar problems as described above. running a fairly powerful system with an i7-14700K/ 64GB RAM 3600mHz/ RTX4080/ nvme SSD. and the funny thing was that in MT i could easily play a smooth game in VR everything on high or ultra high and get steady 55fps on Syria map and even higher fps on less taxing maps. however 2d was a mess, just unplayable, fps all over the place and these so called frame timings where just spiking up and down as well. tried all as explained earlier in the thread but that did not change anything for me. Next i tried 2d on the ST app, super smooth nothing wrong whatsoever. so why was this occurring then in 2d MT? I noticed in armoury crate that my cpu was constantly running at max speed never dropping back to idle speeds even when not running an app. So i thought why not revert to factory CPU settings as I was currently running an AI overclock. So I reverted to default settings and could see the CPU was running idle speeds as expected. opened up DCS in 2d MT. All smooth getting 200-300fps on PG map and 150-200fps on Syria map. No jittery frame timings anymore. Simply steady and smooth gameplay. What did I do: reverted from AI overclock to default CPU speeds. Changed the PC power plan from high performance back to balanced performance. Good luck all!

Anything known about the status of the sar server? It was really a lot fun, maybe the developers can share the mission file with a big group like 4YA or TDCS

so yeah, there is an issue with the vr position of cpg when in VR with the G2. Indeed not in the center of the seat and the tilt of the vr position is also not in line with the TADS. It takes roughly 5-10 minutes every time i fly to change the cockpit camera angles and the the tilt angle. When done i am able to properly boresight and accurately aim with the TADS. I strongly hope that ED will acknowledge the issue and comes up with a solution.

So, now a few weeks later since my last posting about a disfunctioning Orion base and stick. I have in dialog with winwing via their chat function and, although it took some two weeks of back and forth chatting/mailing because of the time difference and daily life/work, we got to solution. So they asked me to do all kind of tests in Simappro and provide video's of it, opening the base and reconnecting the different wires. Eventually it came to Winwing sending me a new motherboard and HAL sensor. Changing the latter solved the issue and the stick and base work excellent again. Sometimes it is a bit of a challenge in the communication with them because English is not their mother tongue nor is it my native language, but we always were able to understand each other in the end. They also showed to be very patient with me as at times I worried so much about my purchase that I wanted to press on with my ideas. But then they convinced me of the purpose of their reasoning and so we got along to find a solution. All in all, you will be assisted by their personnel and we managed to solve the issue. Kudo's to Winwing and reach out to them if you are in need.

Just received the new f16ex stick to fit onto the Orion base. However after swapping it with f18 stick, the SimappPro required me to perform a firmware update. After this updat on the Orion base the stick never worked. It indicates at the test display that it is at it's far left corner and odes not calibrate properly anymore. After following the suggestion of adjusting the config.sjon file no improvements either. Now not the f18 stick nor the f16 stick are working anymore. Anyone else with this problem? It looks like a software glitch.

I just got the order paid and will soon be shipped. Looking forward for the f16ex stick. Ordered at 12 march.

Maybe you could take a look at the z-axis accessory for the stick. That might get you where you want to be without having to buy rudder pedals

I use it for f18, a-10, spitfire, mustang, uh-1, mi-8, ah-64. And works just fine for all of them. Just think thoroughly on how to map you buttons and axis and the range of motion of the throttle handles is more than enough. it is really, as you stated , a jack of all trades

Dear @WINWING, I made my order at 12 March, and still no indication of when I can expect it to be shipped. In the mean time you are adding more stuff for sale however nothing can be shipped as of this date. There will most likely be production/transportation things going on that have no idea of. But still it feels wrong. Please be more specific on delivery terms and dates. I would love to recommend your products as they are of good quality but I am hesistant to do so because of the lack of openness with regard to the delivery proces. Please get on top of your customer game as of now. Kind regards

Thanks. That’s a smart move for the time being.

So the problem lies not with how the TADS is viewed but that the alignment of the CPG HMD is off and this results in targeting with it is also off. I hope ED can correct this in future hot fixes

I do use the IPD setting. I have it set at 55. Never thought it might be a problem. I can try changing the setting. You also asked me what headset I use. It is a G2, and I use right eye rendering. What struck me is that your screen shot from the CPG seat looks quite different than mine. You look indeed positioned in line with boresight lens. Whereas with me, it is to my right.

I think it is hard to see because it's a screen shot taken from the VR environment. But I am positioned left of the seats' centerline. Despite using the VR centering option. In the pilots' seat it's all okay.

nothing left in the config file