These are my custom graphics settings... I wonder how they compare to those who also see these blotches.

 

 

 

[GRAPHICS]
TEXTURE_MAX_LOAD=1024
NUM_LIGHTS=4
MIPMAP_VC_PANELS=0
TESSELLATION=1
COCKPIT_HIGH_LOD=1
AIRCRAFT_REFLECTIONS=1
LANDING_LIGHTS=0
DAWN_DUSK_SMOOTHING=1
LENSFLARE=1
HDR=1
BLOOM_LEVEL=2
SHADOW_QUALITY=2
TERRAIN_SHADOW_CAST_DISTANCE=3
CLOUD_SHADOW_CAST_DISTANCE=3
OBJECT_SHADOW_CAST_DISTANCE=2
CONTENT_NO_SHADOW=0
INTERIOR_SHADOWS_CAST=1
EXTERIOR_SHADOWS_CAST=1
SIMOBJECT_SHADOWS_CAST=1
TERRAIN_SHADOWS_CAST=1
VEGETATION_SHADOWS_CAST=0
BUILDING_SHADOWS_CAST=0
CLOUD_SHADOWS_CAST=1
INTERIOR_SHADOWS_RECEIVE=1
EXTERIOR_SHADOWS_RECEIVE=1
SIMOBJECT_SHADOWS_RECEIVE=0
TERRAIN_SHADOWS_RECEIVE=1
VEGETATION_SHADOWS_RECEIVE=1
BUILDING_SHADOWS_RECEIVE=1
SHADOW_NUM_CASCADES_LOW=4
SHADOW_NUM_CASCADES_MID=5
SHADOW_NUM_CASCADES_HIGH=7
SHADOW_NUM_CASCADES_ULTRA=12
GROUND_SHADOW_TEXTURE_SIZE=2048
CLOUD_SHADOW_TEXTURE_SIZE=512
SHADOW_LOG_PARTITION_LOW=0.850000
SHADOW_LOG_PARTITION_MID=0.850000
SHADOW_LOG_PARTITION_HIGH=0.850000
SHADOW_LOG_PARTITION_ULTRA=0.850000
EFFECTS_QUALITY=1
EFFECTS_DISTANCE=1
[DISPLAY]
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=30
UPPER_FRAMERATE_LIMIT=30
TEXTURE_FILTERING=16
MSAA=8
SSAA=0
FXAA=0
VSYNC=1
TRIPLE_BUFFER=1
WideViewAspect=0
FullScreenExclusive=1
FullScreenAutoFill=1
[PANELS]
PANEL_OPACITY=0
[sCENERY]
IMAGE_COMPLEXITY=5
[TERRAIN]
LOD_RADIUS=6.500000
TESSELLATION_FACTOR=90
MESH_RESOLUTION=23
TEXTURE_RESOLUTION=26
AUTOGEN_VEGETATION_DENSITY=4
AUTOGEN_BUILDING_DENSITY=3
DETAIL_TEXTURE=1
WATER_REFLECT_CLOUDS=1
WATER_REFLECT_USERAIRCRAFT=1
WATER_REFLECT_SIMOBJECTS=1
WATER_REFLECT_TERRAIN=1
WATER_REFLECT_AUTOGEN_VEGETATION=1
WATER_REFLECT_AUTOGEN_BUILDINGS=1
WATER_REFRACT_CLOUDS=0
WATER_REFRACT_USERAIRCRAFT=0
WATER_REFRACT_SIMOBJECTS=0
WATER_REFRACT_TERRAIN=0
WATER_REFRACT_AUTOGEN_VEGETATION=0
WATER_REFRACT_AUTOGEN_BUILDINGS=0
ENABLE_BATHYMETRY=0
WATER_CLARITY=30
WATER_DETAIL=4
[WEATHER]
CLOUD_DRAW_DISTANCE=5
DETAILED_CLOUDS=1
OPTIMIZE_DENSE_CLOUDS=0
CLOUD_COVERAGE_DENSITY=6
THERMAL_VISUALS=0
DownloadWindsAloft=0
DisableTurbulence=0
DynamicWeather=2
VolumetricFog=1
[TrafficManager]
AirlineDensity=15
GADensity=35
FreewayDensity=10
ShipsAndFerriesDensity=20
LeisureBoatsDensity=25
IFROnly=0
AIRPORT_SCENERY_DENSITY=1
[AContain]
ShowLabels=0
ShowUserLabel=0
ShowLabelManufacturer=1
ShowLabelModel=1
ShowLabelTailNumber=0
ShowLabelDistance=1
ShowLabelAltitude=1
ShowLabelAirline=0
ShowLabelAirlineAndFlightNumber=0
ShowLabelFlightPlan=0
ShowLabelContainerId=0
ShowLabelAirspeed=0
ShowLabelHeading=0
LabelDelay=1000
LabelColor=FFFF0000

 

 

