Mister Doodads Posted June 18, 2021 Posted June 18, 2021 Hi. I have been experiencing graphical problems with the Bf-109 after the 2.7 upgrade. I am running an i7 machine, 32GB memory, Nvidia 3060 with 12GB, on SSD. Controls are Logitech G940 with their drivers. The problem can be duplicated by using create mission, select airborne and fly. Once in the air, do a normal dive and the video will begin to glitch out. Level the plane and ascend and the problem slowly goes away. I have many planes (did not realize I have so many) and it seems to happen only with the Bf-109. I have included screen shots... I hope this helps you all. Thanks for your work.
Flappie Posted June 18, 2021 Posted June 18, 2021 Hi. Please attach a track showing this issue. How to obtain a track: Fly the mission and reproduce the issue Exit the mission Slick "Save track" ---
Mister Doodads Posted June 20, 2021 Author Posted June 20, 2021 (edited) Hi, I was able to record the issue. The file is attached. There are other random bugs that do occur but are not reliably reproducible. Mostly they are controls on the plane that do not respond but restarts take care of it. If I find others that have reproducible patterns, I'll post it. Thanks. Bf-109 glitch.trk Edited June 20, 2021 by Mister Doodads
Flappie Posted June 20, 2021 Posted June 20, 2021 Many thanks. According to your screenshots I don't see what you see, all colors are normal and the view it not obstucted, but the cockpit camera goes completely crazy! And then I loaded the mission (not the track): this time, I could't reproduce the issue. Couldn't this be a conflict issue with the camera axis/buttons on your Bf-109? I know the G940 can have issues with the throttle sliders (I used to have one) when the throttle handle is being moved. ---
Mister Doodads Posted June 21, 2021 Author Posted June 21, 2021 Hi. The screen shots are of the camera going crazy. That is how it captured it. I have many planes and this is the only one that does it. I would think a conflict would affect the sim globally. I do have graphic settings set to high, I forgot to mention that before. Let me know if I can get you more info. Thanks.
Flappie Posted June 21, 2021 Posted June 21, 2021 If you can reproduce this 100% of the time, try this: Go to C:\Users\username\Saved Games\ Rename your "DCS" (or "DCS.openbeta") folder as "DCS_backup" so the game cannot find it (do NOT delete this folder: it contains all your custom controls). Start DCS: it will create a "virgin" DCS folder If you're still able to reproduce the bug, launch a "slow" DCS repair ---
Mister Doodads Posted June 23, 2021 Author Posted June 23, 2021 I will try a "slow" repair as I already tried a fresh install. Keep in mind that this was never an issue prior to 2.7. Thanks.
Mister Doodads Posted June 24, 2021 Author Posted June 24, 2021 Hi, I did not try the repair as it didn't seem likely it would help after a clean re-install. However, you mentioned the throttle so I tried to duplicate the problem except this time, I pulled the throttle all the way back and did a dive and did not experience the glitch shown earlier. Trying again with the throttle forward did duplicate the problem. So it appears the throttle is indeed connected to this issue. It is limited to this plane and only happened after the upgrade. Perhaps with this info, the developers can take a look at the controller API's within this craft within the 2.7 version. In the meantime, do you have any recommendations or suggestions in regards to settings that can be done to compensate based on your experience with this control? I suppose I can always cut throttle on a dive but that is not always applicable. Thanks.
Flappie Posted June 24, 2021 Posted June 24, 2021 This doesn't look like a DCS issue; this looks like a hardware issue. Can you please attach screenshots of your Bf-109 axis controls in DCS? I'd like to see if your throttle sliders are configured and if so, for which commands. ---
Mister Doodads Posted June 27, 2021 Author Posted June 27, 2021 Hi, I have attached screen shots of what I think you wish to see. Let me know if there is anything else. Thank you. Here' the other. Thanks.
Flappie Posted July 19, 2021 Posted July 19, 2021 Hey @Mister Doodads. Someone else is having a similar issue. I'd like to compare your logs. Can you please reproduce the issue, and then attach your dcs.log? ( "C:\Users\username\Saved Games\DCS...\dcs.log" - may appear as "dcs" ) ---
Mister Doodads Posted July 20, 2021 Author Posted July 20, 2021 (edited) Ok. I have attached it. FYI, I have upgraded my controls to thrustmaster hotas warthog, and while bringing the sim to another level, it still does the same thing. Therefore, I would look more to video. I have an NVidia 3060 running the latest drivers. The monitor is an Acer, Nvidia GSync compliant, therefore, I have GSync enabled running at native 2K. Processor is i7 with 32gb memory. Windows 10 with latest updates, running as barebones as possible. I think it is odd I experience this with one module. All other modules do not do the same thing and I have a lot of them. Hopefully with this additional info, the problem can be more identified. Thanks. dcs.log Edited July 20, 2021 by Mister Doodads
Flappie Posted July 20, 2021 Posted July 20, 2021 Thank you. I'm still convinced there is more to this than a video issue, because your track shows the pilot view rotating left and right very very fast for no reason. And your companion in misfortune, @vfa132, has the pilot view zooming in and out at the same very fast pace. Have you tested this, yet? Go to C:\Users\username\Saved Games\ Rename your "DCS" (or "DCS.openbeta") folder as "DCS_backup" so the game cannot find it (do NOT delete this folder: it contains all your custom controls). ---
Mister Doodads Posted July 20, 2021 Author Posted July 20, 2021 Interesting difference in behavior. I had not before but I did now and it seems you have proved my hypothesis wrong. I cannot duplicate the problem. I have to test some more but it looks promising. So it seems I have to delete the old folder and redo settings in the new one if this pans out. While a slight inconvenience at least this issue may be resolved. I will update later this evening after more testing. Thanks.
Flappie Posted July 20, 2021 Posted July 20, 2021 Good! You can retrieve your previous custom controls from here: "Saved Games\DCS_backup\Config\Input". Just don't copy the Bf-109 folder for it might be the culprit. ---
Mister Doodads Posted July 21, 2021 Author Posted July 21, 2021 Ok... I have found the problem. Actually, your test helped me locate it. When I ran it originally, it ran with the default settings, with the exception of the axes which I redid. I then went into setup and set things to what I normally use, video, gameplay. I redid the test and the same thing happened. WTF? I deleted the folder again and reran the game and the problem went away. I set the video to my liking and redid the test, everything was fine. Went back into settings and set the rest like I like it, one of them being Game Flight Mode, and the problem surfaced. Went back into settings, turned off game flight mode and the problem went away. So there seems to be some sort of bug when set to game flight mode in the bf-109 module. Try that setting and see if you reproduce the issue (avionics you can leave alone). Thanks.
Flappie Posted July 21, 2021 Posted July 21, 2021 No problem on my end with the Bf-109 game mode. What you're describing means the conflcting axis/buttons are stored in the "Bf-109K-4 Easy" category: I assume you were looking for the conflict in the "Bf-109K-4 Real" cateory but couldn't find any. If you want to keep flying in Game Flight Mode, you first need to fix the conflicting controls in "Easy". If you prefer to fly in Sim mode (=Game Flight Mode off), you're already set. Thanks for your feedback. ---
Mister Doodads Posted July 26, 2021 Author Posted July 26, 2021 (edited) Hi, I couldn't get back to this for awhile. I have set all the axis for every plane in every mode and try to match every on/off control as well to maintain as much consistency as I can. The problem persists with this module, in game mode. I normally do not fly in game mode but do so with the bf-109 because it is so hard to take off otherwise. Oh well. Nothing else I can do at this point but work around it. I've provided all I can, unless you can think of anything else. I have no doubt it is a conflict of sorts but I do not know exactly what is in conflict. I would suggest passing this info on and logging it as it may prove useful as time goes on and more gameplay is done with the new upgrade and newer video boards. Thanks. Edited July 26, 2021 by Mister Doodads
Recommended Posts