Engine.ini

[rags]

Hello,

New to these boards. I've bought all three games now, though I didn't play 1503 much at all.

Anyway I was missing being able to turn off some of the warning and event messages. So I went poking around in the Engine.ini which has these settings:

<FilterEventMsg>0</>
<FilterEconomyMsg>1</>
<FilterDiplomacyMsg>0</>
<FilterResidentMsg>0</>
<FilterExplorationMsg>0</>
<FilterResearchMsg>0</>
<FilterMilitaryMsg>0</>

So as you can see I'm currently experimenting with the Economy messages off, I think. I was wondering if anyone else has been experimenting with the ini, and if we might be able to get a sticky on the forums here where we could all compile our results as we mess with it. Kind of an INI knowledge base. I'll post back once i've figured more of it out, but don't expect it be soon since I'm busy playing :)

Oh and I also wrote a silly little VB app to make editing the thing easier. Who decided all of it should be crammed onto one line anyway? is there a fansite around where I could upload it incase others want to use it?

Thank you for your time.

-Rags

[Omikronman]

There are several tips in the forum to use the ini file to change the screen mode and size!

[RoadRunner]

Well, isn't it easier and more secure to set that via the Options -> Graphics menu? :wink:

I would not recommend to change the *.ini files. If you have technical problems with the game later, you will probably never think about the amended settings...

[rags]

You may feel free to mess with the ini til your hearts content for 2 reasons.

1) if you mess something up or somehow cause the ini to be 'invalid', 1701 will ignore your settings and return to default.

2) at anytime you can delete the ini and 1701 will create a new one with default settings.

under both of the scenarios the defaulted ini will be saved replacing your broken or missing one.

Actually there is some case where my editor thingy is writing a bad value which causes 1701 to return to defaults, I haven't taken time to track it down yet. I'll get to it in the next few days i think.

-Rags

[Sokratesz]

is it possible to have the game spread over 2 displays? I've got 2 monitors and would like to use both.

[rags]

I dunno if you can do that with 1701.

I always go to the wide screen gaming forum when i have trouble with that kind of stuff.

http://www.widescreengamingforum.com/wiki/index.php?title=Main_Page

1701 is so new here they probably won't have anything on it yet, but they might. Regardless you should be able to find good info on how to go about something like that.

Good Luck!

-Rags

[RoadRunner]

I think that's also a nVidia Problem. In the manual (http://de.download.nvidia.com/Windows/93.71/93.71_ForceWare_Release_notes.pdf) for the new driver (93.71) you may find the following quotes:

- multiple monitors:
DirectX Applications Run Only on Single Display Even in Multiview Mode
• Problem
When running DirectX applications in fullscreen mode on an NVIDIA Multiview system, the application appears on only one display instead of all the displays. A Multiview system consists of a NVIDIA Quadro NVS series graphics card with multiple monitors connected and multiview mode enabled.
• Explanation
The problem occurs only with DirectX /Direct3D applications that use fullscreen exclusive mode. In order to support these applications, the driver must switch to single display mode and blank out the other displays. In scenarios that require multiview functionality—such as when using screen savers—NVIDIA recommends using non-DirectX/Direct3D applications.

- Antialiasing issues
Antialiasing Problems With Certain Applications
Antialiasing in the NVIDIA Direct3D driver requires each new frame to be rendered from scratch. This requirement adversely affects applications that render only that portion of the content that has changed since the last frame. A common symptom of this problem is geometric structures that incorrectly disappear and re-appear as the scene shifts.

- DualCore-CPU issues
There may be intermittent application compatibility issues with dual core CPUs.
If you experience this issue, first make sure you have downloaded and installed the dual core patches from your CPU manufacturer and from Microsoft. The Microsoft knowledge base article is available at:http://support.microsoft.com/?id=896256 . If you still experience problems you can attempt to work around these by toggling off NVIDIA’s multithread optimizations using the following instructions:

1 Launch regedit and determine the current primary display card by looking in
HKey_Local_Machine\Hardware\DeviceMap\Video
and note the GUID (global unique identifier assigned by Windows), which is the long string in brackets { } at the end of the entry "\device\video0".

2 Look in
HKey_Local_Machine\SYSTEM\CurrentControlSet\Contro l\Video\{GUID}\0000
where {GUID} is the number derived from the previous step.

3 Open the "0000" directory and create a new DWORD called OGL_ThreadControl and give it a value of 2. This will disable multithreading in the driver for all OpenGL applications.

4 If you want to disable driver multithreading for all Direct3D applications– In the same "0000" directory, create a new DWORD called WTD_EXECMODEL and give it a value of 0.