KoleTang

@silverdevil I appolagize. I did not mean my post to be disparaging. I edited it after I read your post. It was not directed to you. I just wanted to make sure everyone saw my edits and the workaround if it happens to them. Thanks for being helpful.

Please re-read my original and very EDITED post. I found the problem and a good workaround.

This only exists in the MT version the ST version does not do this. When launching missions, especially the first one after the app launch. The progress bar would show no activity for 1-2 minutes. After that initial mission, it would progress normally or very fast for several more missions. But then might slow again. After updating to the latest NVidia driver 532.29, that extended to several minutes. I started looking at the log files and DCS was always stuck on the same log entry. 2023-03-14 21:02:55.871 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 13 After several rounds of trials, I finally found the root cause. I was able to get it working and created a log file with the following excerpt. 2023-03-14 21:17:55.854 INFO TERRAIN (Main): lSystem::CleanScenes() 2023-03-14 21:17:55.854 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 13 2023-03-14 21:18:13.565 INFO EDTERRAIN4 (Main): TERRAIN_REVISION = 5124 You can see that it only took 18 seconds to complete the "EDOBJECTS (Main): lTypeObjectManagerImpl::clear 13" operation. My only complaint about this now is there is no progress bar update during this. There appears to be updating on the ST version. Edited Here - Please read this After even more of the same issue, I think I have found the proper correct cause and good workaround. It appears to be a file system deadlock. It happens whenever I would start a mission that used a different map from the last. What I have found is that I can break the deadlock just by opening a folder or some other file operation. This results in an immediate release of the deadlock situation. Edited Again 3/16 2:45 The actual workaround may be interacting with the UI of another app. I was fooled into thinking it was manipulating folders in file explorer. But I have found that other apps work even quicker. Simply moving the mouse across an open browser will do the same. In addition to updating my Nvidia driver I also updated windows. I am running Windows 11 Pro Build 22621. I and I now believe the windows update created the exasperated issue. Overall this has been an extremely positive upgrade to the sim. Thank you very much. Cheers. bad.dcs.log good.dcs.log

If you fly a mission in the AH-64 then fly an F-14 mission and go to adjust controls the position drop-down menu defaults to the position you last flew in the AH-64. For example, it should have F-14 Pilot but instead has AH-64D Pilot or AH-64D CPG. It does not do this for other aircraft transitions. Only from the apache. It creates confusion as I was meaning to adjust the tomcat controls and ended up changing my apache controls. I just noticed this in the MT release but could have been there before.

This is still the case in the MT Preview. Hopefully, this will be fixed in the upcoming apache fixes.

This is an annoying bug. I have found the best workaround (i.e., works most of the time) is to push both throttles to >90% after pushing the second start button. Ignore the engine fail alarms as it will start. This ruins the cold start experience in this mod.

When using either the 1.78 or 2.24 factors with 4k (i.e., selected resolutions 5120 x 2880 or 5760 x 3240), George's target selection menu is either partially or completely, offscreen. In both cases though the text to select from is offscreen. It's apparent that George's overlay origin/placement is different than the controls overlay which works perfectly with both DLDSR settings. I have a RTX 4090 so I have a good bit of headroom. I limit framerate to 100 FPS. The improvement in image quality from using these settings is amazing. I have tested with the FA-18, A-10 and the Apache. All I have found so far is the problem mentioned above. This is very easy to test with an NVidia card and a 4K monitor. I have not included any mission or log files because they are not required to repeat.

Now that I know the times. I can work around it. Thanks again

Sure, here are the files. And an example. Starting logbook. Mission Debrief. Updated logbook. Note flight hours change correctly but Nighttime stays at 6h 3min. Could it be a time zone/map issue? Thanks for replying. ACLS_Night.miz dcs.log

I have noticed this since 2.8. But I was able to spend some time with this today. I tried a fresh logbook.lua file and was still able to recreate the issue. ["nighttime"] is not being updated in the aircraft statistics.

