Windows XP crashing Issues!

[Legacy_TimG]

               additional:  I fired up the mod on the Win7 unit at work from a save game and then DM'd in with client and used the DM to try going through while logged onto the Win7 game.  The XP box crashed to desktop same as if it was the host instead of the Win7 being the host.  I don't know if that is relevant but it's all the testing I could think to do here at work.
               
               

               
            

[Legacy_TimG]

               another thing:  Just as before I loaded up on Win7 then joined from XP with DM Client.  I teleported the party to the area in question and walked them back and forth successfully on the Win7 unit.  As soon as I tried it on the XP box it crashed, further it crashes if you use the CHOOSER to JUMP to Catacombs level 1 which takes you to a different spot than going through the door.  I think this rules out the door transition?
               
               

               
            

[Legacy_Pstemarie]

               Its sounding more and more like a tileset issue. What tileset was the catacombs built with?
               
               

               
            

[Legacy_TimG]

               okay, it also crashes on XP if you go outside the Temple Darkmoon.  I just tried it with a DM controlled henchman.  The henchman had NOT been in the catacombs before trying to go outside but the DM avatar had been
               
               

               
            

[Legacy_Tarot Redhand]

               It's just a thought but has anyone tried it in single player as opposed to mp? Oh and it works fine (at least to v1.24) on vista.

TR
               
               

               
            

[Legacy_Tim.G]

               okay, just got home and tried a few more things.  On the Dell XP Pro unit at home (GT430 card) it freezes up going into and out of the Temple Darkmoon.  The only hints I can offer are that on my WinXP Pro Dell (home) I noticed that the description doesn't appear above the graphic when the load screen pops up whereas it does on the Win7 unit at home. ALSO, and this may be something on my "good" computer at home (Win7 Systemax GTX295) when changing these same screens that we are talking about there is flickering on the load screen that doesn't happen with any other module.  I believe that it has happened intermittently as I have played through but as it had no effect I suppose I got to ignore it.  Now sitting here with several PC's going it's more noticeable.
To recap:
Work HP with XP Pro/GT9800: crash
Work Dell with XP Pro/ATI card:crash
Work Win7/GTX670: pass through okay
Home Dell XP w GT430: crash
Home Win7 w GTX295: pass through with flickering
               
               

               
            

[Legacy_Tim.G]

               changing screens on the Win7 GTX295 unit doesn't flicker (at the load screen) on other levels like it does on the problem level...
               
               

               
            

[Legacy_Tim.G]

               the load screen starts out normally and when the load bar gets most of the way across is flickers very badly.  Just on this level as far as I can tell...
               
               

               
            

[Legacy_Tim.G]

               last note for the day: jumping a character to Darkmoon Temple and going through the initial "how may we help you" cutscene and then just exiting the temple crashed the screen on the Dell GT430 combo.  The thing that is extra strange about this is the header above the picture on the load screen is gone and underneath where I think it should say "loading screen" instead it says "unloading..."
I think whatever is wrong is wrong for all the pc's but somehow the Win7 boxes power through it where the XP boxes can't.  All my Win7 stuff is more powerful than any of my XP stuff but most of these XP boxes give plenty of FPS and they're the same boxes that we played through EoB 1 with.
               
               

               
            

[Legacy_Pstemarie]

               Microsoft has discontinued support for XP - maybe something has come up with drivers that has rendered XP obsolete. We have a few XP boxes at work and they have become so unstable over the last few months that now you can't do anything with them beyond mediocre tasks. Software that used to run fine now crashes and burns faster than the IT guys and techs can fix it. The computers are so bad that the company finally ordered replacements.
               
               

               
            

[Legacy_Dark]

               I tried it in SP, same issue. The tileset was built with the original Castle Tileset.  It seems like this is a txi issue or shadows, etc on edgetiles. Edgetiles are not supposed to have animations, walkmeshes or tile lights.  So this is being looked at currently.  

