Official Fulqrum Publishing forum - A potential fix for the Aircraft visibility problems?

Official Fulqrum Publishing forum (http://forum.fulqrumpublishing.com/index.php)

- IL-2 Sturmovik: Cliffs of Dover (http://forum.fulqrumpublishing.com/forumdisplay.php?f=189)

- - A potential fix for the Aircraft visibility problems? (http://forum.fulqrumpublishing.com/showthread.php?t=34989)

Quote:

Originally Posted by Blennydude (Post 472329)

I watched your track. The text, as well as the actual aircraft "dot", is visible all the time; from the starting distance (about 1.20 or so), down to .80, where you slow down, and then up to around 5.30, where the text is no longer readable on my resolution - but I estimate it stays there up to 5.60 or so.

Then, I watched the track again, this time with MeshShowLod=1. This yielded the exact same result; the plane as well as the text remained visible all the time. Exactly the same, with no newly introduced stutters or so.

Meanwhile, on ATAG, I searched in vain for a 14-plane Ju88 formation, as advertised by "Chain Home" - nothing, except for a few flak puffs.
Then, I got shot down over France in the usual manner - Bang, Bang, critical dmg, Pilot dead - and after pressing Alt+F2, I was able to see the corresponding Me109 for the first time...
This must've been a happy time for the Me - Pilot :(

So I'm still at a loss and still begging for help! :mad:

P.S.: That other file, "confs.ini" in the Documents/1C.../il-2 sturmovik.../ folder has an option, under [core], called "LinearObjectManager(=1)". Could this be relevant in any way?

That's the thing the dot is there, people including my self will at time's loose track of it. Partly luck, but mostly looking in the right spot is the key. It really is a developed skill over a period of time. For myself I try to not take my eyes off of it, and to determine his heading. Many times if you loose it, look where it should be. If he spotted you, why then he could be anywhere trying to get on your six.

A possible recreation attempt??

http://serendip.brynmawr.edu/bb/blindspot1.html

Quote:

Originally Posted by David198502 (Post 471013)

and the disappearing problem is a specific spitfire problem they introduced with a patch...
at least for me, all the other planes stay visible...but the spit disappears completely..

i cant believe that this really annoying bug made it into the last update of clod......gosh im angry

I saw this behavior with an enemy Rotol Hurri, in an offline mission. Label and plane became invisible at 2.4 km distance, guestimated 400 m below me. Vanished for ~2 seconds then reappeared at 1.5 km. This was with MeshShowLod=1 in my conf.ini in the myuser folder.

Quote:

Originally Posted by SlipBall (Post 472343)

Hmm I don't really understand your answer. But if you're suggesting that I'm not looking hard enough, I am 100% positive that this is not the case. There's just no way. As I have written, planes which should be VERY close, also elude me... (yes, I check my six regularly).

Quote:

Originally Posted by Blennydude (Post 472444)

You were able to track my dot in the file, so I cannot say why you continue to have a problem. I hope that you find a cure:-)

ok meanwhile we tested on more systems, and it seems that three things are important to get rid of the disappearing bug...
resolution
model details
FOV

if you fly with a low resolution, use medium or low model detail settings and use a FOV higher than 70° you will be able to "create" a really big range where contacts totally disappear...

Holy hell, so I just jumped in singleplayer to test the colour modifications and... decided to play around a little.

What I found shocked me, there doesn't seem to be *a dot* anymore, for aircraft. Instead we are literally looking at the pixel that is the aircraft, when it was meant to have a dot, like ground forces. This dot literally does not exist. Because of this, the shape and size of the aircraft is paramount, at certain angles an easily visible aircraft becomes invisible and so on and so forth. The worst places is actually near the horizon, because aircraft so often fly straight and level.

I have video evidence (plain as day), but I don't know my way around video editing programs. If anybody could give me a quick how to it would be much appreciated. In the mean time I will build some .gifs, which I know how to make.

EDIT: OH, I almost forgot. Everyone post your settings (conf.ini) here. I'll sort through them and see if any of them actually work! First off, I'll try defaults but showmeshlod=1.

I agree. In the little experimentation I have done with InjectFX first contact ranges have increased dramatically ... unnaturally so. Aircraft at long range appear as a stark black pixel. To me they are of fixed dimension too. They dont seem to start as a tiny pin prick then slowly grow.

Well shit, disregard my last. Dots do not appear on your own aircraft (even if you zoom out all the way) so my whole argument is invalid.

well, my conf.ini:

Code:

[BOB]

EpilepsyFilter=0



[window]

  DepthBits  =24

  StencilBits=8

  DrawIfNotFocused=0

  SaveAspect=0

Render=D3D10_0

width=1920

height=1080

ColourBits=32

FullScreen=1

ChangeScreenRes=1

posLeft=0

posTop=0

Frequency=60

StereoMode=0



[NET]

  speed=25000

  localPort=3724

  serverName=My Server

  serverDescription=IL-2 Sturmovik: Cliffs of Dover

  serverInfo1=

  serverInfo2=

  serverInfo3=

  serverInfo4=

  VAC=1

  maxPlayers=16

  socksEnable=0

  socksHost=

  socksPort=1080

  socksUser=

  socksPwd=

localHost=

host=216.52.148.29

port=27016

SkinDownload=1



[Console]

  IP=20001

  UseStartLog=1

  WRAP=1

  PAUSE=1

  HISTORY=1024

  HISTORYCMD=1024

  PAGE=20

  LOG=0

  LOGTIME=0

  LOAD=console.cmd

  SAVE=console.cmd

  LOGFILE=log.txt

  LOGKEEP=0



[rts]

tickLen=30

;ProcessAffinityMask=3

maxTimerTicksInRealTick=20

; 0 - not use, 1 - show cursor and not capture, 2 - not show cursor, and capture

mouseUse=2

; 0 - not use, 1 - use if hardware exist

joyUse=1

; 0 - not use, 1 - use if hardware exist

trackIRUse=1

DisableIME=0

culture=en-GB



[rts_mouse]

SensitivityX=1.0

SensitivityY=1.0

SensitivityZ=1.0

Invert=0

SwapButtons = 0



[rts_joystick]

FF=0



[core]

RandSeed = 0

TexQual=3

TexFlags.PolygonStipple=0

Shadows=0

SpecularLight=2

DiffuseLight=2

DynamicalLights=1

MeshDetail=2

LandShading=0

LandDetails=2

Sky=3

Forest=1

VisibilityDistance=3

LandGeom=2

DrawCollisions=1

Water=-1

Effects=2

EffFlags.Light=1

EffFlags.SpriteRender=0

Grass=3

CordEffect=1

UseFog=0

UseLandCube=1

UseLandConnectedObject=1

LinearObjectManager=1

Roads=1

Sun=1

Clouds=1

EffFlags.LightSpritesProj=1

ShadowMapSize=5

TexFlags.AsyncLoad=1

TexFlags.ShowTexture=0

SimpleMesh.SWTransform=0

SimpleMesh.QuadTreeClip=1

SimpleMesh.InstancingHW=1

EffFlags.LightContextSprites=1

CloudsFlags.Detailed=1

TexFlags.CreateHDR=1

Decals=2

EffFlags.SWLight=0

TexFlags.CockpitOnePass=0

MegaTexture=0

TexFlags.Reflection=0

RenderTargetQual=3

MSAA=0

MeshStatics=1

MeshStaticsDetail=1

SimpleMesh.QTNoCompose=0

MeshFirstLod=0

MeshShowLod=0

SpawnHumans=1

TexFlags.FastTransparency=1

TexFlags.SSAO=0

TexFlags.VSync=1



[sound]

SoundUse=1

DebugSound=0

SoundEngine=1

Speakers=1

Placement=0

SoundFlags.reversestereo=0

RadioFlags.Enabled=1

RadioEngine=2

MusicVolume=14

ObjectVolume=7

MusState.takeoff=1

MusState.inflight=1

MusState.crash=1

MusFlags.play=1

MasterVolume=14

Attenuation=7

SoundMode=0

SamplingRate=0

NumChannels=2

SoundExt.occlusions=1

SoundFlags.hardware=1

SoundFlags.streams=1

SoundFlags.duplex=1

SoundExt.acoustics=1

SoundExt.volumefx=1

SoundFlags.voicemgr=1

SoundFlags.static=1

VoiceVolume=8

Channels=1

SoundFlags.bugscorrect=0

SoundExt.extrender=0

SoundSetupId=8

ActivationLevel=0.02

Preemphasis=0.8

RadioLatency=0.5

AGC=1

PTTMode=1

RadioFlags.PTTMode=0

RadioFlags.PlayClicks=1

ActLevel=9

MicLevel=10

SoundFlags.UseRadioChatter=0

SoundFlags.AutoActivation=0

SoundFlags.forceEAX1=0

speakers=1

vgMaster=15

vgVoice=15

vgMusic=10



[game]

mapPadX=0.65

mapPadY=0.08055556

mirror=0

mapPadDX=0.35

mapPadDY=0.6