jjohnson241

Same Problem here. Less than 1 fps. Running Win 10 64bit with GTX 970. Obviously unplayable.

Not sure what your problem is.. I'm running Win 10/Edge and can reload the DCS home page using F5 without problem for as many times as I care to.

For those that need it, here's Mustang's No Tree Shadow mod JSGME Ready. Mustangs_No_Tree_Shadows.rar

In using NVidia DSR, the game was set to a high resolution and the NVidia driver processed the game hd image and scaled the video image to the normal full screen monitor display. There was no need to set the resolution in Windows to the same as the game. One enjoyed the high resolution game video display detail using the "normal" monitor resolution. In the 1.5 beta, when you set the game resolution beyond the normal monitor full screen resolution, the game image expands per the higher resolution selected. Somehow, the game is not talking to NVidia DSR. The image should "scale" lower to avoid windows and the monitor having to display the higher resolution image. As I said in my post above, DCS 12.6 handled NVidia DSR without problem. I have yet to see any acknowledgement that this is a problem in DCS 1.5. If it is not considered a problem, please explain the difference between 1.5 and 12.6 regarding Nvidia DSR.

I have not tried this with Win 10 but look in Settings - Update and Security and you'll see Recovery on the left hand side. Click that and you'll see two options. The first reinstalls Win 10 giving you the option to keep your files or start fresh. I imagine you'll want to keep you files.

Second that and add that all clickable cockpit switches, knobs, etc., should have an associated key mapping. I noticed that the CB's associated with the start-up procedure, for example Battery, Inverters and Radio (ROD) CB switches have no key mapped in Options/Controls. Makes it impossible to create a HOTAS or Joystick Button mapped to the function. Please fix.

I too have this problem. Normal monitor and game resolution is 1920x1080. Using NVidia DSR, set game resolution to 3x monitor resolution and maintained aspect ratio. Video does not scale to monitor resolution but resizes image to 3x monitor resolution. Obviously needs to be fixed. DCS 12.6 had no problem with NVidia DSR.

Having the middle position of the Flaps button would require a LUA change. This belongs in the BUG report as the function should be supported, either on the HOTAS throttle or a key mapping otherwise.

I decided this morning to join the ranks of the BETA Testers. So, downloaded the BETA (about 1hr45min), ran the installation, downloaded and installed all modules (I license everything except CA), configured and flew the L-39C WITHOUT A SINGLE PROBLEM. Others may have had the same experience but I was amazed. Reflects a lot of hard work on the behalf of ED and I (along with others I'm sure) really appreciate it. As Wags said, there's a fair piece to go before we declare victory. Perhaps, but we're well on our way with a significant milestone accomplished. Next challenge will be to get the public version updated to reflect 1.5. I've every confidence now that will happen, and soon. :thumbup::thumbup::thumbup::thumbup::thumbup:

Falcon, Thanks much!

238thFalcon, Love your screenshots. Can you post your SweetFX 2 and Reshade JSGME mod here? Thanks.

My CH pedals run fine under Win 10. Check: 1. That Pedals are connected to a USB 2 port on the MB. 2. In Device Manager, make sure that the Power Options don't allow the device to be powered off by Win 10 to "save power". I had to go into each USB controller and usb device and adjust the power options thusly. If you use Control Manager, make sure you make the device manager - power options change when control manager is running and you have one logical device active. Look in the Game Controller applet to make sure you've got the correct device for the combined mapped controller.

I rarely fly on-line but what I do know is that a game with mods will not typically pass the on-line CRC checks made by the server. Translated, that means no mods for on-line unless enabled by the server.

Inside the mod and in the \Bin folder you'll find a SweetFX folder. Within the SweetFX folder you'll find a SweetFXSettings.txt file. Open SweetFXSettings.txt with notepad++ and edit the various settings for gamma, etc. I can't give you a formula for the settings. You'll have to play with those and experiment. If you like the color set, then concentrate on Vibrance and/or configuration that relates to intensity. Don't forget to save the sweetfxsettings.txt file after editing. Good luck and remember that all your mods including this one cannot be used with DCS 1.5 which is about to implement. The mod community is nearly back to square one with DCS 1.5.

I use Re-shade with SweetFX and prefer it over the original SweetFX. I've attached my JSGME Mod. Remove your original SweetFX mod and replace it with the attached in JSGME. Change DCS Video Options to use HDR "Cold". Search this forum for SweetFX and shader posts. There's a ton of SweetFX and Shader information. You did not mention what SweetFX mod/version you are trying to use. Make sure you delete all files inserted by that mod before you try the Re-shade mod attached. Always disable any mod before running the update to DCS. Edit: I re-read your original post and you may have to repair DCS before you try my mod. Go to Start Menu - Eagle Dynamics - run Repair DCS. Test after completion and before you try any mod. ReShade 0.19.0 x64-Cold HDR Blue 2.rar

Count me in. :joystick:

NTTR Observation/Question Hi Guys, I pre-purchased the NTTR map but have an observation and question: I noticed the map is nearly totally void of any "greenery" save the trees in Vegas and the other towns. No grass/lawns that I can see in the screen shots. Also, at least to my eyes, the color hue of the map is in general a washed tint. I realize this map covers a mostly desert area but I'm thinking it overdoes the "desert" look. In that respect, it resembles the bland look of the Crimea map. Anyone else notice this?

Yeah, so am I. The only thing I can come up with is the MFD drivers are handled differently in Windows. I found a post from Thrustmaster that says the devices differ from the normal USB as they do not send an "alive and well" message to Windows in the power management scheme. Windows as a consequence shuts the power off to the virtual device. Don't know if you have MFD's but they were my only problem. The Joystick and throttle behaved OK.

Catseye, Didn't work for me. The registry hack was the answer. Don't know what differs from your configuration but I went crazy looking for the answer after the approach you mention did not work.

I ran into a problem with my Cougar MFD's. I couldn't run a Target Profile that included the MFD's. Turns out that the problem surfaced with Windows 8 and continues with Windows 10 (I went from Win 7 to Win 10 directly). The MFD devices are placed in a sleep state (virtually) due to the fact that he devices don't send a signal to Windows that they are alive and well. This signal only applies to power management as the devices will test fine using their custom game controller applet. There is a registry hack to turn off the "Enhanced Power Management" for each device. Search "Cougar MFD with Win 10" and the registry change will appear.

Thanks for the reply. Back to square one.

Hi Folks, Has anyone tried to run a HOTAS target profile under windows 10 x64. I'm getting an error that one of the USB devices in the profile (the joystick) is disconnected and the profile shuts down. All devices are connected and working ok in windows 10 controller applet. I'm curious whether we have a Target problem or a Windows 10 problem (or both). Thanks

I tried Autostart in the Instant Action Cold Start mission and the engine started without problem. You may want to try that and follow the Autostart commands as they appear in the top left of the screen. It appears that Autostart uses the Oil Dilute for a few seconds and Primes the engine as it applies the Start switch.

Well so much for the assumption that it might be something simple and/or obvious. Have fun guys!

Let's not go crazy yet with drivers, etc. He said he had system sounds and did not mention a sound card. I upgraded from Win 7 to Win 10 and had no issues.