Author Topic: Play button greyed out  (Read 521 times)

Legacy_Lovelamb

  • Jr. Member
  • **
  • Posts: 68
  • Karma: +0/-0
Play button greyed out
« on: August 07, 2013, 04:41:06 pm »


               When I try to start the module I'm building, I'm taken to the select character screen, and every character has the Play button disabled. Creating a new character just adds it to the list, Play is disabled again. This doesn't seem to be the case with other modules, just this one that I recently edited. I tried moving the start position to a different area and building the module - still the same.

I don't know if this is the cause, but earlier, when I tried to create an area with the Ruins tileset, it would open the new area but immediately give an "access violation" error. I may have saved the module after doing this, and then deleted the new area.

The module uses CEP and other haks, but the only difference between this module and the previous one, in which the Ruins tileset worked, should be one hak containing a new forest tileset and no 2da files. I haven't modified the haks since the last successful testing of the module (though I probably never tried to use that tileset in this module before).
               
               

               
            

Legacy_Fester Pot

  • Hero Member
  • *****
  • Posts: 1698
  • Karma: +0/-0
Play button greyed out
« Reply #1 on: August 07, 2013, 06:16:31 pm »


               Your module, I'm afraid, is corrupt.

Adding a tileset that adds to an existing one, such as creating a new tile with ruins or a new 2x2 tree, as examples, placing them in an area and then removing the HAK content, causes "access violation" errors. The area has these new tiles, but it can't find the references any longer - due to being removed from the HAK list, files removed from a HAK, or overwritten by something else - and thus, errors occur.

To get around the play button being disabled, my suggestion is to load up your module in the toolset - make a backup of it first - and remove the troubled area causing the access violation. Resave the module to a new name _TEST.mod, and try loading it again. Place your start location into a default Bioware tileset if possible.

If it's still disabled, load the module up in the toolset.

File - Export each area, minus the area causing the problems.

Create a new module.

File - Import each area.

Place your starting location in a default Bioware tileset. Save.

Try again.

EDIT: Additionally, when you have the tileset open, COPY and PASTE all the files from the modules/temp0 directory to a directory of your making. This will grab all the scripts, conversations and everything else from the module. Indivudually unselect the *.are, *.gic, *.git .

When you create a new module to IMPORT the areas as noted above, it will create a new /temp0 directory. Once you've imported those areas into the new module, COPY and PASTE all the files back into the /temp0 directory (minus *.are, *.gic and *.git).

Lastly, if you have a backup before these problems started, it might be worth going back to that if a lot of work has not been lost.

FP!
               
               

               


                     Modifié par Fester Pot, 07 août 2013 - 05:26 .
                     
                  


            

Legacy_Lovelamb

  • Jr. Member
  • **
  • Posts: 68
  • Karma: +0/-0
Play button greyed out
« Reply #2 on: August 07, 2013, 11:13:47 pm »


               Thank you for the reply. I imported everything into an old, working version.

I immediately get the error when creating a new area with the ruins tileset, even in the old (published) module now. The new area only has 4 ordinary tiles in the middle, and I can see them, but the error message appears and won't go away (but I was able to click the save button and corrupt the module earlier...). It looks like there is something wrong with my haks on this computer (tried it on another where I have NWN installed, and there were no problems). I move around too much and have to install things every time...