wernst

ok, then let me a bit more specific: DCS program will most probably not kill the PC. The latest update sure has serious bugs but is not killing. I was close to mess up my system completely just because I was applying some of the many "cure recipes" posted here. Later I was trying hard to get back where I had been before. The insidious and tricky thing here is, that obviously all crashes appear non consistently. Applying the one or the other cure recipes may as worst case even cause another issue which adds even more unsolvable problems. Therefore systematic search for what is causing the crashes is almost impossible. Meanwhile I rolled back to 2.5.6 stable and enjoy DCS crash free.

no, the program itself can not kill the PC, sure not. But applying many (if not all) of the cure recipes posted here may as worst case even cause a real serious problem e.g. system crash.

Thank you BIGNEWY for the wink with the fence post: „public open beta test“ in bold letters. Message understood. 2.7. is a beta test version, crashes have to be expected - and accepted. Your advice to my question „how to revert to 2.5.6. by command inputs“ - „Have a fresh and complete new install“. Yes, this message has also been understood well . . . even from a non genius. I was seriously asking for a pragmatic solution until we will receive future fixes but I feel fobbed off with less helpful phrases. I did some search how to revert tu 2.5.6 stable and I found this command: . . . \DCS World OpenBeta\bin>DCS_updater.exe update 2.5.6.61527.3@release If somebody can confirm that this command works to revert to stable I am fine. Thank you.

What is the use of detailed clouds and spinning props if I can’t see them? I carefully read all posts here and have come to the conclusion: So far no report could systematically, truly identify the cause of the problems yet. Many different proposals but no real solution. I'm afraid of following all the proposed solutions because I may inject the one or other new serious problem to the system. And then my system is really messed up. Until the ED devs come up with helpful solutions I want to switch back to 2.5.6. With this stable version I’m the only one who causes crashes - e.g. with the plane into ground. After the devs have evaluated all crashes I hope that they will post dedicated solutions here or release "cure-updates". But for the time being: How can I safely revert 2.7. beta to 2.5.6. stable? What I know is that it can be done with command line inputs. But which commands? What is the exact syntax for reverting the 2.7. beta to 2.5.6. stable? (esp. which updater version?) Any helpful input is much appreciated.

2.7. is installed. Loading old/existing missions is ok. But creating a new mission with new weather/cloud presets game crashes. Missions created which crashed: F-16C at Batumi RWY, Kobuleti RWY, div. clouds e.g. overcast, broken and other cloud presets. Edit: SOLVED ! The problem had nothing to do with mission creating and/or new clouds. As recently reported here there is an issue with the folder ...user/ name / AppData / local / Temp / DCS Just clean the folder content and you are fine.

Die beste Checkliste die ich bisher zum Hog gefunden habe. Alles drin, unwichtiges draußen. Wichtiges in Fett, Optionales oder Test in grau. So soll es sein. Eine winzige Korrektur: "AC INVERTER" switch wird mit (R) - Klick auf STBY gesetzt, nicht L wie fast alle ON - switches. Und, seit einem der letzten updates sind "AC GEN L + R" und "FUEL BOOST PUMPS L+R" für für MAIN und WING schon beim Kaltstart aktiviert. Warum auch immer.

No, unfortunately your beta and my stable are not the same version regarding these special lua file after last update, e.g. this one here for AMPCD: Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\AMPCD\indicator\BAKE\AMPCD_bake_init.lua AFTER LAST UPDATE dofile(LockOn_Options.common_script_path.."devices_defs.lua") -- the parameters for 'MPD_common_bake_init.lua' bake_page_path = LockOn_Options.script_path.."Multipurpose_Display_Group/AMPCD/indicator/BAKE/AMPCD_bake_page.lua" dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/BAKE/MPD_common_bake_init.lua") dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/AMPCD/indicator/AMPCD_viewport_cfg.lua") -- general purpose brightness_scale_gen_purp_nite = 0.085 -- night brightness_scale_gen_purp_day = 1.0 -- day -- HUD only, exported displays brightness_scale_nongen_purp_nite = 0.9 -- night brightness_scale_nongen_purp_day = 1.0 -- day BEFORE LAST UPDATE dofile(LockOn_Options.common_script_path.."devices_defs.lua") -- the parameters for 'MPD_common_bake_init.lua' bake_page_path = LockOn_Options.script_path.."Multipurpose_Display_Group/AMPCD/indicator/BAKE/AMPCD_bake_page.lua" render_purposes_to_use = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/BAKE/MPD_common_bake_init.lua") dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/AMPCD/indicator/AMPCD_viewport_cfg.lua") For the AMPCD lua file this line has gone after last stable update: render_purposes_to_use = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} For the right/left MFD lua file this line is still there but changing it doesn't have any effect anymore.