I found my problem. The method I was using is no longer supported under 2.8. The correct method is to select SEAD and task attack ground unit with decoys for weapons. I was using the bombing method and that no longer works.

AI units are no longer deploying TALDS after 2.8. None of my existing missions utilizing AI with TALDs work after 2.8. Worked perfectly before. Has the methodology changed?

When the launching crews change activity, they have a very noticeable glitch when they change activity. It's like they start the activity then do a short rewind then continue. My platform is a i9 12900K and RTX 3090 Ti. Additionally, while flying I am now experiencing some substantial hitches. I had neither of these issues before 2.8.

I was trying to record the F14 landing on the Truman. I land fine but when playing the track file back it lands in the water about 1/2 mile to the right. I changed the plane to the F18 and the track file is perfect. I also changed from the Truman to the Stennis and got the same result. The F14 did not work but the F18 did. The difference seems to be heading related. The further I start the F14 from the carrier the further the track file separates. F18TestSC.trk F14TestMV2.trk

Yes, this is becoming a daily event. From what I can discern, it seems that DCS is getting "lost". It is still running but is ignoring keyboard input and not presenting the display. Alt Tab works but when you do your mouse clicks are still being captured by DCS so you can't kill the task in task mgr. If I do a windows switch user I can get the mouse back and kill it. Since, it doesn't crash there is no crash report. I will send log files next time it happens. I have a high end system as well. i9 12900K, 64G ram, 3080 Ti

The South Atlantic map has a lot of very cool real estate. Most that is far from any bases. It would be very nice if we could use all of that beautiful empty space for missions without an aircraft carrier. A deployable temporary airbase would be a great addition to the mission editor. Something like the San Carlos FOB would be perfect.

Just looking for some flying buddies. Been flying single player for about 4-5 months. Looking to expand to multi-player. I have over a hundred hours spread over mostly 4 aircraft. In order of flight time. 1. A-10CII 2. F-16C 3. F-18C 4. UH-1H Very much a noob with multi-player.

Ok. All is well. This is just a story about how easily you can fall down a rabbit hole. Turns out the default kneeboard for the A-10C_2 in open beta has added the HOTAS manual pages. The release version does not have these pages. I thought having those exact same pages was a good idea, so I created them when I was using the release version. When I switched to the open beta, I just copied the folder over. If I had gone a couple pages past the first, I would have seen them duplicated. I was using these pages as a test to see if it was updating and what I was seeing was the default. When I checked against the release version, those pages were not there and that amplified my confusion. On to the next rabbit hole. Thanks to the people who responded.

I just tried the nuclear option and uninstalled and reinstalled and the problem still exists. There appears to be some other location for user data.

I just tried renaming the /saved games/dcs.openbeta folder and my existing kneeboards still showed up when the new folder was created by DCS. They must be cached somewhere else.

I have deleted the /saved games/DCS.openbeta/Kneeboard/ folder. I have since tested this on 2 other machines. One with production and one with the open beta. I was able to recreate it on the open beta. The production version does not exhibit this issue and I can create, update and delete kneeboard pages with no problem. I have 2 machines with the open beta that both exhibit the issue. One of the open beta machines was a fresh install on March 5. It appears that my kneeboards are stuck at what they were at the time of the last update. I have done the clean/repair procedure with no improvement. I am running only ED stock mods.

I have also deleted the Kneeboard folder and my custom Kneeboard pages are still showing up. I am running the latest open beta with only stock mods. Is this the appropriate place to ask about this? I think it could be a bug.

I have created a couple of custom kneeboards for the A-10C_2. They were working but I was trying to add some for the F-16C and the FA-18C_hornet. I was not having any luck getting the new ones to show up. In playing around, trying to figure it out, I renamed the Kneeboard folder to something else and my A-10 knee boards still show up. Is there a cache of them somewhere that needs to be updated/deleted for the new Kneeboard folder to show up? Or lack of a Kneeboard folder to show up?