I was unable to find this topic via search, so my apologies if this is already a known issue.
Otherwise, here is the bug:
TG2 will immediately crash if the image map shader is used, set to projection, and the cursor is placed over the preview window (and possibly over the fractal preview window as well). It seems to crash every time, and has seems to have been a bug since day one. Luckily its not a debilitating crash, you just have to be careful not to drag the cursor over those 2 areas and you'll be fine.
Many thanks for your updates and bug fixes so far.
How do you mean "set to projection"? through camera, one of the Plans, UV?
Is this in Tech Preview 4? I can't reproduce this problem, with any projection settings. Which projection setting did you use? Does it happen with any image you try, and how is the shader connected in your scene?
Matt
Hi Matt,
This may have been going on since the first release of the tech preview. I remember it happening way back.
I just realized it works when I use the image map shader by itself (tech preview 4). However, when connected to a default shader, it crashes. I've attached a zipped folder with the scene file so you (or anyone else who wants to) can see what happens.
Many thanks for looking into this. Hopefully its an easy fix.
-Jeff
Seems there is no way around this. Hopefully Matt can take a look.
I'm getting this too now, but only since TP3 that I can remember. I didn't do a whole lot with image map stuff before now (WM2! Yay!) but it's occuring in the same way as moodflow's describing it: everything's fine until the mouse is over the preview window, then Bam! Like, 16 render bucket errors, and crash.
Many thanks for confirming the bug. 8)
on my computer it crashes as soon as i try to move in the preview windows (like trying another pov)...
since the first Tech preview release.
Hi Jeff,
I can get your example file to crash both the latest Mac and Windows versions straight off, and it's not for a very mysterious reason. Well, there may be something mysterious leading to what triggers the bug, but what triggers it is clear and repeatable so it shouldn't be too hard to fix with any luck. I'll file a bug about it and assign it to Matt ;-).
Regards,
Jo
The work around is to add the image map shader by right clicking on the node screen and adding the node from the menus there so it is not linked into the node network, add your image, select your camera and projection and then link it into the network.
Richard
I also found another work around (as I was simply using the default shader as a "catch all" for reflectivity, luminosity, displacement, etc.). The workaround is to use these separately as their own node - but I did want to bring it up to the development team.
Quote from: jo on July 08, 2008, 06:47:13 AM
Hi Jeff,
I can get your example file to crash both the latest Mac and Windows versions straight off, and it's not for a very mysterious reason. Well, there may be something mysterious leading to what triggers the bug, but what triggers it is clear and repeatable so it shouldn't be too hard to fix with any luck. I'll file a bug about it and assign it to Matt ;-).
Regards,
Jo
Thanks Jo for taking a look into this.
I would have thought that the simplest way to avoid the bug is to have the image map projection set to something other than "Camera Projection" as a default. The crash only happens when camera projection is selected (the default) but no camera is specified.
Richard