This was Robs dungeon to begin with, but all of the textures were changed out with new ones.  It’s possible that a texture might be causing this.  I know that a lot of the textures are larger than 256x256  could that be a problem?  Some are set to 512x512.
               
               

               
            

[Legacy_Rolo Kipp]

                <updating...>

Just to be clear on what I am doing and what I am *not* doing...

I am extracting all the tileset models, running them through CleanModels 3.5 (default setting), then compiling the output and bundling it back into a slightly renamed (Mac/Linux-friendly) hak. Put that hak above the old hak, then remove the old hak and test.

Looking at the log so far I am seeing a *lot* of repivots, again suggesting shadow issues.
Also, so far *every* aabb plane has been set to render with shadows... all being reset.

512x512 textures are not a problem. Odd-size textures would be. They *must* be a power of two (256, 512, etc.). But then they simply wouldn't show up in game :-P More woried about txi, or reflection mapping for the textures.

For the Aqua tileset :

450k fixes
**** mbq30_b02_06.mdl failed to load
**** mbq30_d02_01.mdl failed to load
**** mbq30_d02_03.mdl failed to load
**** mbq30_d04_01.mdl failed to load
**** mbq30_d06_01.mdl failed to load
**** mbq30_d15_01.mdl failed to load
**** mbq30_e03_01.mdl failed to load
**** mbq30_e06_01.mdl failed to load
**** mbq30_f04_01.mdl failed to load
**** mbq30_f11_01.mdl failed to load
**** mbq30_g04_01.mdl failed to load
**** mbq30_g06_01.mdl failed to load
**** mbq30_g07_01.mdl failed to load
**** mbq30_j02_01.mdl failed to load
**** mbq30_k08_01.mdl failed to load
**** mbq30_k09_01.mdl failed to load
**** mbq30_l02_w2.mdl is too buggy to output
**** mbq30_p02_01.mdl failed to load
**** mbq30_q02_01.mdl failed to load

For Castle:

1.5 million fixes!
**** fla01_l02_w2.mdl is too buggy to output

For Woods:

920K fixes
No fails

For Crims:

1.2 million fixes
**** cla01_l02_w2.mdl is too buggy to output

For tro06:

1.4 million fixes
**** tro06_l02_w2.mdl is too buggy to output

For tfc01:

1 million fixes
No fails

For marble:

228K fixes
**** mbc30_b02_06.mdl failed to load
**** mbc30_d02_01.mdl failed to load
**** mbc30_d02_03.mdl failed to load
**** mbc30_d04_01.mdl failed to load
**** mbc30_d06_01.mdl failed to load
**** mbc30_f04_01.mdl failed to load
**** mbc30_f11_01.mdl failed to load
**** mbc30_g04_01.mdl failed to load
**** mbc30_g06_01.mdl failed to load
**** mbc30_g07_01.mdl failed to load
**** mbc30_q02_01.mdl failed to load

Those models could not be run through CM. Log goes into more detail, but I'm moving on...

<...an update>
               
               

               

                     Modifié par Rolo Kipp, 16 août 2013 - 07:13 .
                     
                  

            

[Legacy_Dark]

               Hey Rolo,

Thanks, at least you are seeing issues in the tilesset. so thats a good sign that it what is causing these crash issues.  kind of odd that Win 7 does not see this dont you think?  Would this possibly cause issues with performance in those areas?
               
               

               
            

[Legacy_Rolo Kipp]

               <tentatively states...>

The math library was one of the updates to Win7. I think it just handles fatal errors more elegantly. The problems are still there, but Win7/8 gets back up and staggers onward.
My opinion.
Edit: Yes. I think this is causing big issues with performance. On load at the very least.

<...his firm opinion...>
               
               

               

                     Modifié par Rolo Kipp, 16 août 2013 - 03:22 .
                     
                  

            

[Legacy_Dark]

               Okay, I kind of figured it might be.

Thanks again Rolo for taking the time to look this over and hopfully fix it.

I owe ya '>
               
               

               

                     Modifié par Dark, 16 août 2013 - 03:48 .