Do you have beta or stable version?

When in HUD ONLY VIEW the AMPCD (center) and both DDI’s (right and left) are blocking half the view, which sometimes can be annoying. In earlier DCS versions it was possible to switch OFF one or all displays in HUD only view if needed - fine. In later versions, when switching these displays to OFF, empty black boxes stay in the HUD only view - very annoying. Before the most recent update for STABLE 2.5.6.55960 it was possible to modify certain .lua files in order to get rid of these black boxes when DDI's are OFF in HUD only view. In folders . . . Mods/aircraft/FA-18C/Cockpit/Scripts/Multipurpose_Display_Group . . . these lua files had to be modified: AMPCD_bake_init.lua MDI_left_bake_init.lua MDI_right_bake_init.lua namely changing the following line purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} to purposes = {render_purpose.GENERAL} BUT AFTER THE LAST UPDATE THIS MOD ISN'T WORKING ANYMORE! The . . .bake_init.lua files either do not have the above lines anymore (AMPCD_bake_init.lua) or the line modification does'nt work anymore (MDI_right(left)_bake_init.lua). Request: Having the choice to switch DDI's to OFF without getting black boxes on the HUD only view.

When in HUD ONLY VIEW the AMPCD (center) and both DDI’s (right and left) are blocking half the view, which can sometimes be annoying. In earlier DCS versions it was possible to switch OFF one or all displays if needed - fine. In later versions, when switching these displays to OFF, empty black boxes stay in the HUD only view - not so good. Before the most recent update 2.5.6.55960 it was possible to modify .lua files in order to get rid of these black boxes. These . . .lua files in the folder "bake" had to be modified: AMPCD_bake_init.lua MDI_left_bake_init.lua MDI_right_bake_init.lua Namely changing the following line purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} to purposes = {render_purpose.GENERAL} which made the mod. BUT AFTER THE LAST UPDATE THIS MOD ISN'T WORKING ANYMORE! The . . .bake_init.lua files either do not have the above lines anymore (AMPCD_bake_init.lua) or the line modification does'nt work anymore (MDI_right/left_bake_init.lua). Which lines could be modified now? Is there any modification possible to remove the AMPCD/DDI from HUD only view?

done. Used SMN's mod for AMPCD_bake_init.lua and the AMPCD display is gone in HUD only view. This mod is also useful if you want to get rid of the left or right DDI or both.

But you have added: "Update: This isn't working now after yesterday's update"

The display of the AMPCD in the lower center of the HUD onlyview (F2) was previously not visible when brightness was turned fully down. Now, when turning brightness fully down the frame of the AMPCD is still there and visible as an empty black square. How can this black and empty frame be removed so that the center of the HUD only view (F2) is visible unrestrictedly ? (only left and right DDI’s are visible)

Both MFCD’s are either too bright (F1 COCKPIT VIEW) or too dark (F2 HUD ONLY VIEW). Usable brightness can only be adjusted to one of both views, the other will then not be usable. Adusting gamma helps to some extend, but it can be set for one view only and will be lost as soon as the view has changed – not usable. The 4 images have been taken under the following conditions: (F1 = COCKPIT VIEW, F2 =HUD ONLY VIEW) F1 Brightness „B“ = 15 -> whole display fully outshined, not usable F2 Brightness „B“ = 15 -> whole display usable F1 Brightness „B“ = 0 -> green symbology extreme outshined, map readable F2 Brightness „B“ = 0 -> green symbology ok, but map not visible Contrast „C“ has always kept at „40“. Other contrast settings didn't work at all. Setting „S“ has not been changed as I don’t know how to. Is it backlight brightness? The rocker switch for backlight brightness „DSP“ (top right side) of the MFCD has no function.

