Hi,
Sean has left the following comment at Determine why solids.sh fails on
64-bit http://www.google-melange.com/gci/task/view/google/gci2012/7982217:
could be
It's entirely likely that some platform presented the 3 off-by-many pixels
in 64 vs 32 bit and you observe the opposite in your setup. It's possible
that it was just recorded wrong too, but if you have it reproduced in
32-bit, that's certainly good enough to debug.
Even without understanding the math, it may help to find a specific ray
that gives the different values. Then you can just shoot that single ray
(via rt -Q or nirt) and follow the two paths in a debugger. The -X debug
flags may also be helpful (will give a bunch of printing statements).
Greetings,
The Google Open Source Programs Team
---
You are receiving this message because you are subscribed to Determine why
solids.sh fails on 64-bit.
To stop receiving these messages, go to:
http://www.google-melange.com/gci/task/view/google/gci2012/7982217.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_123012
_______________________________________________
BRL-CAD Tracker mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-tracker
