Author Topic: DJ Galaxy Class Pack -- Now Available @ BCFiles (Read 38326 times)

Judge King · « **Reply #260 on:** October 13, 2008, 08:44:56 AM »

Quote from: Billz on October 13, 2008, 06:59:28 AM

The only thing I wish from this pack is that the USS Odyssey from this pack doesn't get overwritten by the USS Odyssey from the Stargate v3 Ship Pack (downloaded and saved on external harddrive before it was deleted off BCFiles.com) like what always seemed to happen with the SNS Galaxy pack.

Maybe that can be solved by naming the files for the USS Odyssey; USS Odyssey NCC-71832?

Kirk · « **Reply #261 on:** October 13, 2008, 09:08:47 AM »

As long as the longname, shipfile, and hp isn't the same as the SG Odyessey, then you will be fine.

DJ Curtis · « **Reply #262 on:** October 13, 2008, 10:49:31 AM »

the longname is U.S.S. Odyssey. I was mindful to use periods between the USS as that's pretty uncommon. There should hopefully be bo accidental overwrites.

Dalek · « **Reply #263 on:** October 13, 2008, 10:56:52 AM »

Quote

There should be no accidental overwrites.

Looking forward to the Pegasus DJ!

MLeo · « **Reply #264 on:** October 13, 2008, 10:57:59 AM »

Or add, let's see, 'DJ Galaxy Class Pack', that's 20 characters, so add 20 spaces to the end of the longname. ;)

DJ Curtis · « **Reply #265 on:** October 13, 2008, 11:05:32 AM »

I can't tell if you're serious or kidding.

MLeo · « **Reply #266 on:** October 13, 2008, 11:16:10 AM »

Quote from: DJ Curtis on October 13, 2008, 11:05:32 AM

I can't tell if you're serious or kidding.

Both I suppse.

Adding spaces to the end makes it unique to Foundation, and they aren't shown in-game, and the buttons don't know of ellipses (those ... you sometimes see on windows when the title is too long).

I'm actually investigating options for this, for example, making Foundation SubMenu aware.
Which is a bit tricky, since at the time Foundation is assigning the shipdef to the "dictionary" (between ship longname and the shipdef) it's still constructing the shipdef, and most people (all, myself including) set/assign submenu at a later stage.

There are various options for this, one I'm currently exploring is loading all ships from the Ships directory into a list or something like that. And then, after everything has loaded, and assigned, assign everything a (new) name that is unique to it's place in the list (ie. species/submenus/subsubmenus/MVAMParentShip/Longname).

Barihawk · « **Reply #267 on:** October 13, 2008, 11:21:39 AM »

Those things are tricky. I remember having compatibility issues with the Stargate Pack and Glenn's Korolev. Involved a total reinstall and no more Stargate

.

MLeo · « **Reply #268 on:** October 13, 2008, 11:23:41 AM »

Well, I can't really help with conflicting filenames.
But some investigation into subdirectories might be interesting. And logging overwrites as well.

DJ Curtis · « **Reply #269 on:** October 13, 2008, 11:35:57 AM »

I know I had a heck of a time getting a longname for the Enterprise. Adding U.S.S. before all the names seems to have solved the problem, in KM1.0 at least.

Also, for the record, I think this will be the last time I release a pack of this scope and scale. To much work!

Kirk · « **Reply #270 on:** October 13, 2008, 11:42:13 AM »

The problem is that no one has every ship ever released on BCF all on one install, so there's no 100% safe way to name your ships short of naming your own releases (like you already do DJ) with an extremely unique shipfile and hp, like Kirk2164Galaxy, and putting it in it's own QB menu, like Kirk2164's ships.

DJ Curtis · « **Reply #271 on:** October 13, 2008, 11:43:37 AM »

well, if people run into problems, there's always the tech support forum! That being said, I'll try to have the beta'd by people who might have conflict issues.

limey BSc. · « **Reply #272 on:** October 13, 2008, 12:02:27 PM »

The ones in the Stargate Pack are all "Odyssey" or "DSC304", so adding "U.S.S." to the front should avoid conflicts.

MLeo · « **Reply #273 on:** October 13, 2008, 12:08:30 PM »

Quote from: kirk2164 on October 13, 2008, 11:42:13 AM

The problem is that no one has every ship ever released on BCF all on one install, so there's no 100% safe way to name your ships short of naming your own releases (like you already do DJ) with an extremely unique shipfile and hp, like Kirk2164Galaxy, and putting it in it's own QB menu, like Kirk2164's ships.

It's all in the longname, for now anyway.

So if you have 2 ships, in the same "species", with the same longname, then one _will_ overwrite the other.

Barihawk · « **Reply #274 on:** October 13, 2008, 12:41:29 PM »

Quote from: limey98 on October 13, 2008, 12:02:27 PM

The ones in the Stargate Pack are all "Odyssey" or "DSC304", so adding "U.S.S." to the front should avoid conflicts.

Unfortunately "Korolev" was the problem for me

.

Whenever the next version comes out I will probably edit the Korolev hp's and files to have unique names so no conflict occurs.

DJ Curtis · « **Reply #275 on:** October 17, 2008, 10:11:13 PM »

Okay. This pack is finished, just needs to be packed up into a file structure and zipped. Final download size will be, err.. never mind. Anyhow, Cord has nearly finished his teaser trailer, and it should be on BCFiles in the near future to build awareness. Expect to see this mod released probably next weekend, Sunday morning.

FourChan · « **Reply #276 on:** October 18, 2008, 12:33:24 AM »

Sweet, thanks for another great mod.

Dalek · « **Reply #277 on:** October 18, 2008, 07:31:04 AM »

This may be a bit late coming but will there be blank textures for the Pegasus refit? I know there are blanks for the normal refit but I'm not sure about the Pegasus.

DJ Curtis · « **Reply #278 on:** October 18, 2008, 11:59:24 AM »

it can certainly happen.

eclipse74569 · « **Reply #279 on:** October 18, 2008, 05:17:56 PM »

Sounds great, can't wait, looking great

.

News:

Author Topic: DJ Galaxy Class Pack -- Now Available @ BCFiles (Read 38326 times)