Try disabling the terrain shadow cast option and see if the blobs disappear...

Try disabling the terrain shadow cast option and see if the blobs disappear...

 

Er...? See my screenshots: how else did you think I made the one without the blobs...? ^_^ At first I wondered what was causing those odd blobs but after changing the terrain shadow cast distance to various disctances it immediately became clear the problem was terrain shadow.

Some good news... nVidia driver 340.66(Quadro/Grid WHQL) fixes the problem with Tessellation with P3Dv2.X.

 

You need to mod the inf to work with non workstation cards, but a Geforce version should be out very soon.

 

 

EDIT: blobby terrain shadows remain though.

Er...? See my screenshots: how else did you think I made the one without the blobs...? ^_^ At first I wondered what was causing those odd blobs but after changing the terrain shadow cast distance to various disctances it immediately became clear the problem was terrain shadow.

 

Whoops - sorry. Thought your question related to cloud shadows interacting with ground shadows. Back to our blobby blobs...

 

(I'd actually disabled ground shadows because of the unrealistic way they appear and disappear based on camera angle).

 

 

(I'd actually disabled ground shadows because of the unrealistic way they appear and disappear based on camera angle)

 

Indeed!... which may be part of the problem... I think even Rob Ainscough runs without terrain shadows, so unless he tests other settings during beta, this could be missed during testing... not that he's the only tester, but lots seem to follow his settings.

 

Despite P3Dv2 being far better than FSX, terrain shadowing in P3Dv2 has always been less affective than the older platform, as is water and cloud to view positioning.

This may have to do with time of day and the terrain shadows. I have been flying mostly in the morning or evening... but using the time preview I was able to get the blobs to show at around noon time.

I was able to get the blobs to show at around noon time.

 

Thanks for confirming Ed... maybe time to post a bug report on the LM forum Jeroen.

I'm curious if anyone has sent in a bug report to LM on this issue yet. I did a 100% fresh installation of my entire system and P3D v2.3 last night and I immediately noticed these strange ground shadows as well. I really don't recall these shadows being this harsh in past versions at all. (SIdenote - I'm also running the good 337.88 driver.)

 

I'd prefer not to turn the ground shadows off, as they used to lend some great effects to mountain flying, but if that seems to be the only solution as of this point, so be it. 

 

If there's any further input from the group, I'd be happy to read it....

-Greg

I'll be honest... I don't find the ground shadows to be of much value in most parts of the flying area. Because of that, I leave it off.

The shadows were like that in v2.2 as well, harsh and abrubt to a point of being a major visual deduction from the overall quality IMO.  I remember reading that in order to get the old FSX styled ground shadow back one has to turn off tessellation in P3D.

 

 

I'm curious if anyone has sent in a bug report to LM on this issue yet.

 

It's been reported on the LM forum but LM doesn't reply as much as they did in the past, so it seems.

I posted on LM forum for this problem., no answer yet. But you could go there if you want and answer to my post for it no to be forgotten.

I had it in V.2.2 but setting the terrain shadows distance to maximum used to fix the problem.

I have this as well with a slightly different twist... It almost appears as if mine are moving... 337.8 driver and did a fresh install of 2.3.