wernst

heard already about this 3 sec hold ENT after freq input, did it, got short blink, but no effect.

Maybe I missed something. After entering TWR Freq on the FUC and call ATC for e.g. start-up I don’t get any answer. What I did: Example for Khasab (Gulf map) TWR FREQ 124.350 (FM) taken from map binding COMM sw (RAlt+\) to key 17 of Throttle on the FUC: Left COM click/push to ON click :FM left COM selector dial to M CLR via scratch pad enter 124.350 ENT call key 17 COM menu, e.g. ATC, start-up (F5, F1, F3) No reply. What’s wrong here? Thanks for letting me know.

yes, YES, Y E S, your guides are NOT "condensed manuals" and that's the charme of them. Without your "image guides" I would have not been able to enjoy the complexity and immersion which DCS is providing. Thank you.

yes, the same here with me, same solution: https://forums.eagle.ru/showthread.php?t=209470

Yes, thanks, I know, but so far I had not much progress in performing any SP campaign. And I don't want to save this disaster . . .

I had the same, stuck loading at 55%. Support said: "Please rename the folder MissionEditor located here C:\Users\user\Saved Games\DCS.openbeta\MissionEditor to any Temp name, then run DCS again" FAQ to this https://www.digitalcombatsimulator.com/en/support/faq/980/ I didn't rename this mission editor folder, I just deleted it. It will be built again by DCS. Hope, it helps.

Thank you, Dav, you have epressed well what my feelings and experiences with DCS world 2.5. are. I'm not native english speaking so I want to join your "thank you ED" speech. And, yes, stutter, which was at the 2.5 beginning is now almost gone (still one for 0.5 sec once a day, who cares) In short: Thank you ED, DCS world is my flying world. Nothing compares to it.

“wrong” is in quotation marks, it’s irony! I simply want to stress that my system behaves differently. My basic question is: What is the reason behind that one system (e.g. mine, Win7) runs well but others not. If it is a DCS bug and not OS related then all gamers, regardless of their OS, should equally be complaining about CTD’s, right? "a greater number of error reports from users with Windows 10 are because there are more users with Windows 10" “a greater number” THAN what. . . “there are more users” . . . THAN who? I’m sorry, I don’t understand the logic of this sentence. The basic expression of this sentence is: a greater number is . . .because there are more. It's an uncomplete comparison, there is no logic, it’s tautology. If I could get at least some reports from Win 7 users about CTD’s after 2.5.2 installation I will end my comments here.

Please learn that I didn't want to report that everything is ok with me but I was trying to help others what may wrong with their systems. Is that what you makes lol?

ok, not the OS. But, "I'm sorry", I don't have any DCS bug! My Win 7 drivers are not up to date. (I'm afraid of the meltdown and spectre updates) And I don't have "the most popular OS nowdays". I have the poor man's Win 7 only. What then it's "wrong" with my system, because everything is ok?

After reading all the CTD posts here (log files) I noted, that most if not all crashes are related to Win 10 systems. Is it really? Or is it my misreading or coincidence? I run 2.5.2 and Gulf map on Win 7 now for almost two days - crash free. Since I set page file size from “stupid low MB” to “system managed size” I had no single crash anymore. I tried all maps, many modules, flew saved missions or started newly created missions (day/night) directly from ME, again and again - no single crash. (Even stutter seems to have gone). Switching off/on the PC many times, loading different missions - no crash during the last two days. But I still keep my fingers crossed !!! There are of course many systems out there which run crash free after the 2.5.2 and Gulf map installation (as mine). And there are systems which are troublemaker. What is it? Do I have just luck or is my luck related to have an old but updated Win 7 system?? Again, it's just a question, a guess which is far from being an expert's advice. If there is a system difference between Win 7 and Win 10, which has negative impact on the new 2.5.2 installation, the DCS team might have a clue to solve the issue. Or not. If not we still have to pray.

