Results 61 to 64 of 64
Thread: X5 3D View Issues
-
09-03-2012, 12:40 PM #61
Chief doesn't recommend it, I wonder why.
Perry
P.H. DESIGNS L.L.C.
Eastvale Calif.
Alienware, liquid cooled
Ver 10-"X6 x64 SSA
WIN 8.1 PRO 64 bit
Nvidia GTX780 3GB.
i7 920 2.67-- 12 GB Ram
40" led monitor
-
09-03-2012, 01:00 PM #62
Perry:
I agree...
XP may work with newer versions of Chief
but does it work well ???
LewLew Buttery
Castle Golden Design - "We make dreams visible"
Lockport, NY
716-434-5051
www.castlegoldendesign.com
lbuttery at castlegoldendesign.com
CHIEF X5 (started with v9.5)
-
09-03-2012, 01:07 PM #63
Thanks Lew, I was wondering why someone hasn't said the same thing.
Perry
P.H. DESIGNS L.L.C.
Eastvale Calif.
Alienware, liquid cooled
Ver 10-"X6 x64 SSA
WIN 8.1 PRO 64 bit
Nvidia GTX780 3GB.
i7 920 2.67-- 12 GB Ram
40" led monitor
-
09-04-2012, 06:23 AM #64Administrator
- Join Date
- Jan 2000
- Posts
- 4,161
We don't recommend XP. But not for these reasons.
The video card and XP don't have anything to do with how the ray trace is working. In fact the video card doesn't affect ray tracing at all.
Primarily we don't recommend XP due to deficiencies in the user interface and the poorer support of multiple core cpus.
XP is slower for several reasons. Under Vista/Windows 7/8 we don't have to redraw things nearly as often and the better support of multiple cores gives a slight edge in performance. The difference is in general fairly minor.
We don't test on XP as much so have lower confidence that we understand all the issues with XP.
We are also seeing poorer support for video cards under XP.
And XP doesn't support 64 bit which also gives a slight overall edge in performance and a big edge if you need to access more memory.
There are lots of good reasons not to use XP, but functionally Chief should work right on XP. In almost all cases where we see something that doesn't work right on XP it also doesn't work right on other platforms.Doug Park
Principal Software Architect
Chief Architect, Inc.