DCS World Updates thread

[aceviper]

I preferred the previous water animation and color...ships stood out much better against the darker color and it looked more lifelike.

ED should darken the default color a wee bit.

But since water is rendered over the entire map..maybe it was causing the fps loss for most people.

 

hey nate went through all the water settings....its still the old water

Edited October 5, 2012 by aceviper
*

[Nate--IRL--]

6192??? :huh:

 

strange ... mine still 6148 and the Auto-update doesn't kick in :cry:

 

Just found out why on another post:

This happens when the server gets hammered c0ff has promised more intelligible messages soon.

Nate

 

Auto-update only checks once a day - use the update function in the DCS start menu entry to force an update.

 

Nate

[[DBS]TH0R]

1) hash mismatch error is now correctly identified as server overload. (not sure it got into 1.2.1.6148, if not, it'll be in the next update for sure)

 

2) autoupdate.log file is for troubleshooting purposes only. Human-readable changelogs will come.

 

Thanks. Trying to update without a success for the past 4 hours. Every time its the same message: mismatch error.

[Ghanja]

FPS are back to normal for me too - thanks for that one ... :thumbup:

[cichlidfan]

1) hash mismatch error is now correctly identified as server overload. (not sure it got into 1.2.1.6148, if not, it'll be in the next update for sure)

 

It would be useful for the updater to reset it's timer if a server overload occurs so that it will retry automatically when the sim restarts.

[Corrigan]

Any reduction in graphical detail?

[Nate--IRL--]

Any reduction in graphical detail?

 

For low water settings yes, the water was changed back to 1.2.0 water - But that's it AFAIK.

 

Nate

[Simas]

It'll be if much help if you .zip and post the *.crash, me.log and dcs.log files left after the crash.

 

Attached my ZIP'ed logs folder.

 

Here is what I did:

 

1. Cleaned up Logs folder so no old info is present.

2. Launched DCS: World.

3. Loaded a simple P-51D ramp-start mission.

4. Hit ESC and hit "Quit".

5. It started loading the main menu again and at ~96% progress crashed.

 

Can reproduce this crash all the time.

Logs.zip

Edited October 5, 2012 by Simas

[Corrigan]

For low water settings yes, the water was changed back to 1.2.0 water - But that's it AFAIK.

 

Nate

 

Roger that, that's good news.

[SkateZilla]

The new water is gone in version 6192 when set to low....thats a shame...I thought it looked great and didnt cause me any fps loss... another step backwards ED.

But noticed big fps increase in 6192.

 

 

You state something new is gone, claim it had no hit on Fr/PS.

 

But then you state your Fr/PS is now back to what it was before that something new is introduced.

 

Apparently the Water DOES have an effect on the Fr/PS.

 

:joystick:

[Corrigan]

You state something new is gone, claim it had no hit on Fr/PS.

 

But then you state your Fr/PS is now back to what it was before that something new is introduced.

 

Apparently the Water DOES have an effect on the Fr/PS.

 

:joystick:

 

Non sequitur. You're assuming only the water has changed, which is a bit stupid.

[Nate--IRL--]

Apparently the Water DOES have an effect on the Fr/PS.

 

The water DID have an effect - not any longer. It was only part of the overall problem however.

 

Nate

[SkateZilla]

Non sequitur. You're assuming only the water has changed, which is a bit stupid.

 

technically, the entire terrain engine could have been changed... the new water could have been a feature of new shaders etc, and were prolly not limited to the water, turning them off at lower settings = old water.

 

 

So if I Run: GFX Settings:

MED Preset, Text.=Med, Scene=Med, Civ Traffic=Hi, Visibility Range=Med, Water=Med, Heat Blur=On, Shadow=Med,

6048x1080, 5.6 Aspect Ratio, Monitors: Custom LUA (1 Viewport, GUI Center Screen only), Pit Displays=256px, MSAA=2x, HDR=Off.

VSYNC OFF, TREE SHADOWS OFF, FULL SCREEN OFF, Cockpit Shadows OFF, TSSAA Off

 

Will I retain the water or should I try and increase my settings some. Havent updated yet (in office)

[c0ff]

Attached my ZIP'ed logs folder.

 

EDIT: works now.

 

Thanks for the logs.

Edited October 5, 2012 by c0ff

[Nate--IRL--]

"Invalid Attachment specified. If you followed a valid link, please notify the administrator..."

Notified the admin.

 

Works for me.

 

Nate

[ginoc1]

FPS back here too with 6192!!! w/ vsync enabled fluctuates between 60 and 53 regularly...dipping as low as 40 in A-10 Instant Mission - much better than 42-45 avg before with dips in mid 30s. But after trying a trick I use in FSX I'm in smoothness heaven...limited FPS to 30 in graphics.cfg, then in nVidia Inspector (latest version) created DCS World profile and set vSync to Standard and "1/2 Refresh Rate". Smooth as a baby's ass...no stutters, no dips, TrackIR like silk...only thing I disabled was mirrors as the lower frame rate of the mirror image creates a "choppy" visual to me a lowers immersion - preference only. Thanks a million ED!!!!

[funkyb]

Well whatever has changed my performance is still in the tank. I tried 1.2.1 last night in the p-51D at various settings. Using quad1, I could play mostly on high (except MSAA is 4x) and it works very well. In 1.2.0 I had to dial down a few things down, water to low, shadows to low, and MSAA to 2x to retain performance in the ballpark of what I have with quad1.

 

Last night was my first time in 1.2.1 (and yes I installed the most recent auto-update), and even with every setting on it's minimum possible value (all low, all distances to minimum, TSSAA off, MSAA off...everything at minimum), I spent the entire session bouncing between a minimum of 10 FPS and a maximum 22 FPS with an average between 17-18 FPS. Unplayable, and there's nothing left to drop. sadface.jpg

 

System Specs:

i5-2500k @ 4.2GHz

8GB Gskill ripjaw DDR3-1800

2 x Sapphire/ATI 6970 2GB in Xfire (Cat v12.8 drivers)

1200W Cooler Master GOLD PSU

2 x 120 GB HyperX SATAIII SSDs in Raid 0

3 x ASUS 23.6" LCDs @ 5760x1080 (not in eyefinity, I use DCS-built in monitorconfig)

 

I'm able to run everything else I throw at this on great settings with good performance, even in (eyefinity or other) triple head configurations. Skyrim, BF3, Crysis II, Just Cause 2, etc... no problem. Hopefully this will get worked out. I miss running the newer DCS modules but will have to stick to quad1 until FPS improves.

[Nate--IRL--]

Well whatever has changed my performance is still in the tank. I tried 1.2.1 last night .

 

Are you using 1.2.1.6192? It will be displayed on the bottom right of the Main Menu screen. It was updated this morning. Use the Update icon in the DCS entry of the windows start menu.

 

Nate

[SkateZilla]

XFire should be disabled, and Cat 12.8 are the worst of the Upper 12.x Drivers, 12.7 Beta I think had the best overall ratings by people that benchmark and test them.

[funkyb]

Are you using 1.2.1.6192? It will be displayed on the bottom right of the Main Menu screen. It was updated this morning. Use the Update icon in the DCS entry of the windows start menu.

 

Nate

 

I'm using x6148, my post was regarding last night. I'll try again after work today, and I should have added to the original post that I'm pleased ED is working hard to address this. I'm sure they're pulling their hair out as much as everyone else has been, and recognize this stuff isn't easy.

 

XFire should be disabled, and Cat 12.8 are the worst of the Upper 12.x Drivers, 12.7 Beta I think had the best overall ratings by people that benchmark and test them.

 

I have no problem reverting to the 12.7 Beta and will try that as well. Concerning x-fire. - I've read that before (disabling xfire in DCS), but in prior versions my personal experience is that it worked better (at least in quad1 and 1.2.0). I'll also try disabling x-fire (but would hope sometime we can see support for it, man that second GPU makes a difference when it's used right.)

Edited October 5, 2012 by funkyb

[funkyb]

I'm using x6148, my post was regarding last night. I'll try again after work today, and I should have added to the original post that I'm pleased ED is working hard to address this. I'm sure they're pulling their hair out as much as everyone else has been, and recognize this stuff isn't easy.

 

 

XFire should be disabled, and Cat 12.8 are the worst of the Upper 12.x Drivers, 12.7 Beta I think had the best overall ratings by people that benchmark and test them.

 

I have no problem reverting to the 12.7 Beta and will try that as well. Concerning x-fire. - I've read that before (disabling xfire in DCS), but in prior versions my personal experience is that it worked better (at least in quad1 and 1.2.0). I'll also try disabling x-fire (but would hope sometime we can see support for it, man that second GPU makes a difference when it's used right.)

[Gunnergolly]

Have they got a plan to optimise the explosions of the CBU style bombs and their Russian counterparts ?.

 

They reduce my FPS to about 7 for approx 10 seconds whenever they explode... other than that i'm getting pretty decent performance out of 1.21.

 

Thanks....

[BIGNEWY]

1.2.1.6192 GREAT Improvement, outstanding work ED

[USSR_Rik]

Attached my ZIP'ed logs folder.

 

Here is what I did:

 

1. Cleaned up Logs folder so no old info is present.

2. Launched DCS: World.

3. Loaded a simple P-51D ramp-start mission.

4. Hit ESC and hit "Quit".

5. It started loading the main menu again and at ~96% progress crashed.

 

Can reproduce this crash all the time.

Could you attach this mission (or do you use Quick mission 'Cold start Vasiani' )?

[aceviper]

The "new water" that came with 1.21 is gone whatever setting its on.