Author Topic: Transparency issue  (Read 746 times)

Legacy_YeoldeFog

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: +0/-0
Transparency issue
« Reply #15 on: June 30, 2014, 09:54:58 am »


               

I think I have found the source of the problem... the ~mb_castle.hak tileset, or known as "Old castle Interior".


I only get this error when I start or pass through this tileset.


 


Anyone know what this could be?



               
               

               
            

Legacy_Rolo Kipp

  • Hero Member
  • *****
  • Posts: 4349
  • Karma: +0/-0
Transparency issue
« Reply #16 on: June 30, 2014, 01:30:06 pm »


               

<shoving a few things...>


 


I'd be real interested in seeing what envmaps and TXIs are in that hak. Where'd the hak come from? (so I can take a peek)


 


<...to the side>



               
               

               
            

Legacy_NWN_baba yaga

  • Hero Member
  • *****
  • Posts: 1944
  • Karma: +0/-0
Transparency issue
« Reply #17 on: June 30, 2014, 07:06:49 pm »


               

the mb_castle hak is mine. IT´s the simple generic and small castle tileset i uploaded only to my OLD bio projects... i dont remember any... hold on i check...there is no txi file in it! So i dont know why this set can cause a problem... nothing exotic in it realy '<img'>


 


But i will upload it on the new vault so anyone who missed it can check it out. I could even build churches with it heh.... temples i mean... no church '<img'>



               
               

               
            

Legacy_YeoldeFog

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: +0/-0
Transparency issue
« Reply #18 on: June 30, 2014, 07:09:34 pm »


               

Uhm, I think it's an uncomplete hak made by Baba... ':unsure:'  But I have had no success finding it elsewhere :/



               
               

               
            

Legacy_NWN_baba yaga

  • Hero Member
  • *****
  • Posts: 1944
  • Karma: +0/-0
Transparency issue
« Reply #19 on: June 30, 2014, 07:30:08 pm »


               

oh ha.. the window there is not from me. Someone or you have changed the window texture (I´m totaly fine with that '<img'> ). That could cause a problem if someone did a skybox behind, used a blending punchthrough property in the txi file maybe. Check the txi for the window there. It clearly looks like an issue with the window and the env. maps!


 


and uhuhu it´s my 1001 post. Well done NWN... the next step is 2001... '<img'> ':wub:'



               
               

               
            

Legacy__six

  • Hero Member
  • *****
  • Posts: 1436
  • Karma: +0/-0
Transparency issue
« Reply #20 on: June 30, 2014, 08:26:54 pm »


               

It's almost certainly the envmap setting in the .set file for the tileset.



               
               

               
            

Legacy_YeoldeFog

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: +0/-0
Transparency issue
« Reply #21 on: June 30, 2014, 09:23:42 pm »


               

Thanks to Cannonade, it was a simple solution - change the envmap to nothing, and it works! No more air-headed blonde! '<img'>


               
               

               
            

Legacy_MerricksDad

  • Hero Member
  • *****
  • Posts: 2105
  • Karma: +0/-0
Transparency issue
« Reply #22 on: June 30, 2014, 10:10:11 pm »


               

ok, so I am assuming you have env maps on the hair and on the wood of the crossbow, as usual. So the env map on the tileset must have been affecting it. Does it try to combine the env maps, or does the one in the tileset just take over? What was actually going on?


               
               

               
            

Legacy_Cannonade

  • Newbie
  • *
  • Posts: 28
  • Karma: +0/-0
Transparency issue
« Reply #23 on: July 01, 2014, 12:24:26 am »


               

Like _six suggested, the envmap setting in the .set file seemed to cause it, but I don't know enough of the subject to give more of an analysis. Initially tested with the envmap of castle interior, which had the same effect/problem, but leaving the field blank seems to have fixed it.