dorianR666

there isnt gonna much be much noise if the radar is scanning against sky. there will be lots of noise if the radar is scanning against terrain. this difference is not simulated in dcs f-1 at all. you always get the same amount of noise no matter whats happening.

i confirm this bug also.

i can confirm that rolling the aircraft during scanning messes up all EXP modes. what amazes me the most is that AG radar still doesnt have gimbal limits modeled. you can fly straight up and your radar screen will still be able to map the ground below you, as if seeing 170 degrees below the nose.

hi, thanks for asking. no, i havent seen it in any recent versions of DCS beta. seems to be resolved for good.

the point is that the radar wont be scanning anything afterwards, it gets blind. not even the clutter effect. you have to return to the "RWS", then TL, then BZ to make BZ work again. i see.

boresight modes still broken in yesterdays OB. also id like to add that even when they happen to work and lock something, they break again when the target leaves gimbal limits. and you have to do the whole dance with the switch again.

the only mistake in ED's removal of features was removing the laughing react emoji on this forum.

doesnt matter. heatseekers in dcs see only 3 states: engine off, engine running, afterburner running. there is no difference between being in idle and being in milpower.

this is still not fixed? huh

you never ever need to "fully undesignate" a trackfile. its a pointless operation, thats why there is no hotas button for it. edit: just realized this is 2 years old. oops. no

i landed on 21 left because i was too lazy to turn around. and it worked fine, i got the ground voicelines

hi when landing, nellis is unable to make up its mind on which runway im supposed to land. player asks for 21 left, tower clears to 21 left. then suddenly tower clears to 03 left and player accepts 03 left. no trackfile for obvious reasons.

lol, 2 years ago

hi if you commit through F10 to destroy a target (instead of your wingman) and you miss and run out of ammo, the mission is bricked. you no longer have any way to destroy your target - but at the same time, you cant make your wingman attack even though he still has jdams. this happened to me during the APC near the boat tasking. i missed my last GBU. there is still an option in F10 to make dutch attack the APC but it does nothing. no voiceline, no AI reaction and it doesnt disappear from the menu either.

hi if during one of the run-ins you forget to press spacebar to confirm youre within the attack cone, and attack and destroy the target, the mission will continue (as expected). however every time you press spacebar for the rest of the mission, youll hear "abort abort abort", even though that target was destroyed a long time ago. its not game breaking but it is very annoying, because it cancels out all the voicelines for the rest of the mission. expected behaviour: no abort and reattack voicelines for a target thats already dead.

no matter the drift, the line shouldnt be horizontal like that, so this is a bug.

got this with raven one mission #8. the "end mission" button just does nothing log shows the following: 2023-02-03 21:42:10.808 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_logbook.lua"]:1128: attempt to index local 'unitTarget' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_logbook.lua"]:1128: in function 'updateUserStatistics' [string "./MissionEditor/modules/me_debriefing.lua"]:361: in function 'updateStatistic' [string "./MissionEditor/modules/me_debriefing.lua"]:385: in function 'endMission' [string "./MissionEditor/modules/me_debriefing.lua"]:351: in function 'onChange' [string "./dxgui/bind/Button.lua"]:22: in function 'callback' [string "./dxgui/bind/Widget.lua"]:368: in function <[string "./dxgui/bind/Widget.lua"]:363> debriefing lua table attached raven8_debriefing_bug.log

hi BD this part being said by player to olive differs significantly from what is in the voice over.

yes, its bugged. the whole INS drift thing in dcs viper and hornet is WIP and full of issues. pretty sure the coordinates on tgp and in markpoint should be the same, because tgp calculates the coordinates from ins' ownship position and markpoint just saves the result from tgp.

the whole launch warning mechanic is messed up throughout dcs. i dont think it will ever be corrected. indeed.

this will get a bit better when it receives the PRF audio functions. youll hear when the lock was broken.

they probably mean link16-sadl gateway so we can finally see enemy aircraft on tad through awacs

ED did not (or not very well) port the campaigns to dcs 2.5's new caucasus in 2018. its the same with FC3 and A10C default campaigns. the new caucasus changed layout of forests and roads somewhat, making some missions impossible to be completed. search for bugfixed campaigns by maddog-ic, he did what ED should have. that guy is a gift to dcs community. another problem is the broken "scenery remove" trigger action, which is used to remove forests. it doesnt work sometimes. it seems to be most stable when you play a mission as the first mission after dcs start (so restart after each). https://forum.dcs.world/topic/216731-scenery-remove-objects-zone-does-not-remove-trees/?do=findComment&comment=4592120

dear eagle dynamics, this bug was reported over two years ago and is nearly five years old. today the only sensor you can utilize in ka-50 is still broken, and what more, it is still broken in your new black shark 3: @BIGNEWY is it known to the BS3 team?

bump