https://askleo.com/what_is_pagefilesys_and_can_i_move_it/

No, of course not. My expectations are low, the level of my excitement is below moderate. I know well from other Windows experiences that solving a problem is a continuous process of happiness and frustration. I hope that DCS solves the CTD with a solid solution.

Yes, you are right, that's what I learned most recently. But - since long I was playing DCS in all versions, maps and modules with a somewhat stupid 20 MB page file size setting - without any problem. After updating to 2.5.2 and installing the Gulf map I had multiple crahses. After setting page file size to "system managed size" all crashes are gone. What has happened? Magic? Placebo? Spurious correlation? I myself can't believe in the page file size thing, the problem behind it's probably more complex. But what is it, what has "healed" my recent DCS installations?

After modifying my page file settings I had (so far!!) no crashes anymore with 2.5.2 and PG and any module. Is it real? How? As inspired by “David_OC” here and his link to “ask LEO” (thanks David) I modified my page file (Win 7) settings by increasing the page file size considerably, namely from “custom size = 20MB” (which was obviously by far too little) to “system managed size”. Result was a 12279 MB page files size on my only one SSD drive, which is just a bit over my 12 GB installed RAM. I want to emphasize that my page file size modification and the effect on CTD’s might well be a spurious correlation. So I’m still keeping my fingers crossed.

After some repeating tests with the Gulf ME I found that one SHOULD NOT start a newly created mission directly from the still open ME. After creating a new mission one should close the ME and recall the new mission from the “missions” menu. My earlier conclusion posting that the CTD has to do with night mission was obviously wrong.

same here - but only if one starts the new created mission directly from the ME. Saving the mission first, restart DCS open beta completely and then loading the new mission seems to work without crash. Memory issue?

After installing the Gulf map I had crashes under the following conditions: - Su-27 night flying over Dubai - setting up a new day/night mission (e.g. Su-27, M2000C) in the editor, saving it and click to immediately fly it Setting up any mission and recall it anytime later seems to be ok. All day flights seems to be ok as well. I had (almost) never any game crashes with the three other maps. I'm not really worried, I'm sure this (memory managment issue?) will be solved later. So far my positive impression of the Gulf scenerey prevails.

Is the Hornet designed to fly in the Gulf scenery only? Or will the F/A-18C (at least) be flyable in the Nevada map too?

Sorry, I missed this feature completely as I was always using the cargo cam since beginning. Yes, the indicator works. I consider it as the poor man’s cargo camera. It’s to some extend a reasonable alternative to the immersive feeling which only a real camera view can give.

"cargo indicator"? What is meant by this? Did I miss anything? "voice prompts": I'm sorry, but these voice commands aren't much of help to me. (Or maybe I don't understand how to use them properly for hovering just above the cargo). The UH-1H cargo is a challenging mission and is very useful to improve heli skills.

Since 2.5.1 the UH-1H cargo camera doesn’t work anymore. When switching the cam to ON only two thin black lines appear which are defining the outer boundaries of the square camera insert in upper right corner. The content of the insert displays the actual part of the scenery only. Did I miss anything, could any system setting solve this issue?

the same here

no, the 2 min stutter interval isn't constant. Up to now I only can say: After the 2.5 update the stutter was annoying. Now, after playing different modules for about 10 times (from start) the issue is there but doesn't spoil the fun that much anymore. I can see now that the stutter occures more irregularily, let's say each 2 - 3 minutes. It seem that over time the stuttering becomes less dominant. I wonder why? The only thing I can definitively say is that with world 1.5.8 I can play stutter free - with the same hardware and without changing any heardware settings.

doesn't help here. Since installation the Saved Game Folder has alway been together with the game on the same SSD drive. (default by installation) Surprisingly the stutter intervalls are becoming longer over time. Initially playing 2.5 the stutter occured each every 10 - 20 sec. Now the stutter interval is more than 2 minutes long. Will it disappear finally?