escaner

This is the list of the ones I have met, minus what is already in the first post: * Engine Start function (RShift-Home) should move the throttle from STOP to IDLE to start the engine, but it will not start unless you actually move the throttle axis forward. * Engine will start even not pressing DEMarrage pushbutton next to the pumps. * CCIP/CCRP Snakeyes/Mk.82: when dropping bombs level or in a slight dive, bombs always land long. Computation is only OK with a moderate dive. * CCIP Gun (CAS). Sometimes the range circle bugs out and you are closer than it actually displays. I think it also happens in air-to-air. I think it can be fixed with Master & Gun SAFE then ARM, but not sure about this. * Ripple bomb release: CCIP/CCRP calculate the point of impact of the first released bomb instead of the middle point of the ripple. https://forums.eagle.ru/showthread.php?t=201663 * Sounds. Doppler effect (high pitch-low pitch cyclic sounds, like in a flyby) can be heard in external views even when the distance camera-aicraft does not change, which is incorrect. Engine sound is muted inside the cockpit when the aircraft flies faster than Mach 1, which is incorrect, as the sound is actually transmitted through the airframe and inside air of the aircraft, which is moving at Mach 0.0 relative to the pilot. * Keybindings. Many keybinding shortcuts not available. E.g. aicraft wingspan, etc. * "PRF Selector High -> Int -> Low" and "Low -> Int -> High" shortcuts not working. TBH I haven't checked this one in a while. * TOT/PAR Mode Toggle keybinding: At first press it works OK. For next switches, you need to press twice the keybinding. Using the mouse always works fine. * In some lighting conditions, it is very hard to tell whether the PCN buttons are illuminated or not: https://forums.eagle.ru/showthread.php?t=201520 * Position of multi-position switches not synchronized between HOTAS and simulator at the start of the flight even if "Synchronized cockpit controls with HOTAS controls at mission start" is activated in Options -> Misc. * Expended rocket canisters cannot be jettisoned because they disappear from the PCA. * Closure rate of air target in TWS mode with target at close range. At less than 1-2NM aprox, closure rate switches to negative figures when closing in. https://forums.eagle.ru/showthread.php?t=202514 * After selecting and jettisioning external tank (RP), the radar in RWS will not lock any target because the RP is still hiddenly selected. You need to select eg an air to air missile so it deselects the RP. https://forums.eagle.ru/showthread.php?t=203038 * Close combat radar modes with Master Safe do work but you cannot see the HUD symbology. PS: The one with the kneeboard was already fixed.

I opened mine yesterday by lifting the exterior case with small flat screwdrivers, inserting them next to the tabs that fix the button to the stick/throttle (see image). Good news in my switch is that the metallic plate was OK. It was stuck down, but I just warped it a bit and now it does its function correctly again. Now I need to solder it back. PS: I haven't found any info on the hats yet, anyone has disassembled them?

This picture is awesome, I will try to fix my LTB that failed yesterday. Anyone has a similar one for the 5-way and 4-way hats? This was the 5th switch with problems on my Warthog in 3 years... :(

That is why I said "in general". If you want to do a snapshot like that you cannot pull g and you need to stop maneuvering so the sight computes the round fall (but still not the lead), which is a very specific situation.

The snake (and also funnel and gyro sights in general) air-to-air gunsights are based in your own aircraft maneuvers to deliver a reliable firing solution. Therefore you need to match the target movements as stable as possible and get a tracking shot. It is useless for snapshots and out of plane shots in general. If you don't have the patience for this kind of sights, you can always use the cross as a fixed sight, which is where the guns are actually pointing and do the lead computing in your head as you would in most WW2 aircraft.

I did the campaign months ago, but I liked a lot the one where you were patrolling roads N of the little base (Suse?) and then the base got assaulted.

Thanks man, you are the best! :)

Not that there are soldiers shooting at them with Kalashnikovs or something, you know? ;)

Thanks a lot Helljumper, you are right. I dumped the external tank when I was sent to intercept as it was already empty.

