Vista and Q4 editing

Post by **Grudge** » Mon May 21, 2007 9:34 am

I read somewhere that there was some problems with running Q4radiant on Vista, due to OpenGL issues or something?

Is this true? Anyone building Q4 stuff on Vista? If it doesn't work, I can avoid reinstalling Q4 in vain.

Also, anyone using GtkRadiant instead of Q4radiant for Q4?

Post by **dichtfux** » Mon May 21, 2007 9:42 am

Grudge wrote: If it doesn't work, I can avoid reinstalling Q4 in vain.

I'd rather avoid installing Vista.

But seriously: from what I've heard so far there seem to be lots of problems with "old" software and vista. Don't know about q4 though.

Post by **d3mol!t!on** » Mon May 21, 2007 10:30 am

I think it's probably just because OpenGL programs perform poorly on Vista, though I haven't heard anything specific on Q4's editor so I can't really answer.

Post by **hemostick** » Mon May 21, 2007 2:43 pm

Provided you install actual drivers from ATI/NV instead of sticking to vista's built-in stuff, the infamous OpenGL "issues" should be a thing of the past.

From what we're seeing with regular q4 clients and Vista, you probably might want to run your +editor shortcut as admin, too.

Post by **Grudge** » Mon May 21, 2007 3:02 pm

cool, thanks

I've had a map layout stuck in my head for a couple of years now (ever since I finished my last Q3 map), and it's time to let it out before I go crazy.

Post by **Lukin** » Mon May 21, 2007 4:20 pm

I use Q4Radiant on Vista without any problems (although I would not recommend Vista to anyone atm). You might need to turn off Aero Glass to see Render preview. Also, I've heard about some issues with CRT monitors (refresh rate resets to minimal value sometimes or something like this) but can't tell you any details.

Post by **Grudge** » Tue May 22, 2007 8:15 am

Actually, I've been using Vista since January and it's been working great (apart from getting BSOD 50% of the time it comes out of hibernation, but I write that down to old hardware, I probably should update the BIOS on the motherboard).

Ok, I'm installing Q4 and giving it a shot. Thanks guys.

Post by **d3mol!t!on** » Tue May 22, 2007 11:23 am

Provided you install actual drivers from ATI/NV instead of sticking to vista's built-in stuff, the infamous OpenGL "issues" should be a thing of the past.

Yeah, sorry I forgot to add "supposedly" to my post, as I personally haven't noticed anything major. With the latest drivers for my 8800 GTX, OpenGL based games seem to run pretty comparable to anything else in regards to the kind of performance differences I remember them having on XP Pro.
Over all I'm also fairly impressed with Vista, and my over all game performance is okay too (though most of my games are the kind that get super powered by my Core 2 E6600, 8800 GTX and 2GB dual channel RAM system, so I find performance losses compared to what I remember from XP Pro are hard to notice).

Post by **dichtfux** » Tue May 22, 2007 3:43 pm

d3mol!t!on wrote:my Core 2 E6600, 8800 GTX and 2GB dual channel RAM system

:icon23:

Post by **Grudge** » Sun May 27, 2007 2:23 pm

Ok, I got the editor working in glorious 1680x1050 now, after some console trickery and shortcut tweaking. Seems like you have to run it in XP compatibility mode and with Vista basic theme ("Disable visual themes" and "Disable desktop composition").

But it's been three years since I touched Radiant, so I feel like a damn n00b now, not even remembering simple commands, lol.

Oh, and that latest 1.4.1 beta patch broke SP (crashes to desktop every time). MP works great though, ggz

Post by **Raven** » Thu Jun 07, 2007 4:25 am

It seems most of you have successfully gotten the editor to run with windows vista. I just upgraded my box and decided to mess around with some ideas, only to get a non-functional editor that does little more than look nice >.<

I am running the 1.3 patch, and the single player game plays perfectly.

I have the latest Nvidia drivers (released June 1st)

dual Geforce 8800’s

Intel(R) Core(TM)2 Quad CPU @ 2.66GHz

2 GB’s of DDR2 memory

Windows Vista 32-bit Home edition

I started up the editor, and set my preferences. I then tried to open a map. The map loads, or at least appears to load correctly, and when it is done I cannot do anything in the editor. The editor console will just SPAM the following errors any time I attempt something:

guid set to jXsylUrw5rg

ERROR: wglMakeCurrent failed.. Error:1282

Please restart Q3Radiant if the Map view is not working

ERROR: wglMakeCurrent failed..

Please restart QuakeEdit if the camera view is not working

ERROR: wglMakeCurrent failed..

Please restart QuakeEdit if the Z view is not working

The next thing I tried was reloading the editor and just building brushes. The editor will load up but it will not let me drop entities, move around the grid, or build brushes. It just spams the error above in the console.

I have tried the following:

1. Run as administrator
2. Run in winXp service pack2 compatability mode.
3. Run with the windows Aero theme disabled and in classic window mode.

Did any of you have this set of errors while you were getting your batch file to run?

Post by **Grudge** » Thu Jun 07, 2007 11:44 am

Hmm, I never got that error.

Did you make sure you're not using any AA? Both in nVidia control panel and in your config.

Post by **Raven** » Thu Jun 07, 2007 3:13 pm

That is actually a really good point, thanks ^^. I had AA off for the longest time by setting the quality tab to "Let the program decide 3d settings," but with the new Nvidia driver set I was able to set it back to quality for other games that I have been playing. I will shut all AA down and try again.
My fear is that the drivers themselves are the problem. It almost seems like the new driver set busted OpenGL in some way that does not allow the editor to accept focus and commands. I don't really want to revert the drivers either, because they have fixed glitches all across the board for me. I think I am having yet another set of issues with the 8800 card, and not vista itself.

