Quake3World

I just bought a new laptop with an integrated graphics card along with vista. When reinstalling GTK Radiant 1.4 i stumbled upon a problem, take a look:

the 3d window does not draw brushes correctly when they are partly off the 3d window. I have never seen this before in Radiant (maybe im missing an option somewhere)
What I have tried so far:
-Make sure the Quake dir and the GTK dir have Read/Write permissions
-run Radiant1.4 in admin mode
-reinstall Radiant1.4
-update video drivers
-reinstall Radiant1.4 with new drivers
-install rollback drivers
-reinstall Radiant1.4 with rollback drivers


My system:
Acer Extensa 4630Z
Intel GMA4500
2GB RAM
Vista Home Premium (second suspicion)

Anyone have any ideas on how to fix this? It makes level editing almost impossible.

Wow, that IS weird looking!

Are you using Intel's video driver or the latest ones from Acer. On some laptops, manufacturers may prefer their own set of drivers over the Intel graphics drivers, try those instead.

Do you get the same problem with GtkRadiant 1.5.0?

I doubt if it's a problem with Vista.

This can't be a problem or a bug with nearest midmap settings and the like, can it? I suppose it would look a bit different then.

Did you try disabling Aero and switching to XP Compatibility Mode for Radiant? A while back, I got the problem, that my viewports didn't update until I tried these options.

I get the same error on my Asus Eee PC 901.

This is a bug not uncommon in integrated GPUs. The easiest solution, apart from hoping Intel will someday roll out drivers that fixes it, is to buy a cheap NVIDIA or ATI card and use that.

Since his system is a laptop is quite unhandy to buy a cheap graphic card
And external cards like the ones for USB are usually not fast enough for complex renderings and also eat up too much CPU performance.

obsidian wrote:Are you using Intel's video driver or the latest ones from Acer........

Do you get the same problem with GtkRadiant 1.5.0

I tried it with the default drivers that came from Acer, then I tried it with the newest from Intel, and then I tried it with the second newest from Intel. I will check and see if Acer has any newer ones.

I have not tried a newer version of Radiant. I might give Zero a try.

maz0r wrote:Did you try disabling Aero and switching to XP Compatibility Mode for Radiant?

I have not tried this.... i have about 1 week of vista experience!


/me waves to ^misantropia^ ....... its CLUTCH from the PQ forums.

I'm new to Vista too (Ultimate x64). Don't see what all the negative fuss is about, it works fine.

I haven't seen your particular problem. On my computer, the 2D grids don't render by default.

Find the GtkRadiant.exe and right-click > Properties > Compatibility.

I checked the box "Disable desktop composition" and that fixed things. Other people have reported needing to check "Disable visual themes" and "Run this program in compatibility mode for Windows XP". Experiment with that and see if that helps (though I think it's still more driver related).

Ok, make a new shortcut for GtkRadiant, right click it and go to Properties.
In Compatibility check the boxes 'Disable visual themes' and maybe 'Disable desktop composition'. Make sure that you enable also 'Run this Program in compability mode for "Windows XP"'.

Here's a screenshot of the mentioned dialog:


Edit: Damn obsidian was faster with that

YOU SNOOZE YOU LOSE!

I may be new to vista, but Google has been around for ages!

I played around with compatibility mode and the only restlt I got was checking "Run in 256 colors" and it actually rendered the 3d window... but as you can imagine, it made it impossible to use because I couldn't see anything else.

Thanks for your help guys. I'll let you know if I find anything.

Sorry for activating a dead topic, but I have been having this problem too - except I have Windows XP.

If you're having the same problem as above using an integrated GPU, you may be stuck unless you can find a way to upgrade.

^misantropia^ wrote:This is a bug not uncommon in integrated GPUs. The easiest solution, apart from hoping Intel will someday roll out drivers that fixes it, is to buy a cheap NVIDIA or ATI card and use that.

Indeed. I'm also having a nasty bug with the camera, XP and an integrated X3100 (Intel Mobile 965 Express Chipset) here. As soon as I open the texture window the first time after starting radiant, all the textures in the camera window are totally fucked up. Here's an example: before, after opening texture window.

Here's another ugly example:
Radiant intel bug


I talked to the netradiant developers about this and they assured me that it was an issue with the driver. I'm using the latest driver IBM/Lenovo offers for my Thinkpad. There's newer drivers for the chipset on the intel website, but they refuse to install with the message This driver was not tested by the manufacturer of your hardware, aborting installation. or similar bullshit.

Idea: if someone could install the driver on his box and send me the .inf files, it could work (unless the latest Intel version is also broken). Augwich, are you using the latest drivers from Intel or from some laptop manufacturer? Which chipset does your card have?

Try this... I spotted the .inf files in the downloaded zip file which you might be able to use to manually install the driver.

I don't have an Intel GMA to test this myself.

http://downloadcenter.intel.com/Detail_ ... l&lang=eng

Works, inf file is in there. Though it was an installer exe you downloaded, but it isn't.

Just unzip the archive, search the inf file and right click => install. Reboot. Done.

The file you want is Graphics/igxp32.inf.

EDIT: No, it doesn't. Bug reappeared.

I asked about this issue on another forum, and here's there answer. I tried it, and it worked beautifully, so I thought that I would mention it here:

goto start run and type in 'devmgmt.msc' without the quotes.

Open the drill down menu for Display Adapters and it should tell you what card you have. If you do have an ATI card, you could try ticking the box in Radiant Prefrences 2D rendering ATI cards with broken drivers - bug #802

Then restart Radiant and see if that helps.