dorianR666

looks like the same thing i reported recently as far as i know, i wasnt giving any attack commands, but i could be mistaken.

yeah i run repair after every bigger update, for that reason, and delete the shader folders. my apologies if my previous post sounded rude, that wasnt my intention. thats another valuable piece of the puzzle. so far everyone affected was using a GPU with GCN 4 architecture, but Vega 64 is GCN 5.

Most interesting post, thanks. Unfortunate about the bay if true.

hi i am not amd drivers version 21.3.1, should be the latest i have also tried setting all those driver options to either "use application's settings" or disabled. it made no difference.

LMAO i literally only asked a question why it cant carry bombs in the bay, devoid of any emotions, because i genuinely didnt know and the post i replied to said "loads of" (which i assume means more than 2, im not native english speaker tho). amazing "adult", to use your expression, response. if you cant reply without personal invectives (appears to be a common theme after clicking your profile), then simply dont reply to me in the future. i would truly appreaciate it, thank you DD_Fenrir.

i confirm this bug, automatic lasing cuts too soon.

of course it is unlikely the game would damage itself in the same exact way for all 3 of us with the same GPU family...

yes beside being off detailed part of the terrain as Bunny Clark says, there is a bug that sometimes makes a part or all of hornet's map be replaced with black. usually the map returns back after about 10 seconds for me. rarely, it flickers on and off for a second. i dont know what triggers it but it happens uncommonly and fixes itself after some time.

some new info when im parked in hornet in novorossiysk, it happens. when i take off from hornet in novorossiysk, it stops happening. when im parked in hornet in batusmi, it doesnt happen. when im parked in l-39 in novorossiysk, it doesnt happen. when im flying any aircraft at any place, it sporadically very rarely happens for a fraction of second. when im parked in hornet in novorossiysk and i switch to free camera but dont move (= it stays in cockpit head position), it happens. as soon as i move the camera, it stops happening (same way as when i take off). conclusion: the bug occurs when camera is at particular Y coordinate or coordinates.

i can make it carry only 2 bombs at most. thats not much, spitfire can carry more. why cant the bay carry anything?

no, its been fixed!

youre right, the trigger action is gone

+1 german side doesnt have any serious bomber right now, its very limiting for missions.

i have no idea what caused this but all UI elements containing icons and so disappeared. it happened in the middle of a mission while i was looking at F10 map. restarting the game fixed it. i dont know how to replicate it.

not bug, performance tradeoff flat shadows means horizontal grey transparent texture at the objects base, thats it. and the terrain thing is as old as dcs. for some reason, dcs just cannot correctly compute when shadow of a particular object is still in players field of view, so shadows of anything keep popping in and out randomly.

did clouds even have any effect on AI in the past? ive never noticed it.

so i take it back, it doesnt happen only on ground in novorossiysk i was now flying spit in normandy and i just saw it around me for a couple of seconds. this time intermitent, as the guys above me say.

is this still a thing? i just had my sights disappear. its possible i did something wrong, i just bought the module and this was second flight. but as far as i know, i didnt press anything its reproducible from this x.trk

dcs.log 2021-04-14 21:36:35.944 WARNING GRAPHICSCORE: already registered Renderer callback 2021-04-14 21:36:35.954 INFO VISUALIZER: StartSimulation 2021-04-14 21:36:36.283 ERROR DX11BACKEND: semantic 'POSITION0' is not declared in shader 'enlight/clouds.fx' 2021-04-14 21:36:36.283 ERROR DX11BACKEND: semantic 'NORMAL0' is not declared in shader 'enlight/clouds.fx' 2021-04-14 21:36:36.283 ERROR DX11BACKEND: semantic 'TEXCOORD0' is not declared in shader 'enlight/clouds.fx' 2021-04-14 21:36:36.283 ERROR DX11BACKEND: semantic 'TEXCOORD1' is not declared in shader 'enlight/clouds.fx' 2021-04-14 21:36:36.283 ERROR DX11BACKEND: semantic 'TEXCOORD2' is not declared in shader 'enlight/clouds.fx' 2021-04-14 21:36:36.283 ERROR DX11BACKEND: semantic 'TEXCOORD3' is not declared in shader 'enlight/clouds.fx' 2021-04-14 21:36:36.522 ERROR_ONCE DX11BACKEND: render target 'cloudShadows' not found 2021-04-14 21:36:36.522 ERROR_ONCE DX11BACKEND: render target 'CascadeShadowMap' not found 2021-04-14 21:36:36.522 ERROR_ONCE DX11BACKEND: render target 'mainDepthBuffer_copy' not found 2021-04-14 21:36:36.522 ERROR_ONCE DX11BACKEND: render target 'DummyShadowMap' not found might be related

only SRS, hornet countermeasure programming and display export renaming. i tried it without them right now, its exactly the same. however now testing a bit more, i found out that its not happening with a-10c2 and l-39. it is happening with viper and hornet. it may be related to whats being rendered in the cockpit, which could also explain why the bug isnt visible with free camera.

interesting might be hw related. im using amd rx 580.

true but thats still a tiny problem. you can simply iterate over all groups belonging to a country and apply the commands. 20 lines of code.

more testing shows its happens regardless of preset selected or time of day. but it seems to happen only in novorossiysk. not in batumi for example. i also didnt see it in syria. and as soon as i lift of from runway, it disappears.

hi this is what i see when viewed from cockpit, but not when in free camera cloud_bug.trk track requires only f-16 module, no lua scripting is involved.

lucky you