Zoom2 Invasion
Verfasst: Samstag 22. September 2007, 17:43
Hello,
You may have ever noticed the huge number of Zoom2 files in your BAHN Zoom2 directory. I myself have 24M in 4039 files there.
Each user-defined car file can contain up to 160 cars, that is, 160 Zoom2 files, usually about 4-8Kbytes long. Using many user defined car files you get more and more Zoom2 files. Unlike the Zoom2 graphics for standard cars, these files must stay in the same directory as the layout that use them. This could lead to file duplication if independent layouts use them, and this all could waste your HDD space. And I haven't counted the Zoom1 graphic files, which can be up to 100 per layout, as of Bahn 3.84.
Although these files are accessed only when their corresponding car graphic file is loaded, the repeated open/close file operations slow down the loading process.
My idea is that instead of a couple of fzz files, a single container file could be used. This file would contain all needed fzz files in their fzz file format, and should have a simple own format, in order to allow other software to easily extract the fzz files when needed or to pack the fzz files into such container file.
With all needed data located in a single file instead of more than one, this should reduce the loading speed.
Besides that, it is quite annoying to have so many files in one's nt3 directory.
Most of Bahn's users rely on the standard Bahn vehicles and use a little number of user-defined vehicles, but others don't. This is just an idea for future versions.
Greetings,
Trix
You may have ever noticed the huge number of Zoom2 files in your BAHN Zoom2 directory. I myself have 24M in 4039 files there.
Each user-defined car file can contain up to 160 cars, that is, 160 Zoom2 files, usually about 4-8Kbytes long. Using many user defined car files you get more and more Zoom2 files. Unlike the Zoom2 graphics for standard cars, these files must stay in the same directory as the layout that use them. This could lead to file duplication if independent layouts use them, and this all could waste your HDD space. And I haven't counted the Zoom1 graphic files, which can be up to 100 per layout, as of Bahn 3.84.
Although these files are accessed only when their corresponding car graphic file is loaded, the repeated open/close file operations slow down the loading process.
My idea is that instead of a couple of fzz files, a single container file could be used. This file would contain all needed fzz files in their fzz file format, and should have a simple own format, in order to allow other software to easily extract the fzz files when needed or to pack the fzz files into such container file.
With all needed data located in a single file instead of more than one, this should reduce the loading speed.
Besides that, it is quite annoying to have so many files in one's nt3 directory.
Most of Bahn's users rely on the standard Bahn vehicles and use a little number of user-defined vehicles, but others don't. This is just an idea for future versions.
Greetings,
Trix
