Starting 3Wave overwrites q3config.cfg with default

Locked
almo
Posts: 7
Joined: Tue Apr 15, 2014 4:12 pm

Starting 3Wave overwrites q3config.cfg with default

Post by almo »

My 3wave icon has this:

Target: D:\Games\Q3\quake3.exe +set fs_game threewave +set com_hunkmegs 128 +set com_zonemegs 32
Start in: D:\Games\Q3

When I start it like this, it overwrites q3config.cfg in both the threewave and baseq3 directories.

I'm on Windows 7, and I have the shortcut set to run as administrator, and in Compatibility mode for Win XP SP2.

Any idea on why it's doing that? :(
obsidian
Posts: 10970
Joined: Mon Feb 04, 2002 8:00 am

Re: Starting 3Wave overwrites q3config.cfg with default

Post by obsidian »

The game is supposed to have write access to q3config.cfg... in the case when you change settings through the menu, it saves those changes to that file. Normally, you would have your custom binds in something like "custombinds.cfg" and launch the game to read it, adding into your startup shortcut, "+exec custombinds.cfg".

The alternative is forcing your q3config.cfg to be read only, by right clicking the file in Windows, properties, and check the read-only option. Note that this forces Q3 to not be able to write to the file at all, so changing settings in the menus won't work and it might have other consequences.
[size=85][url=http://gtkradiant.com]GtkRadiant[/url] | [url=http://q3map2.robotrenegade.com]Q3Map2[/url] | [url=http://q3map2.robotrenegade.com/docs/shader_manual/]Shader Manual[/url][/size]
almo
Posts: 7
Joined: Tue Apr 15, 2014 4:12 pm

Re: Starting 3Wave overwrites q3config.cfg with default

Post by almo »

Ok, I'll try that. Thanks.

I find this odd, since I don't remember it doing this last time I was playing, but that was on XP about 3 years ago.
almo
Posts: 7
Joined: Tue Apr 15, 2014 4:12 pm

Re: Starting 3Wave overwrites q3config.cfg with default

Post by almo »

I added the +exec thing, and it partially worked. My model was reset to the default, but it didn't play the FMV sequence at the start like it was.

I might try the "read-only" solution. :)
Locked