INI File
INI File
Two questions:
First, I have two drives on my computer, C: for operating system and E: for games. I loaded TOAW IV on my E: drive, but when I looked in the folder for OPART 4.ini, I could not find it. I found it on the C: drive in a folder with the following other folders: “Graphics Override”, “My Fonts”, “Saves”, “Scenarios”, and “sound”. Other files in the main folder are OPART 4 Fonts, affinity, toa.cfg, TOAWEquipment.eqp, TOAWEquipment.nqp, toawlog, and toawWeapons. Is this the where these files are supposed to be? I’ve not encountered installations that involved two different drives.
Second, in the OPART 4. ini file as shown in the manual, there are the following parameters:
ChangeScreenResolution=N
ScreenY=768
ScreenX=1024
These parameters are not in the OPART 4.ini file that I have. Is this something that I need to add to the ini file? Shouldn’t they already be there?
I would appreciate any guidance that can be provided. Thank you.
TomC
First, I have two drives on my computer, C: for operating system and E: for games. I loaded TOAW IV on my E: drive, but when I looked in the folder for OPART 4.ini, I could not find it. I found it on the C: drive in a folder with the following other folders: “Graphics Override”, “My Fonts”, “Saves”, “Scenarios”, and “sound”. Other files in the main folder are OPART 4 Fonts, affinity, toa.cfg, TOAWEquipment.eqp, TOAWEquipment.nqp, toawlog, and toawWeapons. Is this the where these files are supposed to be? I’ve not encountered installations that involved two different drives.
Second, in the OPART 4. ini file as shown in the manual, there are the following parameters:
ChangeScreenResolution=N
ScreenY=768
ScreenX=1024
These parameters are not in the OPART 4.ini file that I have. Is this something that I need to add to the ini file? Shouldn’t they already be there?
I would appreciate any guidance that can be provided. Thank you.
TomC
-
- Posts: 43
- Joined: Fri Nov 17, 2017 2:03 am
RE: INI File
That's right where they're supposed to be! Those "Graphics Override," "Scenarios," and "Saves" folders and so on can be added to and otherwise changed by the user, so TOAWIV - like many other games - will store those user-accessible parts in that user's "My Documents" folder. If you have administrator rights on your PC, you have full access to the game's program files (In this case, the stuff on your E: drive), so you'd be able to save games there or drop new scenarios/customizations into that folder no trouble - but for non-admin users, Program Files is locked down by default, and so a normal user couldn't save or change settings since they technically wouldn't have write-access to the folder. One of the few places a standard-rights user has full write access is their own User folder, so Windows games (and many other programs, for that matter) started saving that kind of "user data" there.
It's not too unusual these days, and shouldn't cause any trouble! Theoretically, you'd never have to manipulate or change anything on your E: drive to affect the game - user settings (those INI files) and the scenarios are stored with the user's stuff in My Docs. [:)]
(edit: Gosh, that got kinda long-winded, just let me know if that doesn't make much sense!)
---
As for the OPART 4.ini, you're right - they're not there by default, so you can just add them to the end of the file! It seems there are a few switches like that that, while they would have an effect if added to the INI, aren't added by default. There's a list at the back of the manual of all possible switches, I believe, if you have any interest in seeing what you may be missing.
Anecdotally, those three are the only settings I've had to add myself!
It's not too unusual these days, and shouldn't cause any trouble! Theoretically, you'd never have to manipulate or change anything on your E: drive to affect the game - user settings (those INI files) and the scenarios are stored with the user's stuff in My Docs. [:)]
(edit: Gosh, that got kinda long-winded, just let me know if that doesn't make much sense!)
---
As for the OPART 4.ini, you're right - they're not there by default, so you can just add them to the end of the file! It seems there are a few switches like that that, while they would have an effect if added to the INI, aren't added by default. There's a list at the back of the manual of all possible switches, I believe, if you have any interest in seeing what you may be missing.
Anecdotally, those three are the only settings I've had to add myself!
RE: INI File
Yeah, lots of games use the "My Games" folder for save-games and config, or they don't behave and use the "Documents" folder directly. Problem is, some of these folders tend to be huge. And not all, including me, wants to save all that on the C: drive, for OS backup purposes (to make the image smaller).
For example, my Battlefront folder has a lot of mods and save-games and is over 4GB in size.
So what I've done is made a "symlink" or "junction link" to map the My Games folder to another drive, the same drive I have games on, with plenty of space.
You can use this tool below or just the mklink command from an elevated command prompt.
https://sourceforge.net/projects/symlink-creator/
Another way (probably easier) is to use the method described here:
https://support.microsoft.com/en-us/hel ... nts-folder
Although not sure if that works when some badly written applications use hard-coded paths...
For example, my Battlefront folder has a lot of mods and save-games and is over 4GB in size.
So what I've done is made a "symlink" or "junction link" to map the My Games folder to another drive, the same drive I have games on, with plenty of space.
You can use this tool below or just the mklink command from an elevated command prompt.
https://sourceforge.net/projects/symlink-creator/
Another way (probably easier) is to use the method described here:
https://support.microsoft.com/en-us/hel ... nts-folder
Although not sure if that works when some badly written applications use hard-coded paths...
OUW (Order of the Upgrade Wars)

There are folks out there with way too much time on their hands.
- Norm Koger

There are folks out there with way too much time on their hands.
- Norm Koger
RE: INI File
Thank you, Aperfecturkel and Shadrach. Just goes to show you how long its been since I've bought a new game. I am looking forward to diving into the game. Again thank you.
Tomc
Tomc
RE: INI File
I cannot find my .ini files, he said sheepishly.... I searched every folder. How bad am I???
I would appreciate any help.
I would appreciate any help.
Richard
RE: INI File
They can be found in:
"C:\Users\USERNAME\Documents\My Games\The Operational Art of War IV"
Where USERNAME is, well, your User Name on your PC [;)].
"C:\Users\USERNAME\Documents\My Games\The Operational Art of War IV"
Where USERNAME is, well, your User Name on your PC [;)].
RE: INI File
Seems like a good place to post my questions about Opart 4.ini
What are these values:
HugeIcons, basicDefaults, experimentalAIP1, experimentalAIP2, and MacroTerrain. Their manual descriptions are ambiguous and I can't find them through forum search.
What are these values:
HugeIcons, basicDefaults, experimentalAIP1, experimentalAIP2, and MacroTerrain. Their manual descriptions are ambiguous and I can't find them through forum search.
RE: INI File
Thanks piotre, I also had to go into view/hidden files to make the ini files view-able. Now I will poke around to see if there is a setting that will stop the constant crashing. If not, I may just go back to toaw III.
Richard
RE: INI File
ORIGINAL: mccartyg
Seems like a good place to post my questions about Opart 4.ini
What are these values:
HugeIcons, basicDefaults, experimentalAIP1, experimentalAIP2, and MacroTerrain. Their manual descriptions are ambiguous and I can't find them through forum search.
Manual page 171-172:
experimentalAIP2=Y For Ralph to do AI testing
experimentalAIP1=Y For Ralph to do AI testing
basicDefaults=N
MacroTerrain=N
The first two seem to be for the developer for testing, not for gameplay.
The last two are not defined.
So you would probably ignore them unless you know what you are doing.
RE: INI File
ORIGINAL: rtropp
Now I will poke around to see if there is a setting that will stop the constant crashing. If not, I may just go back to toaw III.
rtropp, regarding your calls above and in this thread, your crashes can be caused by a software or hardware issue. This forum used to be watched by users who can help with hardware and driver related issues (dxdiag etc.) to begin with. I hope one of them drops by and can help you see if that is the cause, and then look further specifically at your TOAW IV installation etc.
-
- Posts: 4876
- Joined: Sun Feb 10, 2008 7:37 pm
- Location: Germany
- Contact:
RE: INI File
Oberst,
Thanks, attached is the crash log. I cannot find the dxdiag.
...uh, I don't know how to attach a file or what "dump"means.
Boy do I feel silly..
wait.. there it is... whew!!
crashlog is attached.
Thanks, attached is the crash log. I cannot find the dxdiag.
...uh, I don't know how to attach a file or what "dump"means.
Boy do I feel silly..
wait.. there it is... whew!!
crashlog is attached.
- Attachments
-
- crashLog.txt
- (61.14 KiB) Downloaded 5 times
Richard
-
- Posts: 4876
- Joined: Sun Feb 10, 2008 7:37 pm
- Location: Germany
- Contact:
RE: INI File
Oberst,
attached is the dxdiag file.
Thank you
attached is the dxdiag file.
Thank you
- Attachments
-
- DxDiag.txt
- (83.21 KiB) Downloaded 6 times
Richard
RE: INI File
Manual page 171-172:
experimentalAIP2=Y For Ralph to do AI testing
experimentalAIP1=Y For Ralph to do AI testing
basicDefaults=N
MacroTerrain=N
The first two seem to be for the developer for testing, not for gameplay.
The last two are not defined.
So you would probably ignore them unless you know what you are doing.
I guess if I ask what uberdude is now I'll be told that it's super simpleton mode. Was going for actual definitions as I mentioned I've already read the very undiscriptive manual lines and have searched the forums as well. Anyone know what these ini values mean exactly?
-
- Posts: 4876
- Joined: Sun Feb 10, 2008 7:37 pm
- Location: Germany
- Contact:
RE: INI File
Richard,ORIGINAL: rtropp
Oberst,
attached is the dxdiag file.
Thank you
your system is far superior than mine! Now, you gut multiple core CPU... me just dual and 4GB RAM. You got the latest beta, 4.0.1.23, aye? As for some tweak in the Opart 4.ini, did you switch multicpu=y?
Klink, Oberst
-
- Posts: 4876
- Joined: Sun Feb 10, 2008 7:37 pm
- Location: Germany
- Contact:
RE: INI File
Geoff,ORIGINAL: mccartyg
Manual page 171-172:
experimentalAIP2=Y For Ralph to do AI testing
experimentalAIP1=Y For Ralph to do AI testing
basicDefaults=N
MacroTerrain=N
The first two seem to be for the developer for testing, not for gameplay.
The last two are not defined.
So you would probably ignore them unless you know what you are doing.
I guess if I ask what uberdude is now I'll be told that it's super simpleton mode. Was going for actual definitions as I mentioned I've already read the very undiscriptive manual lines and have searched the forums as well. Anyone know what these ini values mean exactly?
see my post fb.asp?m=2742936 from 2011, just digged it up. It will explain everything. After all... When in doubt, ask the Kraut!
And here for the public, too

