|
Author
|
Topic: par File Oddities
|
Whirlwind Pilot
|
posted 03-27- 07:17 PM
I don't know how this is happenning, but the guy working on the Contest Pack seems to be having touble with 2 FB2's showing up in the 'Training' area in SDOE. Through no fault of it's own, it is being duplicated, even though an extract reveals only 1 F2B. The F2B suffers not alone, but with the F4U, and F4U-4. Both refuse to show up, even though an unbig reveals the plane's training files and folders present and accounted for. What kind of muntiny is this? There is no problem when all the planes are standing by themselves. I rather hate seperating these fine planes in a hit-n-miss manner to see who or what is playing this foul game. Such treacherous acts. I beleive it to be demon (daemon, for you Unix weenies) possesion or black magic.IP: Logged |
Zoycite JAG
|
posted 03-27- 07:54 PM
So when might these demons be vainquished so we might carry forth and commence the ritual of.... "Voting"?  Umm, just a question, why is there more than one version of the F4U. I seem to recall there only being one entered. The F4U-1D. Strange days indeed. ------------------ Zoycite 33rd~GS visit The War Paint Factory IP: Logged |
Whirlwind Pilot
|
posted 03-27- 08:15 PM
The FB2 problem was vanquished by deleting a file (o-buddy, can you hear the hyperventilating now?) that started with an underscore '_'. It 'means duplicate me' in 'big' talk. The F4U's aren't showing up in the mission editor (well, just the F4U-1D and F4U-4).Let me check the entries list, this might make it less of a headache . IP: Logged |
Whirlwind Pilot
|
posted 03-27- 08:17 PM
Life just got a wee bit easier, it appears that the F4U-1D is the only viable Corsair to be chucked in the pack. The guy doing it is pleased (bowing at the great Zoycite).IP: Logged |
Whirlwind Pilot
|
posted 03-27- 08:31 PM
New odditie. The F4U-1D had a mission in it that had the same name for all the versions of the Corsair. I renamed the mission to the name of the plane it was for. For example, the original mission name for the Corsair 2 was 'Gunner's F4u-1 Trap Practice' which was renamed to 'Gunner's Corsair 2 Trap Practice' in hopes of remedying the single corsair problem. It didn't work. Period. The F4U-1D had the mission name of 'Gunner's F4u-1 Trap Practice' and it still does, despite being renamed to 'Gunner's F4u-1D Trap Practice'. At least it appears that way in the training missions.I'm seeing if I can fly it right now, even though it isn't in the par file, nor anywhere else in the directory. The mission worked. I'm clueless..... IP: Logged |
jedi Pilot
|
posted 03-29- 01:04 PM
Hmmm. I meant the "extra" Corsairs just to be added "features." Maybe I shoulda left em out of the contest pack.If you just want the F4U-1D for the contest parfile, go to my site at: http://sites.netscape.net/jeditaub/Downloads/F4U-1D.zip get the one called F4U-1D.zip. If you check the date on it you'll see I haven't updated it since well before deadline. That one file is a "stand-alone" aircraft that contains the common files for all four, but it's the only one of the four that is functional by itself. It should be easy to put into the parfile. Be sure you do NOT use the PatchF4U.zip file in the parfile. That one is strictly for guys who had earlier versions that weren't working right, and should never have made it into the contest site. I don't think I uploaded it there. Let me know if it doesn't work for some reason. I have good working (pre-deadline) copies of all the "contest version" Corsairs.  ------------------ --jedi--
[This message has been edited by jedi (edited 03-29-2000).] IP: Logged |
Whirlwind Pilot
|
posted 03-29- 05:25 PM
Oddly only 1 version of the F4U would show up, so I stripped out the other ones. No problem, the 1D flew fine in the pack. The only problems now are that the mission descriptions are hosed on half the planes and the DVIII is a no-show, even though it exists in the pack and in the unbigged pack. I didn't want to say the pack is done and have thousands of angry people pointing fingrers for having such an err. I am suspecting a conflict behind it all.MH is working the issue. I got in over my head when the really scwewy stuff started up. IP: Logged |
Raider Pilot
|
posted 03-29- 10:04 PM
Whirlwind, thanks for your efforts. I know this turned into a bigger job than expected. I hate it when crap like that happens for no reason at all. Get this fixed then that happens. Where does it all end?  ------------------ Raider 33rd~GS IP: Logged |
jedi Pilot
|
posted 03-30- 09:57 AM
Dumb question, maybe, but wouldn't a big zipfile (or two or three) have made just as much sense as a new parfile? These planes will ALL have new versions appearing over the next few months, so the parfile will end up being almost completely "overridden" anyway.I can't help but thinking that the "bigmungering" is causing some problems here. I know I had the Corsairs all working "harmoniously" at one point, and the DVIII is certainly working OK in my sim... Just a thought. ------------------ --jedi-- IP: Logged |
Whirlwind Pilot
|
posted 03-30- 03:01 PM
The files alone weighed in at about 34MB, the pack at 27MB, the zip at 13MB. I wonder how big a single zip would be?IP: Logged |
jedi Pilot
|
posted 03-30- 08:54 PM
Hehe I'll be shutting up now...Took me about 5 tries to get ONE plane zipfile right, so anything I say on this subject is automatically suspect  ------------------ --jedi-- IP: Logged |
Whirlwind Pilot
|
posted 03-30- 09:22 PM
I still have the false SDOE directory set up. The planes work fine when I just copy and past them. WinZip is a drunken walk through Central Park when it comes to getting the files in a zip that you want.IP: Logged |
Whirlwind Pilot
|
posted 03-31- 10:06 PM
Just to get the planes out for judging (other things emerged with the .par file idea that can't be dealt with in a timely manner) we've gone with jedi's idea of just zipping the whole schibang up and posting it somewhere. The planes should all work rather well this way. It also isn't as bad as I thought, a mere 17MB file.IP: Logged |