dorianR666

hello, if you equip Supers and then you jettison them, the pylons they are attached to themselves disappear (track 1). it even happens with empty pylons, if Supers were equiped and fired (track 2). it appears to be a problem with Supers or their pylon adapters rather than their stations, because if you equip mk82s on the same stations and jettison them, pylons stay. it happens with both emergency jettison and selective jettison. mirage_jet_bug1.trk mirage_jet_bug2.trk

hello, manual says : Distance and angle measure is based on the radar. Therefore, it needs to be operating throughout the procedure. Should the radar be unavailable, the computer bases its computation on radio-altimeter height. This backup method is less accurate, and assumes that the terrain area is flat. If it is not the case, correct computation will be impossible. This doesnt work. You can deselect TAS and select RS on PCA, so the user interface is there. However once you try to designate the impact point for CCRP... nothing happens! No wings appear near the diamond, as if you didnt press the button. There is no release happening, no horizontal line. The system still waits for designation. One thing I noticed is that the range in kilometers on right side of the HUD is complete nonsense when using radar altimeter for ranging. For example, distance which radar ranges as 5.0km is ranged as 0.7km by radar altimeter. On flat terrain, the two values should be equal. Track attached. Notice how the distance on HUD changes as I dive below horizon. It starts way too low, then increases, then decreases and ends up absurdly low. It even shows distance of 0.0km at one point during the dive. mirage_ccrp_bug.trk

hello, according to manual, if TOT salvo mode is selected, both Supers should be launched 2 seconds apart if pilot holds the trigger the entire time. this doesnt happen, only one missile is launched no matter what. track attached mirage_tot_bug.trk

hello, this one is quite annoying. the knob rotates around, with no ends. so you cant tell if you have selected minimum value or maximum value. mirage_radalt_bug.trk

hello, this one is perplexing. the knob has labels on its opposite ends - nuit, meaning night, and jour, meaning day. yet, setting this knob to "night" position makes the lights have maximum brightness and "day" position the minimum brightness. this is the opposite of literally all other planes, so this is highly suspect. on top of it not making any practical sense... the name of the knob says "rheostat". perhaps setting this value to maximum, as graphically and directionally indicated on night position, should decrease the brightness, not increase. another possibility is that the labels nuit and jour are simply swapped in the texture. track attached. PS: there is a typo in the label that appears when you hover cursor over the knob, it says "casution" instead of caution. mirage_nuit_bug.trk

hello air started M2000 is spawned with "Radar IFF power switch" set to OFF, but it behaves as if it was turned on. if you move the switch out of OFF position and back to OFF, IFF stops working. expected behaviour is that air started plane shouldnt have this switch in OFF position. or if it does spawn with OFF position, then IFF should truly be OFF. current behaviour is definitely incorrect. also, the third position of this knob doesnt have any label next to it (OFF - SECT - black space). is this correct? mirage_iff_bug.trk

hello, the orange light with "IR" label right of the HUD is supposed to blink when 6 or less flares remain, according to manual. however currently it blinks only once 2 flares remain, which is a completely pointless notification to pilot, as that means only one more release is possible. track attached for brevity, the mirage is loaded with only 16 flares. program 4 is selected, which releases a pair of flares (this is possibly another bug, as manual states it should release one flare). notice the IR light will only start blinking before the last release, after which it will be lit up permanently (no flares remain). mirage_ir_bug.trk i havent checked chaff, as the minimum load is 112, but it might be worth checking if it doesnt have similar bug once you are at it.

i too needed to bind switching mouse view on and off with mouse button, and its not allowed in m2000. works fine with hornet.

thats accumulative keyboard pitch. its not part of the flight control itself, merely how the game translates keyboard input into cockpit stick input. thats weird. i play on keyboard too and modules WITHOUT this function are entirely uncontrollable on keyboard. this is a massive improvement. its also the same for vast majority of dcs modules. without this function, you cant dogfight or land or do anything really beside flying on straight line. you can always display the input window with rctrl+enter to see where the stick currently is, and act accordingly.

yep, i confirm this. after you do selective jettison with 4x magic, 2x magics are jettisoned (shouldnt be) and no magics can be fired for the remainder of the mission. track attached its not visible in the track obviously, but im trying to fire at the end and it doesnt work. magic_jettison.trk

no, you mark the target with the diamond. then you fly over the designated target, watching the "wings" around the diamond which tell you whether to correct left or right. hold the trigger during horizontal line passing through the diamond, bombs will release and hit the designated target. you dont need to hold the diamond on the target.

To express it in pseudocode Current incorrect behaviour: ins_coordinates := real_plane_coordinates Expected behaviour: ins_coordinates := entered_coordinates_of(selected_waypoint) Or if RAZBAM implemented the INS drift as separate variable, instead of continuously modifying INS coordinates Current incorrect behaviour: ins_drift := 0 Expected behaviour: ins_drift := entered_coordinates_of(selected_waypoint) - real_plane_coordinates

Just wanted to report that this ^^^ is still true 4 years later, as of current OB. Having to do correct INS fixes is half the personality of strike missions in these pre-GPS aircraft (Viggen etc.). Disappointing that this doesnt work...

still present in latest OB. the INS bombing training mission cannot be followed because of this bug.

Picture speaks for itself. Cant attach track, because its 11MB (yes, even just spawning and exiting). Its the first mission in M-2000C caucasus campaign.

clients see/hear the message only if the transmitmessage action happened after they joined. this problem exists for several other functions as well. ED never implemented the netcode for it. its been reported for like a decade now. what you can do is to periodically execute the transmitmessage action. make it go for a minute, after a minute make it got for another minute, and so on. therefore clients will not see the beacon for maximum of one minute after joining, which is acceptable.

net.load_mission IIRC must be called from server lua context, not mission scripting context. but those two contexts can interact so its fine.

basically: stay away from TWS, or your RWS will be unusable for the rest of the mission

this problem is still present in latest OB, but the solution Thallios posted no longer works for me. therefore i cant use TWS AUTO, because then radar elevation doesnt work in RWS until respawn.

confirmed

thats not the code. this says nothing about the problem. post the code that touches the airbase field. do you want to be helped or not? also, once an error pops out, the rest of the script will not be executed anymore.

nobody can help you if you dont post the piece of code that throws the error

indeed. somebody found this out on the forum about half a year ago, thanks to that guy and his info i was able to play comfortably without bricking my radar half the time ever since. you simply mustnt switch to guns while already having locked a target from rws/tws.

close up