nodelay – Useful for debugging scenarios in computer vs. computer play mode, this option turns off many of the small timer controlled delays and animations in the game. The effect is most noticeable on faster machines.
noupdate - Useful for debugging scenarios in computer vs. computer play mode, this option turns off many of the screen updates in the game. The effect is most noticeable on slower machines. This option should not be used when playing the game, as some of the updates are necessary for normal play purposes. A combination of nodelay and noupdate can speed computer vs. computer scenario test dramatically.
nosound – Turn off all sound.
norandom – Turns off system time based initialization of the random number generator used in TOAW.
polog – Turns on the programmed opponent logging feature. This will generate a po_log.txt file in your game directory. The log file is a detailed record of programmed opponent decision making during a game.
toawlog – Turns on the general game logging feature. This will generate a toaw_log.txt file in your game directory. The log file is a detailed record of many game management functions, including loading and unloading of resources and combat resolution.
nointro – Turns the introductory cinematic off.
uberdude – Increases the amount of feedback from the event engine and other game functions for debug purposes. Many event engine actions that leave no trace in normal mode will fully document themselves in the news report if you use the uberdude switch. This can be used during normal play, but is really intended for scenario designer use. It has a tendency to clutter the news report and certain graphics areas with information that isn’t needed during normal play.
Klink, Oberst
RE: INI File
What of HugeIcons, basicDefaults, experimentalAIP1, experimentalAIP2, and MacroTerrain though? It isn't really material to gameplay but, I'd just like to know.
-
- Posts: 4876
- Joined: Sun Feb 10, 2008 7:37 pm
- Location: Germany
- Contact:
RE: INI File
As per JPJ's answer earlier and the manuel:ORIGINAL: mccartyg
What of HugeIcons, basicDefaults, experimentalAIP1, experimentalAIP2, and MacroTerrain though? It isn't really material to gameplay but, I'd just like to know.
Manual page 171-172:
experimentalAIP2=Y For Ralph to do AI testing
experimentalAIP1=Y For Ralph to do AI testing
basicDefaults=N
MacroTerrain=N
The first two seem to be for the developer for testing, not for gameplay.
The last two are not defined. Therefore, no effect(s) and leftovers from Norm's code
So you would probably ignore them unless you know what you are doing.
HugeIcons=Y does what it says - The unit icons in the unit information panel are larger

Klink, Oberst

- Attachments
-
- cats.jpg (95.86 KiB) Viewed 418 times
- ralphtricky
- Posts: 6675
- Joined: Sun Jul 27, 2003 4:05 am
- Location: Colorado Springs
- Contact:
RE: INI File
BasicDefaults helps control the numbers on the icons.
MacroTerrain should set the combat background to the old Macro Terrain instead of the new Hexes.
MacroTerrain should set the combat background to the old Macro Terrain instead of the new Hexes.
Ralph Trickey
TOAW IV Programmer
Blog: http://operationalwarfare.com
---
My comments are my own, and do not represent the views of any other person or entity. Nothing that I say should be construed in any way as a promise of anything.
TOAW IV Programmer
Blog: http://operationalwarfare.com
---
My comments are my own, and do not represent the views of any other person or entity. Nothing that I say should be construed in any way as a promise of anything.