16.12.2009, 22:15
Nope, I am familiar with the buttons requirements and have only one buttons file in the Files/gui/game folder. The reason for the crash was that the java files (assume java, but the ones with the hash like naming) were not being copied into the Files/ folder related to the P-40 mod. The two file with the hash-like file names were not being copied to the correct location using the GME tool. Once I updated the P-40 mod to look like:
P-40F-L/Files/
everything fell into place. The hash-like files were copied into "Files" and the Files/3do folder was updated with the relevant files for the P40. Everything loaded and works correctly.
UPDATE: Yep, just added two new aircraft to HSFX in addition to the P40 addition, using the technique noted in this thread with no problems. I also updated the fly_zo f6f cockpit mod to use the technique and now that mod is correctly working in the HSFX base install. The bottom line is that for any mod added to base HSFX, all the mod code must be packaged in Files/. Therefore, you would have something like this for the P-40FL mod:
Extract the mod to a space on the harddrive. in the actual directory where you see the 3do directory and all the java (hash like named files) create a new folder called "Files/" Move all the hash like files and the 3do directory into the Files folder. Copy your updated mod pack to the jsgmemods folder in the IL2 HSFX game directory. Fire up GME and enable your mod. Let it do its thing and if you get the warning message, simply ignore it. Once GME has the mod enabled, fire up IL2 HSFX, and wala, your mod is in there!
As for mod mgmt, I have used a naming convention for my "add on" mods in GME. All the add ons start with "MOD - " in the naming convention, so if I need to use the base HSFX install for online flight or some other reason, I can simply disable all the ones that start with "MOD -" using GME, and have the base HSFX install.
All in all, pretty slick, and I like it!
P-40F-L/Files/
everything fell into place. The hash-like files were copied into "Files" and the Files/3do folder was updated with the relevant files for the P40. Everything loaded and works correctly.
UPDATE: Yep, just added two new aircraft to HSFX in addition to the P40 addition, using the technique noted in this thread with no problems. I also updated the fly_zo f6f cockpit mod to use the technique and now that mod is correctly working in the HSFX base install. The bottom line is that for any mod added to base HSFX, all the mod code must be packaged in Files/. Therefore, you would have something like this for the P-40FL mod:
Extract the mod to a space on the harddrive. in the actual directory where you see the 3do directory and all the java (hash like named files) create a new folder called "Files/" Move all the hash like files and the 3do directory into the Files folder. Copy your updated mod pack to the jsgmemods folder in the IL2 HSFX game directory. Fire up GME and enable your mod. Let it do its thing and if you get the warning message, simply ignore it. Once GME has the mod enabled, fire up IL2 HSFX, and wala, your mod is in there!
As for mod mgmt, I have used a naming convention for my "add on" mods in GME. All the add ons start with "MOD - " in the naming convention, so if I need to use the base HSFX install for online flight or some other reason, I can simply disable all the ones that start with "MOD -" using GME, and have the base HSFX install.
All in all, pretty slick, and I like it!