Aller au contenu

Photo

Copying a module between PCs.


  • Veuillez vous connecter pour répondre
2 réponses à ce sujet

#1
Firky

Firky
  • Members
  • 2 140 messages
Hi there,

Vaguely, it's the same PC. I had to format the HDD.

So, I saved a .dadbdata and imported it into a new module on the new PC. All of the files seem present and correct. I went to the modules properties and assigned script, starting area and waypoint.

When I try to play it, though, it loads this black world with fluoro green sky and a spooky moon. And, if I try to zoom out, there is no player. It's pretty awesome. But what would be more awesome would be playing the module. :P

Does this ring any bells as to what I've missed? Probably just something obvious. Any ideas?

Thanks,

Firky

Modifié par Firky, 01 novembre 2012 - 07:34 .


#2
Firky

Firky
  • Members
  • 2 140 messages
Weird.

Typically, as soon as I posted that, I realised I'd forgotten to pop the art resources into the right folder, so I did that. The module starts with a slideshow.

So, I exported everything again, just to be sure and I now have the slideshow, just text, no art, and then Jaden, as the rest of the world loads correctly. At least this is closer ...

#3
sea-

sea-
  • Members
  • 264 messages
Hmm.

First of all, you should have only exported stuff that was relevant to your module. Exporting and overwriting core resources is a huge no-no as they can severely mess up the game.

If that wasn't it, it might be a case of the string IDs being messed up. You need to make sure the string ID range of your new module is the same as the old one, and that you import the existing string IDs. If that doesn't work, then set up some new string IDs and select "create new string IDs" when importing - you will have to change any 2DA and voice-over files to refer to the new string IDs if that is the case.

From the sound of it, most of the problems may just be missing files you forgot to copy, and they may need to be remade if you don't have backups. Stand-alone art resources (models, textures, etc.) are not part of the database and so are not saved when you do a builder-to-builder create.

If you have not watched it already, this is a really good overview of how the database and files work:


Modifié par sea-, 14 novembre 2012 - 06:29 .