Author Topic: Armor Parts: Access Violation  (Read 339 times)

Legacy_dusty.lane

  • Full Member
  • ***
  • Posts: 222
  • Karma: +0/-0
Armor Parts: Access Violation
« on: September 14, 2012, 02:17:58 am »


               So I am trying to get some armor into the default game, I have my model, my texture, I put them both into a hak and put it in a module. I open up armor, select the armor piece (I only have one piece ready right now) and the screen flashes wildly until I close the window. It also gives an error message, "Access violation at address 0075A476 in module 'nwtoolset.exe'. Read of address 002A554C."

It's prohibiting me from a lot of work currently, and I have no clue what I'm doing. It's probably something extremely simple that I'm forgetting to do. I have a model base, and all that, and am using gmax. What might it be?

Any help would be grand! ':crying:' Thanks in advance for whatever I get, just hope it's not a, "You're stupid for missing this simple step even a child could do." '<img'>
               
               

               
            

Legacy_Borden Haelven

  • Hero Member
  • *****
  • Posts: 681
  • Karma: +0/-0
Armor Parts: Access Violation
« Reply #1 on: September 14, 2012, 03:50:31 am »


               I've found access voilations are often caused by dud TGAs try re-naming a known good one and overwriting the one in the hak and see if fixes it.
               
               

               
            

Legacy_B_Harrison

  • Sr. Member
  • ****
  • Posts: 301
  • Karma: +0/-0
Armor Parts: Access Violation
« Reply #2 on: September 14, 2012, 04:23:15 pm »


               I'd check your parts_*.2da file(s); IIRC, incorrect entries in 2das (eg, *** rather than **** for "no value") can cause nasty toolset behaviour.

I'm probably wrong (it's been a while), but it might be worth checking.
               
               

               
            

Legacy_Pstemarie

  • Hero Member
  • *****
  • Posts: 4368
  • Karma: +0/-0
Armor Parts: Access Violation
« Reply #3 on: September 14, 2012, 10:13:32 pm »


               Is the model compiled? If so, try it with the decompiled model.
               
               

               
            

Legacy__NagaShadow_

  • Newbie
  • *
  • Posts: 22
  • Karma: +0/-0
Armor Parts: Access Violation
« Reply #4 on: September 15, 2012, 03:22:58 am »


               I think is for in your texture there are transparent.
               
               

               
            

Legacy_dusty.lane

  • Full Member
  • ***
  • Posts: 222
  • Karma: +0/-0
Armor Parts: Access Violation
« Reply #5 on: September 15, 2012, 08:36:12 am »


               I've got it basically working now, thanks Borden!

@_NagaShadow_,

Is that bad in a plt?
               
               

               
            

Legacy__NagaShadow_

  • Newbie
  • *
  • Posts: 22
  • Karma: +0/-0
Armor Parts: Access Violation
« Reply #6 on: September 15, 2012, 03:15:44 pm »


               For my experience, yes. You should look at your texture, and make sure that it has no transpariencies and prove it again.

Sorry, my english es very bad @_@
               
               

               
            

Legacy_Failed.Bard

  • Hero Member
  • *****
  • Posts: 1409
  • Karma: +0/-0
Armor Parts: Access Violation
« Reply #7 on: September 15, 2012, 04:10:06 pm »


               Transparencies are essential in a plt file, considering they're made up of overlapping layers.  Amy part of a layer that isn't meant to be coloured by that particular part coulour needs to be transparent, not solid.

 With tga files, the main thing to watch for is that it isn't saved using rle or any other compression.  It usually works in overrides still, but can cause issues trying to convert to DDS if you do.