Yesterday I was intercepting a medium sized transport (campaign mission), aspect hot in HFR, Mach 1.2 closure. I detected it at about 60-70 NM, but I never could lock it into TWS. When it was far, I had an overstriken PSIC message in the HUD, but not anymore at closer distances. I even tried to go medium PFR (also could not lock it) and BFR momentarily. When it disappeared from the radar (2-4 NM I'd say), as I had a tally, switched to a close combat mode and it locked instantly. Throughout the intercepion I didn't see a trace of ECM. How come I could not lock it? What is that crossed PSIC message (I was trying PID, not PIC)? While we are at it... is it possible to move back from PIC to PID without completely unlocking the target? Thanks

I have only played a bit with it, but from what I have found, you need to: 1. Set the desired altitude in the dials 2. Activate the AP in a climb or descent to reach that altitude 3. Press selected altitude hold. This will arm the mode (in yellow) 4. When the aircraft reaches the altitude, it selected altitude hold activates to intercept it and then reverts to altitude hold.

I just downloaded the one from your Google Drive and it gives me the same SHA256 hash that the one I have from 2.5U3, so yes, it was the latest version.

I have done this mission a few times and got a few glitches. Sometimes I tell COTON06 to attack troops near the south building while I go to the trucks but they engage both of them (noth and south buildings). Happened twice. In one of the runs, I saw the truck near the LZ and destroyed it before authorizing Ford 1-1 to land. When Ford 1-1 landed, enemy troops next to the destroyed truck killed it. The messages said that they were going to hold in another place, but Ford 1-1 was destroyed. Ford 1-2 killed the troops, but the mission got stuck there. See screenshot. In another try, I didn't kill the truck and sent Ford 1-1 to the LZ. Again they started to take hits, but I attacked the troops, helping Ford 1-2. And again Ford 1-1 said that they were going to hold somewhere but they just landed and stopped the engine. At the end of the mission they never started the engine again, never took off. In this case the mission completed correctly. See screenshot. Edit: forgot this one: Mission briefing says QNH is 1009 but it actually is 1013.

Thanks! :)

I cannot find the definition of ABL.

It was the same bug in 2.2, I have not tried it in 2.5 yet.

I checked it too and weird readings only happened in TWS at close range. Beyond 1-2 NM, they are OK, but less precise than in STT. In this last mode, it was always fine, even at very close range.

Baltic Dragon, I just tried the updated mission. Nice, I can see the tracers now, and also the MiG-25s, good job! :thumbup: There is still that 3 in E43 44.315 that I think should not be in the messages (see screenshot).

The problem is that the Mirage stick has less travel forward than backward, but our sticks have the same. Neutral stick is 1G, max deflection back is 9G and max deflection forward is -3G (figures from memory, limits could be wrong). So you have 1 - -3 = 4G travel forward and 9 - 1 = 8G travel backward => Pitch up has double the authority than pitch down. To solve this we would need to modify the response curve of our stick so it saturates at about 50% travel forward while keeping the backward range the same.

The closure rate is the number to the left of the range scale? If so, sometimes it gives me weird reads to the point that I was doubting what it actually is. I think it happens when closing in a bit fast to my locked target (more than 100KT closure, less than 1NM range): it then displays negative numbers and I was sistematically overshooting my leader in the campaign.

From memory, that could be the SERPAM switch, some kind of flight data recorder for debriefing. I don't think it is functional.

LOL, that is obviously a bug on ED's side. Thanks a lot for your dedication and feedback, man. I am enjoying the campaign so far. I think next mission will be #7. :)

I did this weekend. Don't forget the refueling switch to day or night.

Yes, deferred shading is awesome at dusk and dawn, but it breaks illumination at night. It happens with all aircraft and even with scenery lights and city lighting. Actually the Mirage is one of the least affected planes that I have. You can always deactivate deferred shading and go back to 2.0 lighting.

Same here, just did the mission a couple of times and have several problems. (BTW, all missions seem updated to the google repository versions in 2.5.0 update 2). 1. No tracers whatsoever. I went even to external views seeing the troops. Nobody shoots. Just saw an explosion and went to the airplane. That was the only clue viewable from the cockpit. 2. Coordinates in the text are wrong, they say: "N42 4.23 E43 44.315". The first one is missing a zero (not big deal) and the second one has that "3" that should not be there. I didn't really listen the audio. 3. It is also weird when everybody tallies the MiGs in a pitch dark night... 4. Following Colt, sometimes they fly slower than 170-180 KIAS, which is awfully slow for cruise in this aircraft. The first try I thought I had to follow Colt down for the show of force. So waited and waited. They said the helos arrived. Finally introduced the coordinates and made a BAD delta North 5.0 (is that 5 NM? 5km?) Well, whatever, did the low pass and nothing. Anyway the coordinates were a bit off with that "3", so perhaps that was the problem. The second try I saw the explosion, but as I already said, no tracers. Did a visual pass on the area, and the trigger worked.