Post by **dzjepp** » Thu Jun 07, 2007 3:15 pm

Hey I just noticed you work for Raven. You should bug one of the programmers there for a good Vista fix =)

Post by **Raven** » Thu Jun 07, 2007 3:22 pm

Hehe, I always go bug our poor programmers first as busy as they are ;;. I don't ask more than once though, because they are extremely busy making our current projects function ^^. I have actually gotten some good feedback, but we are not the ones releasing updates anymore. Id Software has been updating and adding content for the engine since early after release. I figured that somebody else has maybe run into similar problems on the forums, so I posted here as well.
Thanks for the help you have given me so far. What people have said here makes me really lean towards my 8800's and their driver set more than Vista.

Post by **Kat** » Thu Jun 07, 2007 6:45 pm

Grudge wrote:Hmm, I never got that error.

Did you make sure you're not using any AA? Both in nVidia control panel and in your config.

It's an error to do with using multicore CPUs.

http://www.katsbits.com/htm/tutorials/c ... m=&ucat=15&

Post by **Raven** » Thu Jun 07, 2007 6:57 pm

Perfect. Thank you Kat ^^

Post by **Raven** » Fri Jun 08, 2007 3:15 pm

I thought I would throw an update out since everything is working perfectly now ^^ Oddly enough AA and the fact that I have a Multi-core CPU were not the problem. It all came down to the fact that I updated my GeForce driver set after I had installed Quake4 and when I deleted my Quake4.cfg and editor.cfg everything worked perfectly the next time I loaded the editor and it created fresh ones. I later added +r_multiSamples 0 to my batch file, just in case I switch AA on for another game. Thanks for all of the info. in this thread, and thanks Kat for your research into this error.

Post by **Kat** » Fri Jun 08, 2007 4:07 pm

I can't find a ref in my own cfg but that means that the game is storing graphics card info in the CFG files which isn't being updated properly; removing forces it to update. I'll add this info to my common errors entry as that's 3 ways this error can crop up now! (thanks for reporting back/confirming btw)

Post by **EshQuIA** » Sun Aug 16, 2009 2:31 pm

Hey, sorry for bumping the topic up but I experienced smilar issues and I wanted to share my problems and their solutions in case someone may benefit from. Since I came accross Raven's topic, where I was redirected from, and Kat's link when googling the subject, the explanations here became my starting point. So I'm adding to this thread to keep things together.

I'm using Ubuntu 8.04 LTS and Windows 7 RC in dual boot. I spend my most time on Ubuntu and rarely boot Windows 7 since I don't need. Yes, I'm not playing PC games nowadays except Quake 3, it's installed on my Ubuntu and I'm enjoying it everyday.

In addition to that, I've installed Quake 4, configured it, fixed full screen problem with Compiz. Everything was OK. But when it came to editing, I couldn't launch the editor because of it's Windows API dependency. Like the LevelEditor, FXEditor and GUIEditor can't be run under Linux. I tried GTKRadiant but it's real time render mode was missing, it wasn't the same picture you see while rendering in LevelEditor, because it wasn't Quake 4. Maybe I did something wrong or missing, I don't know.

After that experience, I installed the game on Windows 7. I've never installed and used Vista before, so this RC is my first time experience with Windows 6.x family. After configuring the game according to my viewing pleasure I launched the editor and experienced the same symptoms as Raven did. "ERROR: wglMakeCurrent failed.. Error:1282" flood on console with blank pages on cam and grid windows. I tried different combinations of offered solutions in here such as running as administrator, not using AA, turning off SMP, setting different affinity, etc. and I've found perfect-well let's say almost perfect, it may be enhanced- solution for my case:

First of all, under properties of Quake4.exe, disabling desktop composition in compatibility tab is needed. There is no need to change other preferences in my Windows 7 RC case. Just put a tick for "Disable desktop composition" preference. You can also do that under properties of any Quake 4 link, it applies to all.

Second, the editor also doesn't get along with antialiasing and SMP. We have to disable them. Instead of turning these features off completely, disabling just for the editor is fine. We may need them under the game. I'm making this switch by adding commands as you do. The target lines of my links look like below:

For single player link:
C:\Quake4\Quake4.exe +disconnect +set r_mode 7 +set r_fullscreen 1 +com_allowconsole 1 +set developer 1 +set logfile 1 +set r_useSMP 1 +r_multiSamples 2

For multi player link:
C:\Quake4\Quake4.exe +disconnect +set r_mode 7 +set r_fullscreen 1 +com_allowconsole 1 +set developer 1 +set logfile 1 +set r_useSMP 1 +r_multiSamples 2 +set fs_game q4mp

And for my editor link:
C:\Quake4\Quake4.exe +disconnect +set r_mode 5 +set r_fullscreen 0 +com_allowconsole 1 +set developer 1 +set logfile 1 +set r_useSMP 0 +r_multiSamples 0 +set r_brightness 1 +editor

Note that my Quake 4 path is "C:\Quake4\Quake4.exe". And also note I'm playing the game under 1280*1024 resolution with 2x antialiasing plus SMP support.

My hardware specs are; Core2Duo E8200, 2GB RAM, 512MB 9600GT. I'm using 185.85 driver with the following settings for Quake 4 plus 16x anisotropic filtering:

Hope that helps someone who wants to make editing under Windows 7.

Vista and Q4 editing

Vista and Q4 editing

Re: Vista and Q4 editing

Re: Vista +(Windows 7 RC) and Q4 editing