Fix the grass!!!!
19.03.2013 @ 02:07 #4
19.03.2013 @ 02:16 #5
Its not just your modest pc. I have a good computer and it does that and there are problems even with the grass mod for TW2. Since EE i do not play the game often because its so annoying.
19.03.2013 @ 02:16 #6
BTW slimgrin have you ever seen anything like what I have in my topic? The sky and light go haywire and blocks the view of the player.
19.03.2013 @ 02:19 #7
19.03.2013 @ 07:20 #8
V1000 Cooler Master PS, 128g Samsung SSD, 1tb Black Western Digital HDD,
LG BluRay Burner, 2 EVGA 660TI in SLI OCed just a wee bit, In a NZXT phantom 630 case!
Asus Nvidia 3d 144mhz 24 inch monitor. Logitech Track ball, Mech keyoard, Razor Xbox Gamepad
19.03.2013 @ 12:12 #10
Geralt The Riv said:
Actually EVERYONE has the issue. Its only in Chapter 2 in the mountain areas.
Win7 64Pro/Win 8 Dual Boot
i7 2600k @ 4.6ghz
2x GTX580 Stock
24Gigs DDR3 1333 Stock
1250 Watt PSU
All settings Maxed (except motion blur off as I hate it)
Display @ 2560x1600
19.03.2013 @ 22:29 #11
All settings to High/Enabled except for
all of which are off because I dislike them
19.03.2013 @ 23:06 #12
19.03.2013 @ 23:08 #13
It is a specific fault (not a bug) introduced by CDPR. It isnt the PC causing the issue, or faulty code. Its an incorrect texture being loaded by default. Its incorrect code, not faulty code. Everyone that has the EE version has this faulty code. So yes, everyone has this issue. Lower spec PC's wont notice it due to everything else being set low and grass rendering being limited. If your setting has the grass being rendered then you'll see the fault. Its only certain areas, and only in chapter 2. Its minor but extremely distracting, and immersion breaking.
19.03.2013 @ 23:12 #14
That is exactly what I am talking about, but since when is it acceptable for ANY developer to let a fault go unchecked because some modders kinda/almost, but not really fixed some of the noticable affects of the fault. It isnt fixed, and is still there.
Its still laziness and imo crap that CDPR should have fixed a year ago. Not acceptable.
19.03.2013 @ 23:18 #15
In truth I don`t know why it`s still there . For myself it doesn`t bother me probably because it`s been there so long that I don`t pay attention to it .