Jump to content

dorianR666

Members
  • Posts

    1623
  • Joined

  • Last visited

Everything posted by dorianR666

  1. there is a PDF manual installed with the game, it describes it all in detail. open \Doc\DCS User Manual EN 2020.pdf for example the EPLRS command is explained on page 269
  2. logbook isnt reliable. never was as far as i remember. its not OB related or RO related, dont worry.
  3. good idea. could probably be very easy to implement as bindable to keyboard combination like anything else.
  4. hello bignewy i have found the exact cause of this bug. it happens when you enable "hide stick" in game settings, while not having enabled "solo flight" in l-39 special tab in mission editor OR enabling your own pilot body with rshift+p. you see, the glitching deformity is actually pilots or AI copilots right hand which doesnt know where it should be positioned when the stick is missing, so its just randomly flying stretched out in space.
  5. its a nightmare for singleplayer too. you instantly see every unit on the map, just by looking. simply put, gamebreaking - for more than half a year. https://forums.eagle.ru/forum/englis...55#post6389255 how is this bug not critical priority, ED? its not just minor graphical glitch, it makes night mission impossible.
  6. oh and one more thing in that one mission (dont remember number), where enemy su-27s arrive and fight friendly f-15s, consider disabling weapon jettisoning for player's su-25s. they just drop their stuff as soon as su-27s arrive making them useless for the rest of mission. shouldnt take more than 3 minutes to fix.
  7. hello nineline consider adding those triggers please. ive seen it happen twice yesterday. helis emergency land and it doesnt count as destroyed - what more, emergency landed helis are invincible and cannot be destroyed (another bug in dcs now). which makes this mission impossible to finish if just one heli lands. i have also had a heli leave the battlefield and go home, which also makes the mission impossible to finish. not sure why (rtb from low fuel after fuel loss? rtb because no weapons? mission abort due to threats?). perhaps add a trigger that handles leaving heli as if destroyed.
  8. you can do that without markpoints in a much straightforward manner: move tgp to target, switch TOO1 to TOO2, move tgp to target, press step - do this line 4 times, thus feeding in 8 different targets total, except the last "press step" which youll replace with undesignate. then when launching: launch 4 bombs, then for another 4 bombs set the station to TOO1 before each launch. ez
  9. as TLTeo said, sea modes are not implemented yet. best you can do is map mode with gain set to maximum (data subpage). which is i assume what you are doing already. that mission is a bit pain in the ass. dont forget to use markpoints to overfly mark ships when you check them so you dont get lost in which ships you have already visited and which not (like me). AG radar in BMS is completely arcadish and has nothing to do with real behaviour. every vehicle is a bright spot from 30 miles away yet there is no background clutter, so you can perfectly clearly see columns inside cities (nonsense). it even sees through terrain :-) realistic AG radar simulation will be painfully underperforming compared to BMS' magic AG radar, so dont expect future sea modes to match it.
  10. there is no way to fix your track. there is an ancient bug which causes some inputs to not be recorded in tracks, they are just skipped. i suppose in your track thats gear up. this bug was never fixed and appears randomly (and fairly rarely), so there is unfortunately no known way to avoid it.
  11. would be cool if there was some progress on this pictures attached are current OB as of october 2020, sending t72 group over bridge using combined arms
  12. i would like to add that this is a SERIOUS issue with Frontlines Georgia. the campaign often uses deploying infantry from helis for you to use - but you cant, they are all stuck inside each other and cant move or fire. just spawn them with more space in between each other when deployed from heli.
  13. heh its been 1 year 6 days since this post. i shall make this post again 1 year from now.
  14. saved, thx though it says EMCOM instead of EMCON :-) consider for future update
  15. yes, it would make sense, therefore hornet doesnt do it :-)
  16. at first i thought this thread is user error, but ive seen it multiple times today in multiplayer. jsow-a, efuz on, too (target designated from tgp) and aligned to maximum. consistently missing the target.
  17. update: still present in the game, got it again today on one smaller syria server. however when i used the radio menu as if case 3 was called by the ship, the communication then worked fine according to case 3. i cant check if this is reliable though.
  18. yeah it was me who said that. "32bit (...) unlike 24bit, its a power of two" means that 32 is a power of two and 24 is not. i didnt say 32 isnt a power of two. i agree with what you wrote above this though.
  19. looks the same as this https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-f-a-18c-hornet/bugs-aa/289644-reported-hsi-waypoint-symbol-displayed-on-wrong-position
  20. I found this while playing the community-made campaign Cage the bear for Hornet, mission called Interception. Mission file attached. Every time i started the mission, sun was missing. Track attached. I played with it a bit and found out sun appears if cloud precipitation is set to 8 or less. With 9 or 10 sun doesnt appear. Second image shows the missing sun (precipitation 9, unmodified mission). First image shows how it is supposed to be (precipitation 8 ) missing_sun.trk FA-18C - Caucasus - CTB 5 - INTERCEPTION.miz
  21. this broke in like early 2018, ED never bothered to fix it. hopefully the could now.
  22. yes, it doesnt work yet. perhaps on 4th it will.
  23. nice but the first not implemented is actually implemented i think
×
×
  • Create New...