search

ayoub05 / vdrift-ogre

Automatically exported from code.google.com/p/vdrift-ogre
0 stars 0 forks source link

User data files and cache usage #24

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The game should write nothing to the system wide data dir as that dir will most 
likely be write-protected after the game is installed (On Windows: C:\Program 
Files\stuntrally, on Linux: /usr/) and a game should never be run with 
administrator privileges.

This means all generated stuff (impostor billboards and whatnot) should go to a 
cache directory and important data, such as track records and modified tracks 
should go to a user's data dir. There is more information in the Paths wiki 
page.

There are two goals in this:
1. After this the game can be installed to a write-protected location and it 
runs fine, without any reduced functionality.
2. The game never modifies or creates any files in Mercurial, i.e. `hg status` 
shall be clean whenever you have committed your stuff.

This all applies to editor too.

Original issue reported on code.google.com by tapiovie...@gmail.com on 22 Mar 2011 at 4:58

GoogleCodeExporter commented 9 years ago 
Still to change:
1.cars have dynamic saved textures eg.
data\cars\3Sgrav\textures\body_dyn.png
2.screenshots dir
3.track records.txt

Original comment by Cry...@gmail.com on 25 Mar 2011 at 6:45

GoogleCodeExporter commented 9 years ago 
From where are body_dyn-images loaded? I found where they are saved but not the 
loading code. I hope it is not hard-coded into the .mesh-file. 

In other news, screenshots are now saved to user's home dir (scrawl).

Original comment by tapiovie...@gmail.com on 26 Mar 2011 at 12:08

GoogleCodeExporter commented 9 years ago 
Track records are now saved and loaded from a user-specific data directory.

Original comment by tapiovie...@gmail.com on 26 Mar 2011 at 12:41

GoogleCodeExporter commented 9 years ago 
body_dyn.png is now handled. It seems:

1. After this the game can be installed to a write-protected location and it 
runs fine, without any reduced functionality.

is accomplished.

Original comment by tapiovie...@gmail.com on 26 Mar 2011 at 1:16

GoogleCodeExporter commented 9 years ago 
What about the MyGUI.log file ? On Win it's written just where exe is.

Original comment by Cry...@gmail.com on 27 Mar 2011 at 6:15

GoogleCodeExporter commented 9 years ago 
I committed a change where MyGUI.log is put next to the other log files. 
However, there is an issue where init and shutdown messages are still written 
next to the exe, so there is now actually two MyGUI.log files, with different 
content. Any ideas? (This seems to be non-critical issue though, as the game 
doesn't crash if it can't write MyGUI.log).

Original comment by tapiovie...@gmail.com on 27 Mar 2011 at 8:02

GoogleCodeExporter commented 9 years ago 
The MyGUI.log is problematic, we could turn it off, but it doesn't disturb so 
it can stay like this.

Original comment by Cry...@gmail.com on 27 Mar 2011 at 9:01

GoogleCodeExporter commented 9 years ago

Original comment by tapiovie...@gmail.com on 9 Apr 2011 at 2:20

GoogleCodeExporter commented 9 years ago

Original comment by Cry...@gmail.com on 9 Apr 2011 at 3:31

GoogleCodeExporter commented 9 years ago

Original comment by Cry...@gmail.com on 11 Apr 2011 at 5:25

GoogleCodeExporter commented 9 years ago

Original comment by Cry...@gmail.com on 12 Apr 2011 at 4:51

GoogleCodeExporter commented 9 years ago

Original comment by Cry...@gmail.com on 13 Apr 2011 at 5:33

GoogleCodeExporter commented 9 years ago

Original comment by Cry...@gmail.com on 13 Apr 2011 at 6:08

GoogleCodeExporter commented 9 years ago

Original comment by Cry...@gmail.com on 16 Apr 2011 at 7:33

GoogleCodeExporter commented 9 years ago

Original comment by Cry...@gmail.com on 8 May 2011 at 1:38