klem

:music_whistling:

'DCS Updater' updater: "Version 2.6.13: - Skipped because of the tradition" :megalol: EDIT: ooops, today is the 13th :(

+1 probably a bit late for you now but in Windpws CP.... 'Programs and Features' I had 1.2.16 and 2.0 listed but not the open beta as that was effectively a copy, not an install, of 1.2.16 converted to 1.5 beta. I worried that there might be some registry issues so I manually deleted 1.5 beta and updated 1.2.16 to 1.5.

What, like "DCS Panavia Tornado (IDS) really needs to be a thing!":lol: Just joking.

Along with a Wildcat/Hellcat/F4U :D I'll take any Carrier I can get !

I can only refer you to post #1 and #2 and the fact that I had to remove Sweetfx for 1.5 (EDGE?) to work properly. It looks ok though.

Actually I already tried that but, stupid me, I ran a repair and the problem went away. I hadn't considered that as I only recently updated it. :wallbash:

In 1.5.2, Options, Controls, F-86F, Keyboard

Why are the following controls settings displayed in RED and do not actually respond to the key presses? Cockpit Pressure Schedule Selector Switch - 2.75 PSI/5 PSI || Left Side Panel || LAlt + LCtrl + P Engine Anti-Ice and Screen Switch - Down || Left Forward Console || LAlt + LShift + S Flight Control Switch - Down || Left Side Panel || LAlt + LCtrl + C Longitudinal Alternate Trim Switch - CW || Left Side Panel || LAlt + LCtrl + D Pito Heater Switch - On/Off || Left Forward Console || LAlt + LShift + P

A simple mission with an F-15C in flight. A trigger is set that will load the same mission on Unit Dead or Unit Damaged. When ditching the a/c the reload command is implemented but DCS stops working. Logs attached. Logs.zip

OK

It was online in server "*** TAW.net - Event server - DCS World 1.5.2.43162 ***", Mission Name "03_Novorossiysk Massacre".

OK I will. Do those sound errors look like my rig or DCS?

Win 7 64 bit home premium

There's no confusion. V2.0 is an Alpha test model which is downloaded separately from 1.5. If you have 1.5, the v.20 install should automatically activate your modules in v2.0. The only map that can be used is Nevada which you will have to pre-purchase, otherwise v2.0 will not do anything. Most aircraft controls work in v2.0 (I haven't found any that don't) so you can go to Options... Controls, pick your aircraft, highlight a cell under your controller and click Load Profile at top right. Next, navigate to the v1.5 /Saved Games/DCS/Config/Input/[aircraft]/[device type]/ and select the ****.diff.lua file for your controller and click OK and it will load into v2.0. When you then click OK on the Options panel it will save to the v2.0 folders. For [device type] I mean keyboard, joystick, mouse, trackir. At he moment Nevada really hammers the GPU back to v.12 Caucuses levels but it's still in alpha. As said above you can make missions or fly online but really feedback is wanted.

Not since the crash. It was running just fine. I can do a repair and then wait to see if I get another freeze. In the meantime do you see anything in the logs?

OK, I see your problem. You are running 11.4 MegaPixels. I have all four of my monitors (triple plus 1) side by side in 7820x1080 = 8.4 MegaPixels whch is easier on the GPU but requires all monitors to be the same height (e.g.1080). hansangb is correct but try the attached, tailored to your screen resolutions. You can rename the file to whatever you like, DCS selection uses the "name = xxxxx" inside the file. If you get around to bezel correction then change bezel_left = 0 to whatever the left hand bezel value is in the Surround setup. Remember to use Notepad++ not Windows Notepad. HOWEVER! This comes with a warning, there is a triple screen problem which has not been addressed by ED yet. The map gets squished as DCS appears to try to squeeze a screen.width/screen.height size Map into the GUI width/height. It is worse with all monitors side by side as the aspect ratio is different. As you know, if you just leave the GUI unspecified, which uses the entire screen.width/screen.height, the bottom left and right hand corners of the GUI are off the screens (where you don't have bottom left and right monitors) and the map, though not squished, suffers the same loss. It's possible that with the attached and your three over one setup the map may not be too bad and I'd be interested to hear. 5760_1080_Over_1440_900_Insts.lua

They would be in the "C:/Program Files/Eagle Dynamics/DCS World/bin/" folder (the main game folders not C:/Users/[username]/Saved Games/DCS etc.) If you did not install them you won't have them. If you did be sure to remove the SweetFX folder(s), all Sweetfx***.txt files and any of the following (you may not have them all): d3d9.dll d3d9.fx dxgi.dll dxgi.fx injector.ini log.log shader.fx

Do you mean 5760 x1080? What are the resolutions of each monitor? Which MonitorSetup file are you using? Is that bottom monitor using in-game DCS cockpit or HELIOS? Yours looks very much like mine except I use bezel correction with the bottom monitor displaying the in-game cockpit so hopefully I can give you a lua file.

Hmm not sure what happened there but zipped folder is attached. Logs.zip

No idea why. Just locked up mid-flight during on-line mission. Log attached.

Same problem in 1.5 release. Any news?

THANK YOU! A leftover from 1.2 All good now :)

My GUI and any missions I load have graphics problems. The GUI is in low res black and white and missions are all night-time with intermittent but frequent flickers and poor quality (resolution?), clouds etc. I have tried various MonitorSetups from stock 1 screen and 3 screens, my usual triple screen over instruments. All the same result. My triple screen definition is copied across from my 1.5 open beta version. I tried deleting the entire /Saved Games/DCS/ folder to re-create on launch. Same problem even before I make any adjustments. Tried Windows Start... DCS... Update and Repair routes. Same. Checked my 1.5 open beta version through Update and have same version as the 1.5 released today. The open beta works ok. I will use open beta for now but as it is a copy I'd like to solve the basic problem to avoid installed programs registry issues.

Set a waypoint for the AI where you want the aerobatics performed and go to Advanced (Waypoint Actions). Click on Add. You'll find Aerobatics under 'Perform Task'.