!!!HELP PLEASE!!!

[shifty9889]

i recently made a mod and took me about a week but after adding a few new guns to the game i keep getting 2 error messages then a CTD

the error's are

"scope geometry has a height map for parallax, but no parallax flag set" and

"lens geometry has a height map for parallax, but no parallax flag set"

 

 

then it just crashes to desktop

iv added loads of new guns to the game then saved it and afterwards its loaded up in the geck fine untill the last time i added a few (about 4) iv tried removing the files from the data location but it still wont load up my mod in the geck

 

this mod has taken me ages to put together but i cant find help anywhere and i dont really want to start all over again

 

if anyone knows how to fix this please help asap

[GrindedStone]

If you wana you can upload a copy of just the .esp only, an I can take a look at it. Besides that I bet that if you did start over an make it again you would find that you are much better at making things now.

[shifty9889]

sorry for the long reply but the .esp relies on loads of custom models textures and sounds so if i do you would not get the errors that im receiving and my knowledge using the geck is basic but i know how to add new weapons and textures and create a building and nav mesh and everything but this error is a set back that has taken me ages to create )=

[GrindedStone]

Whatever... You want to pretend that your .esp is IP but Bethesda owns it, and once you put it on the Nexus, then Nexus owns it too. So you can stop treating me like I'm some kind of content pirate that does so by going around pretending to "help" people just so I can get my little grubby hands on your one week lifes work. My thinking behind wanting to look at the .esp was to see how dirty it was an how the textures were applied. It sounded like that you had broken the mod, so look at it with tools other than the GECK, which I though if you knew how to do that you wouldn't be wasting time here asking.

 

A bad weapon mesh will cause CTD an there are many ways it can do that. The more common is from it being a dirty mesh. By whatever means you used to create it, it remains in that post-edited format as a .Nif rather than a clean cut an paste of the shape data only to a known good mesh, though such practice can be unpredictable when used on Havok primitives. It does solve a few problems at once. The basic run down is located at Nexus Wiki under the nifscope part of create a sword Here

 

The error itself is probably nothing, you get these types of errors a lot. However if you had applied textures to meshes with the GECK, it would mean you have an actual error. If you just have one mesh an one texture then you apply the texture to the mesh in nifscope. If you have one mesh an 30 textures then you use GECK to apply those textures. Just because it's less work this way. In GECK look at the 1stperson textures for vanilla weapons an then your weapon an make sure they match. But unless you have more than ten reskins for this weapon it would be a little silly.

 

Though it's rare you would ever need to set weapon textures in the GECK I've only done it once back when I was learning. The possible cause of setting this texture inside nifscope which is yeilding a error such as was described in GECK, is actually fixed by the above suggestion of clean pasting into known good meshes, because there are a lot of flags that go along with the actual structure of a .Nif, in this case one that causes the GECK to freak out, which could have been a product of editing.

 

*edit* I read it again an it sounds like you should indeed look at the .esp with another program besides GECK. I bet that cleaning it would fix it. You could also make sure you are using the 1.5 version of GECK. Try updating to 1.5 again or un-install re-install the GECK, and last you could try a master update on that .esp with FO3 edit then master restore. FO3 edit/ TES snip/ FO3 PIU/ Wyre bash that kind of stuff, they all have tools, you can make it a .esm with TES snip then convert it back with FO3 plug in utility (FO3 PIU) You could also just remove the entries which are causing the crash, or copy those entries into a new .esp as new entries.

Edited May 26, 2011 by GrindedStone