Project Reality Forums

During the last couple of days I've had some issues when trying to play PR.

I've started the game and loaded into a server, only to be unable to see the ground, which kinda ruins the game for me, as I might be able to see the enemy at all times, but I have no idea wether he's behind a hill or not... :/

There's also the risk of being banned after PBSS' and stuff like that, so I would greatly appreciate it if someone was able to help me find a solution for this

Images of the "groundhack":





I also tried screenshotting the settings, but that did not work, so I will edit them in shortly. (possibly in some time as it smells like dinner is close to done )

Edit:

Resolution: 1280x1024 (native resolution of my screen)
Terrain: Medium
Effects: Medium
Geometry: Medium
Texture: Low
Lighting: Low
Dynamic shadows: Off
Dynamic light: Off
Anti-aliasing: 8x
Texture filtering: Low
View range: 100%

Specs:
ATI HD Radeon 4570
6 GB RAM
Intel E6300 2.8 GHz

Edit2: And seeing as I just finished eating and had the time to search, first hit is a possible fix, on this very forum...
https://www.realitymod.com/forum/f27-pr ... arent.html
Yet to see if it works though

opened exact the same topic some days ago, i also found that thread you posted and this helped my directly:

MadTommy wrote:i've had this issue.

What fixed it for me was...

Under BF2.exe properties, goto 'compatibility' tab and tick; 'Disable visual themes' and 'disable desktop composition'.

After doing this i have not had the issue reappear.

btw have you both FH2 and PR installed? seemed to me to have caused the problem.

I did that but it didn't help, also deleted my shaders :/

And yes, I do have both installed, but I haven't played FH2 for ages, and PR worked just fine before christmas

Do not use ingame Anti-aliasing (AA) and CCC AA at the same time.
Give it a try with AA completely off.

CCC (assume that the Catalyst thingy) AA was not turned on, and it made no difference turning the one ingame off. Looks like a reinstall is imminent...

the bug occured around christmas with me too.

so there might be some windows update or similiar which caused the problem.

as i see more and more guys here got this bug.

yup, this just happened for me too.

mightymints wrote:yup, this just happened for me too.

Could you tell me your system specs please? I'm having this problem too and am now looking for the cause and the fix for it.