Wiesel02

Hi, I have quoted my own post from above just to get the context right... An hour ago there was an automatic update to my BitDefender anti virus. I let it install and thought I could give it a try again. I ran a DCS repair on stable and open beta installs (I have both) and then restarted the PC. Then, up again, I started both versions of DCS and there was no anti virus hit. The Harrier module was available again with no issues in both versions of DCS. Just wanted to let you know.....because I think that sometimes issues like this could be caused by the anti virus software rather than by modules files in your installation directories. I conclude this because since the issue came up and what happened today, there were no changes/updates introduced by EagleDynamics/RAZBAM, it is still version 2.9.5.55918.

I have the same issue "...\bin\AV8B_CPT.dll is infected with Gen:Variant.Lazy.551852". Appears since last update 2.9.5.55918. Is this under examination? Restored the file from quarantine and scanned the drive. Again it is detected as a threat. Removed it for now, then scanned again, no more threats found.

Ah, ok... thanks a lot!

Sorry, but no Sir. At least, not in my case. I tried Auto Start in Stable Version 2.8.4.39731 and OpenBeta 2.8.6.41363 and in both associated MT versions. Same issue as was described here before: When in external view the Auto Start doesn't make it past the "APU 20 seconds" issue. Test map was Nevada. No switch of seats. Nothing at all was switched, just the key to external view (F2 view) followed by Auto Start procedure key. Nothing else. When in cockpit view, however, the auto startup works fine. Let me know please if I can provide some data that might help and I will try to post it. Thank you!

Hi Flappie, in return, nice finding! So I checked it out. Test modules: Super Carrier and F14B. Really, it seems to be a mix of double and single MOUSE_BTN3 clicks to switch between on/off clickable cockpit and on/off head movement fwd/bwd or normal zoom. But this is new right? I mean, I never noticed this behavior before...

Hi, thanks for investigating. I checked according to your hints Flappie. Actually, I found that now with 2.5.6.55960 stable version, there is no longer a need for a button assignment for mouse control in the cockpit. I don't know if it's something I never noticed before, but now you can just use a MOUSE_BTN3 double click to activate/deactive clickable cockpit control, even with the F14B. As far as I can see, not mouse control need be set up at all to get this functionality. So in the end, I don't know if it was buggy before and has been fixed now, or if it was just me - I could have missed it. But during the tests I made with several modules, I found something else: Before the latest stable version update I could zoom by using the mouse wheel in the cockpit when mouse control was active. I can zomm now as well, but the type of zoom seems changed. Before, it was a zoom function just like you would expect - zooming in and out from the current head position. Now, using the mouse wheel just moves the basic head position inside the cockpit forward/backwards, but it is not a "zoom" any more. Best visible if you look to left or right side panels and then use the mouse wheel to zoom in or out. Your head moves forward/backward, which is not a "zoom" as I know it. Do you see the same?

Hi Guys, since the latest open beta update the function "activate/deactivate clickable cockpit" (that's possibly what it is called in the english version) seems changed. Don't know if this is a bug or a feature. For all modules that previously allowed a mouse button to be assigned to activate/deactivate the cross-hair inside the cockpit for clickable cockpit control, it's the same: It no longer works. And in the control settings that function is red marked now as long as a mouse button (in my case I always had Mouse button 3 set up for this function) is assigned to it and doesn't work any more. It always worked before the update. Except for modules that never offered a mouse button to be assigned to that function, like the F14B. I also noticed that assigning a key on the keyboard to that function works without issues, but as long as the mouse is in use for activating/deactivating clickable cockpit controls, it no longer works. Does anyone know if this a intended or a bug? Because I always liked the idea to use a mouse button to activate/deactivate cockpit controls via mouse... Thanks!

same for me, i just reported to the support. let's see if it helps...

I have exactly the same problem since 2.5.6. Still nothing helps, none of the recommendations, not a fresh install, no twiddle with folders or files in saved games...DCS just hangs on startup screen and won't let me do anything

Hi, I just made another startup and here's the log file. dcs.txt

no, doesn't work. This is not related to antivirus. It's just the presence of theat damn folder...

I will try and let you know if it works. Thanks for responding mate!

I have posted the issues as a response to another thread that dealt with antivirus problems, and meantime it was classified as [NO BUG]...so I am repeating here, but not related to antivirus issues. The antivirus problems are gone for some reason, but DCS OB still gets hangs at start up and is simply unusable. Only the first start is successful, and only if the saved games folder "DCS.openbeta" does not yet exist before the program start. If it exists already at the time I start DCS OB then DCS gets stuck on the startup screen and that's it. Always. It is not possible to do the initial settings, like screen resolution changes for instance, because all settings changes that require a restart of DCS will lead to hang-up-start as the "DCS.openbeta" folder exists already. No chance to get out anyhow but killing the DCS process. So, this is NOT solved for me. DCS OB doesn't run since the update to 2.5.6. No issues whatsoever before that change. Please, any ideas?

... and so, it's also not possible to redo the settings, such as screen resolution, because all settings that require a restart of DCS OB lead to the situation where the restart will be made with the saved games folder already in place - and thus to DCS hanging up on the startup screen. In that case I can't even kill the process without restarting the PC. Next time I try, I have to delete the saved games folder again to avoid the lockup, but of course, the settings are defaulted again. I also noticed, that on the startup screen, the music starts playing for 1 or 2 seconds and then it starts hanging. No idea what happened here since 2.5.6, but it's completely unusable.

Hi Bignewy, first of all, thanks for your support! I followed your proposal and did some tests. First: I inceased the page file size as recommended from 4096 to 16384. -> No influence. Second: right after having backed up the folder "DCS.openbeta" by renaming it to "DCS.openbetabackup" - so before DCS could create a new folder, the startup worked. I didn't trust it (sorry), so i closed DCS and immediately restarted it. This time DCS had already created a new "DCS.openbeta" folder (from the first startup). That's when the startup fails again and everything just hangs up as soon as the startup sceen is shown and music should start playing. Next trial was: again, I deleted folder "DCS.openbeta" on drive C: that had been created new just before. The backup was still there, so ne need to redo that. Result: startup was sucessful. In general, i takes more time than ever before, but it finally worked and DCS wasn't locked up. Again, I closed DCS and restarted it. Result: Failure again. So, it seems: - the page file size thing is not the root cause for the trouble. - the problem is linked to the "saved games" folder somehow...once DCS has created it new from scratch, then the next startup fails and hangs up. As a reminder: I never had any problem with DCS or DCS OB so far with my system, it all started when OB 2.5.6 was released and my system did not change in between 2.5.5 and 2.5.6. Stable version is still ok without a need for any of the above changes. Any more ideas?