All Activity

I made a macro for Notepad++ to edit all the declare_kneeboard_device files so that after each DCS Update, it will reduce your workload. Two things to note: 1. Edit the folder location for your main DCS installation folder on Line 19. 2. Copy & paste Lines 14 - 23 into the existing shortcuts.xml file for Notepad++. It can be found here: C:\Users\UserName\AppData\Roaming\Notepad++ 3. These basic instructions are also found inside the XML file. shortcuts.xml

Ok. That assumes a cold and dark scenario and yes, you would be correct in that case it could be, easily user error... But in a hot start it would perfectly aligned so an incorrect alignment procedure wouldn't be a factor, right? I'll try to add a track / screenshot later today or tomorrow: Hot start, on the ground, looking at a well define object.

This doesnt really add to anything but I do find 4ya servers really task a system at least in my case. I tune my VR/DCS on their Syria USA server. If I can get decent performance, there I'm pretty well golden everywhere else J

Hello! After some time not having it installed I just reinstalled the NS430 for the MiG29... but it does not appear in the cockpit. I created a mission with in ME with NS430 activated. It is checked for all available modules in Special options. It also does not appear in the Mi8 cockpit. Thank you

wip

@WINWING @WinwingTech Please add support for the rest of the DCS modules you haven't so far. Last one you added was F4-E on 1.14.9 patch. Ill make a list of the DCS official modules that dont have support for vibration and key bind profiles as I know for sure still need support on SimAppPro: - MB-339 - F4U-1D Corsair - F-5E Flaming Cliffs 2024 - F-86F Flaming Cliffs 2024 - MIG-29 Flaming Cliffs 2024 (All variants MIG-29A, MIG-29S) - New MIG-29A Fulcrum full fidelity - Su-25A (SimAppPro only have Su-25T variant) - MIG-15 Flaming Cliffs 2024 - MIG-19 Flaming Cliffs 2024 If anyone know any other module I need to add here for Winwing SimAppPro please LMK

At minimum we can take a look at the F1 view and alignment procedure being done. The problem is when we test on our various VR devices we are unable to reproduce, we are happy to keep trying and looking for clues however.

Honest question: Can you determine from a track file where the HMD is pointing to? Or where the center of the physical headset is pointing to? If so, we could setup a mission, look to a particular object (head level and object 'centered' in the line of vision ) so you can grab something useful from the track file. I think this has been done with screenshot, but if that helps you somehow, I can do it.

Очень смешно. Куда определить большое количество хорошо летающих на нем игроков? Это уже по серверам видно давно. Чудовищ надо изгонять…

Hi, please let us know your system spec and your connect speed and internet setup. If you can post a dcs log from a session where it happens it may also help. thank you

was on 4YA me and buddy in separate tomcats tried to tank from MPRS but it was next to impossible due to rubber banding in multiplayer we both experienced. a tiny bit less when i flew away and have one ship tank, but still rubberbanding also after my buddy lost fuel, my buddy hopped in as RIO and we both saw rubber banding from my plane. i went to ask in 4YA discord if it was server, but guys say its happening in many servers..

Thanks for the correction

It is possible to get into a deadly embrace with the Taxi at the beginning between you and Blade, if you signal to Taxi at the same time Blade moves off both Directors tell you to stop and it never resolves ( you need to wait until Blade has started Taxing before you request to taxi).

We have said in other threads we are unable to reproduce the issue, which is why we ask for data on the issue, a track and dcs log so we can look for clues. If you do not want to add them no problem, but please dont derail this thread. thank you VR hmd / ihads alignment threads merged

'Post your log and track file' - is that ED's version of kicking the can down the road for another 2 years?

Hello. Just started to follow the manual and compare it to the module, so some more question will follow. For now I have this one. I think there is a misinterpretation from my or ED side about correct sequence of engine start. Manual says that ignition is switched off when 35% are reached and APU and starting system are shut-down when 50% are reached. In auto sequence LHenginestarts after the 10sec rest of APU. In module we can see that this 10sec rest period starts at 35% when the RHENG START (lit when ignition is running) goes off, but not 10sec after the 50% reached