#46 Nifskope crashes when selecting from view window

closed-out-of-date
Theo Habit
NifSkope (75)
5
2009-06-13
2008-09-18
Arthmoor
No

Here's a real stumper. I just upgraded from an nVidia 8800GTX to an AMD Radeon HD4870 video card. Nifskope ran flawlessly using the nVidia but has developed an annoying problem while using the Radeon. The video card upgrade is the only thing I've done to the system at all.

When I open a nif file and the image is displayed in the render window, I cannot click on any portion of the actual image or the application crashes with a Windows error dialogue. The best I've been able to capture from the crashes is this:

"Faulting application nifskope.exe, version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x0698df0f."

The fault address is random though. This happens with every nif file so far I've tried it with. I cannot select anything by using the render window. However, I am able to navigate the entire node tree on the left and manipulate the data as normal. Even including removing blocks and such from the image. However once I've clicked there, I can no longer click on the render window at all for any reason, in any part of it. The problem affected Nifskope version 1.0.12 so I came by to check for upgrades, and sure enough you have 1.0.14 now. I've installed that and the problem still exists.

I'm able to work around the problem for now but it's definitely slowed my ability to work with the program in a bad way.

I'm not sure how much it will help, but here's a rundown of my system specs:

AMD Phenom 9850 2.5Ghz
Sapphire Radeon HD4870 1GB (single, not an X2, no crossfire)
Catalyst 8.8 release drivers downloaded from game.amd.com
4GB Corsair high performance RAM

If you need anything more, let me know. I realize it's pretty vague and randomish but I'm not really sure what else to dig up right now.

Discussion

  • Amorilia
    Amorilia
    2008-09-18

    Thanks for reporting. Since none of the devs here can reproduce the problem, this sounds like a bug in your graphics card driver, crashing on particular OpenGL calls. There's nothing we can do about that unfortunately, so you're probably gonna have to wait for a driver update from AMD, or try a few older drivers instead (if that's possible with your new card...).

    If other drivers don't help, it may also be a Qt bug. In that case you could try with nifskope 1.0.9 (uses Qt 4.3.4) or nifskope 0.9.8 (uses Qt 4.2.3).

    I'm sorry that I can't be more helpful. I'll reassign this to tazpn who has a much better idea of how the OpenGL part of nifskope works, and perhaps he has a better idea.

    Cheers,
    Amorilia

     
  • Amorilia
    Amorilia
    2008-09-18

    • milestone: 530614 -->
    • assigned_to: amorilia --> tazpn314
    • status: open --> open-accepted
     
  • Arthmoor
    Arthmoor
    2008-09-18

    Something of interest in this I stumbled on by accident. I was updating some lowpoly LOD objects and realized that I could click into the render window on some of those and not others. Turns out that strips/shapes with no tangent space data defined don't crash when their segments are clicked on in the render window. When I told it to update all tangent spaces in the nif, clicking on any segment in the render window results in the crash.

     
  • sandman
    sandman
    2008-10-12

    i have the same thing happening to me, nifskope worked wonderfully on my old computer which had an nvidia card. now im using an ATI 4870x2 card and if i touch the render window with the mouse nifskopes crashes.
    allthough ive found an workaround for it though, disable shaders under the settings menu

    my specs are
    Motherboard: ASUS P5E Deluxe
    CPU: Intel Core 2 Quad Q9550 2.83 GHz
    RAM: 4GB Corsair Dominator
    Graphicscard: Gainward Radeon 4870x2

     
  • Arthmoor
    Arthmoor
    2008-10-15

    Confirmed on disabling shaders. I just tried the same and am able to click on the render window. It's a kludgy workaround though because you can't see the model in full detail without the shaders :/

     
  • Sen-chan
    Sen-chan
    2008-10-18

    I'm also having this problem when I switched to a Sapphire Radeon 4850. I thought it was just me. Oblivion runs fine, no problems, so it appears just nifskope has an issue with the card by the whole crashing thing. Hopefully this can be fixed up. Considering several other people aren't having a problem, they're using NVIDIA cards. It's something of the way that the new radeon cards are handling it. I'll keep checking up to see if there's any news and turning off the shaders for now.

     
  • Amorilia
    Amorilia
    2009-04-04

    There is a chance that the new Qt 4.5.0 fixes this. The upcoming release of nifskope (1.0.19, soon to be released) will still be based on Qt 4.4.3, but the nifskope lead devs plan to move to 4.5.0 after that. Anyhow, I've quickly put together a Qt 4.5.0 build for you to test:

    http://www.sendspace.com/file/i6qpbd

    Can someone try this out and see if it fixes this particular OpenGL problem?

    Be warned though that Qt 4.5.0 has not recieved much testing from nifskope, so this build might break other things (although I haven't noticed any problems myself yet). But if you notice other problems with this build you may of course also post them here on the tracker. :)

     
  • Amorilia
    Amorilia
    2009-06-13

    • status: open-accepted --> closed-out-of-date
     
  • Amorilia
    Amorilia
    2009-06-13

    I assume this has been resolved in the mean time (by a Qt update, or otherwise), so closing. Feel free to comment on this issue and we can open it again.

     
  • FlagellumDei
    FlagellumDei
    2010-08-30

    I'm running Nifskope 1.0.22 (revision 8329d39) under Windows 7 x64 (Ultimate) on a Phenom 9850, 4GB RAM, Ati HD4870 system. Regardless of the Catalyst version (I tried older and recent versions, now running Catalyst 10.6), when I left-click on any mesh part in the Render window, Nifskope crashes. Left clicking OUTSIDE the mesh is fine. I can select mesh section by clicking on the Nitrips block, but left-clicking anywhere on the mesh results invariably in a crash.

     
  • Arthmoor
    Arthmoor
    2010-08-30

    This is definitely not fixed yet. I'm also now running Nifskope 1.0.22 on Win7x64 (Home Premium) with Catalyst 10.6 etc. Enabling shaders and then clicking anywhere on the mesh causes it to crash and send a Windows error report.