Yes, you are right, there are still quite a few more general lighting issues, which are subcritical and so I have gotten used to it over time.

"nightly cockpit too dark" had been an issue in former OB versions because flood light was by far to weak, almost useless. But now you can brighten up your cockpit as bright as daylight, just increase flood light, it's functional now. (It helps even in some daylight conditions) But flood light is only effective if Gamma setting is increased accordingly.

yes, I have already posted two other issues, which have been introduced with last beta update. One concerning unreadable MFD's (F2 view) in the Hornet and the other concerning dim digigital ALT display in the Huey. Both have been confirmed as bug, so let's hope for a general lighting overhaul.

After fixing the night cockpit flood light issues there is another issue with night lighting of the MFCD's Both MFCD’s are either too bright (F1 COCKPIT VIEW) or too dark (F2 HUD ONLY VIEW). Usable brightness can only be adjusted to one of both views, the other will then not be usable. The 4 images have been taken under the following conditions: (F1 = COCKPIT VIEW, F2 =HUD ONLY VIEW) F1 Brightness „B“ = 0 -> green symbology extreme outshined, map readable F2 Brightness „B“ = 0 -> green symbology ok, but map not visible F1 Brightness „B“ = 15 -> whole display fully outshined, not usable F2 Brightness „B“ = 15 -> whole display usable Contrast „C“ has always kept at „40“. Other contrast settings didn't work at all. Setting „S“ has not been changed as I don’t know how to. Is it backlight brightness? The rocker switch for backlight brightness „DSP“ (top right side) of the MFCD has no function.

Since last update 2.5.6.50321 the digital display of ALT in the radar altimeter is not readable at daylight anymore. Even when zooming in the blue digits are very vague, extreme weak, clearly not usable at daylight. All INST brightness knobs have been set to MAX.

Since last update 2.5.6.50321 the digital display of ALT in the radar altimeter is not readable in daylight anymore. Even when zooming in the display is vague at best, it’s extreme weak, clearly not usable at daylight. All INST brightness knobs have been set to max. (At night the digital display is fine, of course). UPDATE: Has been fixed with latest OB update 2.5.6.50726

what makes this issue even worse is that if sunlights hits the front cockpit panel from behind both MFD's aren't readable (MFD brightness and contrast to max)

since last update both MFD's on HUD ONLY VIEW don't have the black background anymore. Now the background is transparent and as result the green display is almost not readable anymore. (daylight, 2D monitor, no VR) UPDATE: Has been fixed with latest OB update 2.5.6.50726

The speed of mouse movement for external and cockpit view can be modified in View.lua file. e.g. I have slowed down mouse speed in View.lua ExternalmousespeedSlow = from 1 to 0.2 CockpitmousespeedSlow = from 1 to 0.2 This settings are more suitable for smooth mouse control of the external camera movement. The external camera movement can also be controlled by the view (down, left, right, up) slow commands by NUM key input. How can I further slow down the speed of these view (NUM) slow commands? Is there any entry in the view.lua file which can be modified like it's possible with the mouse speed (see above)? Which?

Thanks, Antoine, your link was more than helpful. This s/w obviously does exactly what I was looking for. No fancy jostick implementation for a virtual mouse in order to get smooth control of the external cam movement. Just software with many options controlled by the standard mouse. Great. I'll test it soon. Did you find this software in DCS user files? I haven't seen it there. Do you know the email adress of the author "Kaidrick"? Is he DCS forum member? Be safe these days, actually we have much time for flying in the DCS world.

Yes, a second joystick which behaves as a mouse would certainly be nice and would nicely (smoothly) do what I want. But how can I assign a second joystick in DCS options to function as mouse? Besides the 1st, real standard mouse? There is even a dedicated program "joystick to mouse". I have contacted the dev of this program and he said, that the additional joystick (as mouse) has to be assigned as the 1st (preferred) jostick device. I'm sure the DCS won't work this way - or?