Cockpitshadows and HDR for Win x32

[asparagin]

Apparently Win x32 (x86) systems won't get so much love from ED from now on and if you have one, you have noticed that by 1.0.0.8 HDR, cockpit shadows and high settings are not selectable.

I was going to change to win 7 x64 when I'll update my system, but until then:

 

********

If you still want HDR and cockpit shadows:

 

1. back up options.lua from C:\Users\*name*\Saved Games\DCS Warthog\Config

 

2. open options.lua

 

Change the following:

 

["HDR"] = 0, to

["HDR"] = 2, (2 is right for me)

 

["cockpitShadows"] = false, to

["cockpitShadows"] = true,

 

and

shadows have to be on, so 2 for eg.:

 

["shadows"] = 2,

 

3. save file, and afterwards: right-click on the options.lua file / proprieties / read-only: on because DCS is trying to modify it, afterwards.

 

 

PS: on your own risk, since ED didn't add it with the release.

Edited June 3, 2011 by asparagin

[const2k]

This only works for shadows and HDR, but not for high textures:(

[REL]

Hey asparagin

 

First thanks !

 

I don't have those options:

3. save file, and afterwards: right-click on the options.lua file / options / write-protected: on because DCS is trying to modify it, afterwards.

 

Can you explain more please ?

[asparagin]

This only works for shadows and HDR, but not for high textures:(

 

Didn't try it myself, have you changed "textures" to a higher number 2 or 3 and it doesn't work?

[const2k]

I've set it to 2 - still medium tex, then to 3 - no textures at all...

[asparagin]

Hey asparagin

 

First thanks !

 

I don't have those options:

3. save file, and afterwards: right-click on the options.lua file / options / write-protected: on because DCS is trying to modify it, afterwards.

 

Can you explain more please ?

 

Ahh, it's not "options" but "proprieties"

and "read-only" should be on

(I have a german system, and I was lost in translation :D)

Edited June 2, 2011 by asparagin

[REL]

Eh ... did that ... TNX

[Wags]

Use at your own risk. We do not advise because it can often lead to game instability and dropped textures on 32 bit systems.

[Panzertard]

Tez replied on this in another thread as well gents. You're likely to see crashes. So either it's time to think about 64bit and a bit more memory, or leave it as it is.

High settings require a lot of memory. Microsoft has made 32bit Windows to allocate up to 3GB of memory to applications with /3GB or increaseuserva switches. That isn't enough for Warthog on high settings.

[asparagin]

Yep, got it, I use only HDR and cockpit shadows, and it's going ok so far. I'll let you know if I get crashes.

I also have the 3G switch enabled.

Edited June 3, 2011 by asparagin

[Tez]

I think on most powerful systems high settings in 32bit will be rather stable. Until you go for a big mission or online (or both at the same time).

[Nate--IRL--]

Yep, any big mission (Any Campaign or large MG mission) will have DCS crashing randomly in a 32bit OS from memory exhaustion. The 3gb tweak does help, but does not eliminate the exhaustion of memory.

 

Nate

[asparagin]

It figures, even at 1.0.0.7, there were problems with x32.

At the moment I see no reasons against x64 but when I made the jump to W7, there were still some compatibility problems (software generally), and I didn't want a bigger risk so I installed x32.

So I understand the decision not to keep the support for x32. It doesn't strike me actually, because I own also x64, but I'll install it with the pc upgrade (:v: hope it's soon).

Anyway at least I can have a taste of the cockpit shadows now.

[Sabadin]

Use at your own risk. We do not advise because it can often lead to game instability and dropped textures on 32 bit systems.

 

I know you guys don't like giving firm answers, but hopefully the team can look into adding a seperate setting for cockpit textures so anyone unable to make the jump from 32bit can still at least keep the cockpit sharp and clear?

[Nate--IRL--]

I know you guys don't like giving firm answers, but hopefully the team can look into adding a seperate setting for cockpit textures so anyone unable to make the jump from 32bit can still at least keep the cockpit sharp and clear?

 

I have highlighted this, but I've no idea if it will happen.

 

Nate

[Aries]

Really great... :doh:

Now the only executable where my FacetrackNoIR (with my specifically acquired PS3 Eye) worked, has cut-back graphics...

 

Who asked ya to cut the 32bit graphics anyway... wasn't it good enough to leave for the user to choose? :(

 

Bah...

[sebro83]

Same for me. Running w7 64bit on a 64bit system but falling back to the 32bit dcs-executable for the freetrack-"support". And it's not even mentioned in the patch-notes. Maybe most customers won't notice or what?

 

This is finally a real slap in the face for anyone not using trackir but instead an open source solution. And it's the first time I'm really annyoed so as to post here. Whatever, enough said - I'll stop the whining.

[Nate--IRL--]

Same for me. Running w7 64bit on a 64bit system but falling back to the 32bit dcs-executable for the freetrack-"support". And it's not even mentioned in the patch-notes. Maybe most customers won't notice or what?

 

This is finally a real slap in the face for anyone not using trackir but instead an open source solution. And it's the first time I'm really annyoed so as to post here. Whatever, enough said - I'll stop the whining.

 

ED has released an API for 3rd party developers (like freetrack) to integrate native support for DCS. So hopefully this will be less of an issue in the future.

 

Nate

[Crashdown]

Lovely.

The way I set up my game I managed to have a smooth game experience both in SP and online even though I am limited by my 32-bit system.

But now, thanks to the new patch, the game looks horrid and I have to strain my eyes to read what the labes in my cockpit says.

I understand not wanting to bother support an old OS, but with a bit of tweaking, us 32-bit users could run this well with a good graphical level even if it wasn't supported. So why was this changed? Why instead of not supporting you are actively penalizing us with this patch?

[asparagin]

I understand not wanting to bother support an old OS, but with a bit of tweaking, us 32-bit users could run this well with a good graphical level even if it wasn't supported. So why was this changed? Why instead of not supporting you are actively penalizing us with this patch?

 

The blurry cockpit textures on medium is being worked on, and hopefully solved.

 

About the x32 systems: I suppose if they let the High textures for everyone, imagine how many would start complaining about crashes.

[Crashdown]

The blurry cockpit textures on medium is being worked on, and hopefully solved.

Well that good to hear! I honestly don't mind playing on a lower than maximum graphical setting for most games, even when I have the hardware to do so. But those blurry textures break the game for me. It's only a incredibly small part of the game, and I've got the cockpit pretty much memorized, so for the most part I can operate the A-10 blindfolded, but it's there.

 

 

 

About the x32 systems: I suppose if they let the High textures for everyone, imagine how many would start complaining about crashes.

You do have a point, but ED could simply make it so that 32-bit users are warned that High mode is not stable/supported/recommended on 32-bit systems and that any complaints about crashes/stuttering/armageddon caused by using those will be ignored (and possibly laughed at). :D

[secretkon8700]

Could be a noob question, but i'll rifle it anyway, my OS is 64bit, but I run the x86 version for facetrack, is DCS making use of all available RAM (4Gb)??

[BlackRazor]

Could be a noob question, but i'll rifle it anyway, my OS is 64bit, but I run the x86 version for facetrack, is DCS making use of all available RAM (4Gb)??

 

If the executable has the /LARGEADDRESSAWARE flag set then it can use up to 4GB of virtual memory; however I don't have the x86 executable installed on my system so I don't know whether this is the case or not.

 

EDIT: also notice that the limit discussed in this thread is about virtual memory, not about physical memory (i.e. RAM memory). They are two completely different concepts that have almost nothing in common.

[winz]

Just to add to BlackRazor, the DCS executable is /LARGEADDRESSAWARE.