Testing Spring 0.77a

[Crayfish]

I built some of the same core things that you have there and didn't get any invisibles. Also my radar was fine.

[[Krogoth86]]

Well I also can see this when planning things:


You already have just this one colored geometry here which then completely dissappears during the final nano stage (the wireframe and the filling is visible during construction - just not the final textured stage)...

I'm just having these problems with the new 0.77a version...

[jK]

seems like you didn't set AtiHacks on 1.

[[Krogoth86]]

Ah ok, forgot to set that to one - works now...

[Satirik]

seems like you didn't set AtiHacks on 1.

maybe it should be enabled by default no ?

[el_matarife]

I wonder if there's some commonality in driver versions that are causing some of these issues, and if there's a driver version that actually works. Do you guys think it'd be a good idea for people to upload GPU-Z screenshots? All you have to do is download it: http://www.techpowerup.com/gpuz/ run it, click the camera in the top right corner and it can upload it to free hosting for you.

[reivanen]

Here some of my issues I have encountered so far:

Mod-specific (CA):
Some Core things just won't show up ingame - i.e. they are there and can be selected but are invisible. It also seems they have no collision geometry at all (at least it doesn't get shown):


Non mod-specific:

• Ground decals don't work anymore. Instead of the graphics you get grey geometry:
  
• Radar Icons don't work - you just get colored rectangles for everything:
  

EDIT:
System specs:
- Phenom 9850
- ATI HD4870 (Catalyst 8.7)
- Windows XP Pro SP3

I got the same problem with units that are not there when trying pure mp beta 1, CA works just fine though.

[Hoi]

you need to make atihacks 1

[reivanen]

I have a 8800 so the atihack feature should be renamed if it fixes issues with nvidia cards also :)

[AF]

Are there any cases where enabling ATIHacks actually causes bugs under some cards?

[imbaczek]

No idea.

[AF]

In the next test installer release lets enable ATiHacks by default and see what happens. Lets identify as many errors we can correct that will work for everyone, and possibly any code that could detect that the errors could occur and run conditional code that corrects them for those affected.

[Kloot]

atihacks also affects build anims, it should NOT be enabled by default.

[imbaczek]

It probably should be split up into smaller components, as was suggested before, and those should be available in the expert settings. I don't have the knowledge what they actually do and how to call them, though.

[koshi]

Please, when you split them up, don't just go for individual options, but rather functional groups. Imo there's already enough options in the Gui.

[Kloot]

What atiHacks does as of r6302:

• * disable custom clip planes for unit nanoframe rendering
  
  * rescale (named) NPOT textures in nearest texture filtering mode
  
  * (commented out) force an older-style mipmap generation method

So I'd suggest splitting into atiClipPlaneHack and atiRescaleTexHack, or
whatever other beautifully descriptive names you think are appropriate
for your settings program.

[Peet]

I think it's a good idea to split them up for the pre-release stage, then put them back into grouped options for the actual release, once it is determined which combinations work on various hardware configurations.

[imbaczek]

hopefully fixed comsharing with AI bug.

[el_matarife]

Next question: Do you think it makes sense to develop some "test renders" along with screen shots that could be included in settings? Basically, render one of these test cases, then show a screen shot of how it is supposed to look and say "if it looks like this click yes if not click no" to enable or disable the hacks for that particular rendering method.

[imbaczek]

that'd cool, but a lot of work, no? or am I mistaken?