 |
 |
UNREAL doesn't work with QT4, uninstaller doesn't complete the job
|
 |
|
 |
|
mike one
|
|
after installing QT4, unreal freezes my B&W consistantly, right before the demo/fly through screen.
upon removing QT4, and reinstalling QT3 the problem goes away.
note: i reinstalled QT4 a 2nd time, same problem.
I didn't feel like trying to disable the all too numerous extenstions installed with QT4.
also the uninstall feature of QT4 does not remove the sound manager extension (which the installer updated) nor does it remove the AT plugins, you need to remove all plugins manually before trying to use your internet browsers.
also the QT control panel is removed by the uninstall thus making certain functionallities of the finder unuseable, such as the internet search feature of Sherlock. QT 3 reinstall will correct this problem.
|
|
|
| |
|
|
|
 |
|
 |
|
Rumplestilskin
|
|
if anyone finds a way to make Unreal run on a Blue and White G3 with Quicktime 4 installed PLEASE let me know! Right when the fly-by should start, all you (I) get is a black screen and a freeze. please post!
|
|
|
| |
|
|
|
 |
|
 |
|
JoseCruz
|
|
Dear Mike one and Rump,
I found that if you set the monitor to it'ss native resolution before you start, Unreal (ver. 1) will boot properly. In my case My 17" studio display boots at 832*624 resolution AND set at 256 colours. I only had time to check that startup resolution/ccolour depth. Tomorrow I'll try others. I had the same problem as both of you until I tried this.
BTW my B&W is a 300/512 with a Jackhammer Ultra SCSI card I run the Japanese version of OS8.5.1 and an assortment of third party stuff (including Now Utilities ver.5) alongside QT4b
Good luck, post how it works out.
Jose Cruz
------------------
|
|
|
| |
|
|
|
 |
|
 |
|
Spencer Olson
|
|
Well, comforting to know I'm not the only one having trouble..
Furthermore, Unreal no longer recognizes my Rage 128 card [b&W 350]. I think it may be related to the new ATI drivers, from the OpenGL package.
Obviously, software rendering is disappointing enough that I don't play long enough for it to cause a crash!
Spencer Olson
|
|
|
| |
|
|
|
 |
|
 |
|
Dr_Stein
|
|
Do you have the current Unreal updates? 220b3 is the newest.. I have qt4 on my G3/300 and have had zero problems..
|
|
|
| |
|
|
|
 |
|
 |
|
Rumplestilskin
|
|
How do I know what my monitor's Native-resolution is? I too have the 17" studio display. I'll try 832x624 at 256 colors like you did and see what happens. BTW, I do have version 2.2.0b3.
Dr. Stein, do you a Blue and White or Beige G3 (new or old)? Please post.
|
|
|
| |
|
|
|
 |
|
 |
|
Rumplestilskin
|
|
It worked! I set my monitor to 832x624 and 256 colors like you said and it didn't crash!
YAY!! Any idea WHY it will crash at other resolutions?
|
|
|
| |
|
|
|
 |
|
 |
|
JoseCruz
|
|
I'm not really sure why it worked, or why I even thought of it, but I found a little bit more useful info.
You probably, like me, started up Unreal full screen. I think that's what gives the Rage card the willies when the monitor is set to anything besides it's native setting.
I disscovered that if you just set the game in it's advanced options ("Game Settings" I think) to NOT start up full screen, you'll be able to start up at any resolution and colour depth you like without crashing.
then after it starts up switch to full screen and play. Before quitting the game make sure that you go back to non full screen mode and all will be well for the next game too.
Jose
|
|
|
| |
|
|
|
 |
 |
|
 |
| |
|
|
|

|
|
 |
Forum Rules
|
 |
 |
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
 |
 |
 |
 |
|
 |