anb2004 Posted January 11, 2012 Share Posted January 11, 2012 On 12/3/2011 at 2:02 AM, Ghogiel said: Oh anyone seen any NiStencilProperty in the skyrim nifs? If it is used, how is it linked up? like where the alpha property is linked in...? On 12/3/2011 at 2:13 AM, throttlekitty said: Nope, that's in the LightingShaderProperty flags as well. finally managed to bring my custom armor in game, but i kinda confuse how to set NiStencilProperty in the shader flags. shader flags also looks weird, if i click it theres no other option at all (everything just blank), theres only one with checklist but with no flag name.. a little help...thanks Link to comment Share on other sites More sharing options...
Ghogiel Posted January 11, 2012 Share Posted January 11, 2012 it's in shader flags 2. you want SF_Double_Sided. If you are not seeing a random looking string of numbers then you should update nifskope.... Link to comment Share on other sites More sharing options...
anb2004 Posted January 11, 2012 Share Posted January 11, 2012 (edited) On 1/11/2012 at 12:43 PM, Ghogiel said: it's in shader flags 2. you want SF_Double_Sided. If you are not seeing a random looking string of numbers then you should update nifskope.... oh god, thats why i dont find the shader flag 2, i'm still using 1.1.0 rc1 afraid updating nifskope will break something.. finally just fired up the newest 1.1.0 rc4 now i can see the shader flag 2 and many new settings.. thanks very much ghogiel... :wink: Edited January 11, 2012 by ebony_ivory Link to comment Share on other sites More sharing options...
throttlekitty Posted January 12, 2012 Author Share Posted January 12, 2012 Nifskope 1.1.0 RC5changes since 1.1.0-RC5: * Fix: .kf attaching for 10.0.1.0 - renaming the fields in "nif.xml" works as well * Fix: double_sided rendering issue * Add: SF_Double_Sided handling for "BSEffectShaderProperty" * Fix #3468080: property "paste" now works for non-NiProperty blocks * Fix #3471254: temporary set global template for some properties * Fix: rendering of double-sided + alpha unsorted triangles issue * Add: "BSEffectShaderProperty" - initial support * Add: unknown properties are now reported by the property factory Link to comment Share on other sites More sharing options...
jgreybear Posted January 13, 2012 Share Posted January 13, 2012 Sweet! can't wait to try it out thanks TK. Link to comment Share on other sites More sharing options...
throttlekitty Posted January 13, 2012 Author Share Posted January 13, 2012 Thank corwin, he's writing the code! Link to comment Share on other sites More sharing options...
throttlekitty Posted January 13, 2012 Author Share Posted January 13, 2012 (edited) I found a small bug in RC5's nif.xml some of you might be interested in, it's an easy fix. Right now, not all values for LightingShaderProperty>Shader Flags 2 are visible, and flags 9/13 will end up checked by default when using the dropdown. Can't unselect one of them, only both. Line 4467 of nif.xml:<option value="432713" name="SF_13"></option>should be<option value="13" name="SF_13"></option> Also, shader flag 8 is interesting, not sure what to call it. The model acts as a pass-through for shadow rendering but not receive. Kind of like a window, but only for shadows, kind of trippy. Gives me some devious ideas for a maze scene. Edited January 13, 2012 by throttlekitty Link to comment Share on other sites More sharing options...
jgreybear Posted January 13, 2012 Share Posted January 13, 2012 Sorry not much of a coder my self...what program is best to use to fix the xml? Link to comment Share on other sites More sharing options...
throttlekitty Posted January 13, 2012 Author Share Posted January 13, 2012 ah, sorry. Notepad++ Link to comment Share on other sites More sharing options...
throttlekitty Posted January 16, 2012 Author Share Posted January 16, 2012 http://dl.dropbox.com/u/13576177/NifTools/nif.xmlhttps://github.com/throttlekitty/nifxml/commit/bc9973217af9f15d2eebff5a0871b298fd7de686 I worked my nif.xml away from Amorilia's alpha build, and worked towards corwin's release candidate builds, this should fill out some better descriptions and help solve a few more of the "Link points to wrong type" errors you may have with RC4/5. Link to comment Share on other sites More sharing options...
Recommended Posts