Redux & W7...

[Ciaran]

Just a note, the linked sresolution fix seems -for me at least- not to work with the campaign map for Redux.
Custom battles are fine, however, using the posted ddraw.dll results in an error message when trying it with the redux campaign map.
So, those as unfortunate as me will still have to reboot with reduced ram to play redux on any higher screen resolution.
I had hoped that using 1003 would solve that problem (so far I played at v1002), as it did apparently for you, Axalon; alas, no such luck, and I´m afraid I can´t comprehend what you mean by:

On the VI/v.2.01- engine I have 2034MB set by default in game-options

I´m certain I´m missing something obvious...

[Axalon]

Hello Ciaran,

Um... Can you somehow succesfully use the ddraw.dll file and get the desired resolutions while using the original MTW-map or any other map (from some mod)? If not then it is a matter of hardware and drivers - and not Redux. If you are indeed able somehow to run other stuff (successfully) then specify which map it is (and relevant mod etc.).

I have not had any problems at all with Ram and resolution in Redux (v.1002 or 1003), not on my rig, regardless the settings I use. Now, if I install VI from scratch (and then apply Redux on top), and do not cange the Ram settings somehow in options, I will then get 2034 MB in Ram in VI (and 50 on pyrotechnics. All this will more then suffice to play the game on excellent terms). That was also what I meant....

- A

[Nagnar]

Hello Axalon!
I thought i'd post this because Ciaran hasn't replied and i have his same problem.

The Vanilla MTW Campaign map doesn't crash and i can't say for any other mods because I don't own a copy of VI.
But it would therefore appear that the problem lies with the Redux campaign map.

If you could work out a fix for Redux so that people with this problem could use Redux and higher resolutions without the full of hassle alternate fix then I would much appreciate it.

-Nagnar

[Axalon]

Hello Nagnar,

Let's first make sure that Redux somehow actually is the problem here (which I still doubt was actually the case with Ciaran). Make a copy of your (entire) raw MTW-install and place it somewhere else. Once that is done. Check out for sure that raw MTW really runs without such (or any) problems on your hardware at all. Once that is done, take copy of the Redux campaign map-file and replace the original campaign map-file (on that new copy of your raw MTW install) and see what happens. If that can not run as successfully as with the original file in place - then it might be the Redux file. Until we know that for sure, it is basically pointless to do or attempt any possible fixes for it.

The file is located: "?:\?\"your game directory"\Textures\campmap" and it is called: "MapTex2.tga"

- A

[Nagnar]

Okay I've tried that and some other combinations.
So this is using a copy of my Vanilla MTW folder and my Redux folder. The results are all when entering the campaign map, everything else works fine under any conditions.

Vanilla MTW:
without ddraw.dll - Works
with ddraw.dll - Works

Vanilla MTW + Redux MapTex2.tga:
without ddraw.dll - Works
with ddraw.dll - CTD

Redux
without ddraw.dll - Works
with ddraw.dll - Error and crash to "In-Game Menu"

Redux + Vanilla MTW MapTex2.tga
without ddraw.dll - Works
with ddraw.dll - Error and crash to "In-Game Menu"

-Nagnar

Edit: I found the answer after doing some replacement of individual files in Textures/campmap. Both MapTex.tga and MapTex2.tga cause the error and crash to menu both independently and together. Unfortunately though, Its unplayable with Vanilla MTW's copies of those files as many provinces and sea regions in the campaign are inaccessible.

[Axalon]

Just a note, the linked sresolution fix seems -for me at least- not to work with the campaign map for Redux. Custom battles are fine, however, using the posted ddraw.dll results in an error message when trying it with the redux campaign map.

I have now tried the "ddraw.dll"-file as well, and it does not seem to work with Redux at all, the same error happens to me. This in turn provides us with the obvious answer that the problem is not with Redux as such but using it in combination with the "ddraw.dll". The obvious solution is to not use the "ddraw.dll" as then Redux will work as supposed to... Thus I take back any previous scepticism on Ciaran's post as it clearly appear to be valid in this outlined context after all.

***

Nagnar... The "ddraw.dll"-file is evidently not designed with mods in mind - this obviously includes Redux as well. Redux's extreme use of alternative files and the "ddraw.dll"-files seemingly strict dependencies on the original MapTex-files (somehow, I don't know how) is in direct conflict. The solution here is obviously to stay away from the "ddraw.dll" until it gets mod-friendly, as I doubt the current version will get along with any mod anywhere that actually changes the "MapTex2.tga"-file somehow. If it actually does, by all means point out which one...

I would imagine that we - or rather you - are thus left with the alternatives to either play Redux without the "ddraw.dll" or play raw MTW with it. There is seemingly no compromise to be had on that - as is. This until the creator of that "ddraw.dll"-file makes another version that does work with mods - including Redux. By all means forward such a request to the man actually responsible for the ddraw-file at any time. In the mean time, Redux obviously works without it, so I basically fail to see an actual problem here. ...?...

- A

[Nagnar]

Thanks for clearing this all up.

-Nagnar