Grontar

Just tried it and it worked like a charm again. You are a godsend Flappie. Thank you very much and just in time to enjoy the Marianas release! 11/10 sir.

Dear Flappie, I just managed to find some time to try VR mode. Unfortunately, the problem persists on VR, with the black screen and me not being able to reach the main menu. This time, the game crashes. Here is the log I managed to get (I guess it is not a graphic/ headset problem, as I ran Onward just to check the VR set and worked fine, as usual). Sorry bothering you and thank you very much again in advance for your assistance. Kindest regards. dcs.log-20210629-215331.zip

Seems to do the trick! At least in 2D. I will try VR as soon as I am able to and keep you updated. Thanks a lot Flappie for such a quick and effective answer. 10/10. Best regards,

Dear ED Team, I open this thread as I found a problem I have never experienced: I tried to play DCS last weekend, and I was not able to even reach the main menu screen (VR or 2D) as when initiating DCS it only leads to a black screen with no end. Not a crash, not a freeze, just a black screen, and after waiting several minutes, I am forced to close the program with Alt+F4 or similar. Needless to say, I ran the slow repair / integrity check with no result. I tried a complete reinstall of the closed beta with no result. Of course, DCS & Windows are totally updated and Nvidia drivers too. I attach here two logs (VR and 2D) so you can have a better view of the problem, and hopefully, get it solved. Thank you very much for your swift actions and assistance. Please let me know if I can help anyway (even via Discord or similar). Kind regards. dcs A-2D.log dcs B-VR.zip

I removed axis curves. & Settings page for the Ka-50: FFB with no springs option selected. Thank you all again :)

Hi all, Just quick update, after finding some free time today, I tried adjusting setting as you suggested in your comments for the Ka50 and I am happy to day it worked like a charm! I have no longer to fight the stick and the shark became pleasant to fly instead being an uncontrollable beast. :thumbup: Thank you very much for your cooperation, time and support. Happy flying pals and see you around! :pilotfly:

Thank you very much for the tips guys. I will try around this weekend and see if any of them works!:joystick: Kind regards, and enjoy a nice time you all.

Hi Volk, (Thank you for your videos by the way, sweet material there). The only way to "not fight" the stick is having the trimmer button pushed all the time, which is not comfortable either for long periods. The moment I release it to register the trim to set, it strongly & quickly positions itself in that forward-right position and stays there. as if ignoring or misreading the input. Just to discard this can be a joystick malfunction, I have other warbird/jet/helicopter modules in which the trims/force feedback works as intended to (Huey to name one). This is why I asume is some Ka50 configuration / procedure I may be doing wrong. Thank you again for the time and comments. Best regards!

Fellow Ka-50 pilots, I come to you today because I admit I love this module; but there is a thing it really annoys me when flying the shark: I am a MSFFB2 joystick user, and the moment I engage the force trim, the joystick itself positions itself in a different position and it would require a decent amount of force moving it from that position, making trimming the helicopter something unusable and very uncomfortable for longer sessions. It may be something I am doing wrong regarding autopilot usage, specific Ka50 options...I really do not know anymore as I have tried different configurations with the same or no result, and this is why I find myself writing here. Thank you very much in advance for your comments and assistance (and patience). Kind regards!

What a wet dream that would be pal...

I am a WMR user and I can also confirm that crashes also happen there. Thank you very much in advance for your time, investigation and efforts.

I experience the issues in different maps as well, such as Caucasus / PG / Normandy

As one user previously said: "I noticed the strobe light doesn't change from dim to bright." that is totally right, and not only that, the intensity regulator knob on external lights seems not to have effect at all, meaning they seem to be off, or full powered.

Absolutely +1 to OP's message: I have been experiencing the exact same issues he describes, and he describes them accurately (I mean, you learn how to "force" the issues to happen, and how to "cope with them"). As a DCS enthusiast, and owner of several of its modules, I feel it is really sad and dissapointing to see how this poor performance / FPS drops / crashes are not a high priority matter to address and fix, but having a new version of something already existing (A-10C II as an example) is. You can argue getting money from a product is important for a company, but having a dwindling playerbase in latest years due to poor optimization should be a big concern too I guess. Renewing the old graphic engine is a promise still unfulfilled since years, and optimization to better take advantage of newer technologies should be a must. I agree the solution to the problem should never be "toss more RAM to it", that is just lazy. If you have a leak in your gas tank, you do not buy a bigger leaked one, you just fix the leak. Pure logic there. I hope ED realizes this can have a big impact in their existent and future playerbase / customers, especially when there are other simulators available showing this is posible to achieve, not just a crazy dream. Thank you in advance for the time and attention, and kind regards.

+1