Got a small issue... maybe someone here has encountered it and solved it already.

I had to replace my hard drive. Upon re-installing all of my modding apps (Blender, nifSkope, nifTools, etc) I have encountered this issue where nifSkope will crash immediately upon clicking directly on the object in the render window. I can do everything else just fine, but clicking directly on the object causes the generic " ****.exe has encountered a problem and needs to close" error message, then nifSkope closes. I can click on the render window, not directly on the object, and rotate the object at will, and nothing happens. I can change/attach/remote/etc values on the block list or block details, nothing happens. It is just clicking directly on the object, either the mesh or the collision box, that causes nifSkope to crash.

I have tried 3 different versions of nifSkope. First I installed the version I had used in the past ( I kept all the modding tools) and downloaded 2 others, exact same result. I have re-installed nifSkope in the past, and I've been using different versions of it the past 4+ years, and this is the very first time this occurs.
I''m using the same OS (XP SP3) and this installation is an OS image one of my co-workers made for me(a MCSE or whatever they are called, Windows winnies ) , so I don't do anything during install other than boot from the disk, choose the size of my partitions, and it installs hands free after that.

Anyone has seen this before?

All the time. I've simply gotten used to avoiding the mesh in the preview window. Even with shaders turned off in the render settings it still does it.

Well, Took me longer to type the original post than to find the answer

For future reference:

Open an image on nifSkope.
Got to Render > Settings...
On Rendering tab, deselect Anti Aliasing. I left shaders and textures selected. Close nifSkope.
Upon reopening nifSkope, you can click on the meshes and it won't crash...


Funny, I don't remember doing this the first 4-5 times I installed nifSkope on the exact same system

Not sure yet if that works, but I was able to click around on a mesh with both AA and Shaders turned off. If I turn either one on, it crashes without fail.

LOL -- On mine its shaders only --- I can leave AA and textures on and no crash but enable shaders and click in the render window and instant crash !!

Heh, well. Maybe time to file a bug report

Faulting application name: NifSkope.exe, version: 0.0.0.0, time stamp: 0x4ba1e91e
Faulting module name: atioglxx.dll, version: 6.14.10.10428, time stamp: 0x4d23df82
Exception code: 0xc0000005
Fault offset: 0x000a55cc
Faulting process id: 0x794
Faulting application start time: 0x01cbc71b6ceed391
Faulting application path: C:\Program Files (x86)\NifTools\NifSkope\NifSkope.exe
Faulting module path: C:\Windows\system32\atioglxx.dll
Report Id: aed5a533-330e-11e0-9be3-90e6baee94f2

Thing is, it could also be an ATI driver issue since the ATI file is what tanked.

Yep I think it is an ATI driver issue -- didn't have the problem on my old 7800GS but after upgrading the system about a year ago and switching to a 5770 had it -- took while to figure out what was going on but eventually found that unchecking the shaders made the problem go away and haven't had it crash since doing so. Just reenabled shader to check and sure enough instant Crash with the following details :

Filed a bug report for it, in case anyone is interested: https://sourceforge.net/tracker/?func=detail&aid=3175492&group_id=149157&atid=776343

I had this exact same crash after updating my ATI drivers. Very annoying. Rolling back to 10.4 drivers fixed it for me ( and got rid of that irksome white pixel line in my Oblivion game).

That white line thing is super annoying. There's an OBGE shader fix for it, which I've now tried, but it didn't help. Unfortunately AMD isn't doing anything with the bug reports that have been filed against that, and I doubt they're doing anything with the error reports from nifskope either.

I had/have this problem too, but usually get around it by RIGHT clicking instead of left clicking first in the render window. Then it won't crash for me. No idea why though. It also is not with all meshes that it would crash on a left click, usually only on the bigger ones.