#3ds3-os/2 video problems
6 messages in this thread
I am having problems running 3ds3 under OS/2. 3ds2 ran fine, so I do not
suspect the dos settings. The problem occurs when I Ctrl-Esc back to the OS/2
screen. The OS/2 screen is very dark and distorted. When I switch back to 3ds3,
it locks up. Somehow, the 3ds and OS/2 video drivers are interacting. Any ideas
on how to fix this ?
Joseph Roseberry
70421,724
Bailey Brown is our resident OS/2 expert. Perhaps he has an answer for you.
Bailey?
– G
Hey Joseph,
Sounds like a problem I was having. What is your video driver setup? I've found
the only way 3DS will run is in VGA mode for the MAIN-DISPLAY. Just don't
ALT-ESC when rendering or in the MATERIALS-EDITOR. If you're desktop is running
on the same video card as 3DS, some sort of conflict happens and it all burns
down. The way I have it set is MAIN-DISPLAY at VGA, and the desktop at VGA. I
have yet to try running the desktop on my VIPER card and leaving 3DS at VGA –
that should work – just always remember to render to disc and turn off the
display, otherwise you get big time corruption!
Let me know if I can help further – I've messed with it for weeks! James
Jim: Thanks for the suggestion. I'll give it a try. Could this problem be
caused by the Vibrant driver ?
Joe Roseberry 70421,724
It may be the Vibrant driver but probably more an OS/2 thing. When you switch
from one session to the next, I believe OS/2 saves the screen image. At the
moment, it can't seem to cooperate with an application that uses the same video
display without OS/2 controlling it (which 3DS has to).
I guess it would be the Vibrant drivers, since they are accessing the video
card directly, by passing the OS – considered a no-no in some circles.
But I'm really not knowledgable on this kinda thing (the nuts and bolts) so
this is all speculation. I just know what works and doesn't work <g>.
James
Joseph,
You ran 3ds2 under OS/2? How did you do that? Did you apply the mythical
patch, the one whose existance Autodesk kept denying?
What kind of video card are you using? I've heard of somebody solving a
similar problem by setting VIDEO_8514_XGA_IO_TRAP=ON.
Bailey