-Painter-

macedk - what is that link good for regarding the question?

Hey Mr. Unknown, obviously you do not get the point: Your example is the best example to show how easy it is to mix it up (maybe even worse in VR) - you need to know and you need to remember in the current situation, if the diamond/box is aligned to the true horizon or if it is aligned to the acft. (obviously 2nd is the case). When you look at your 2nd picture on the first look at it that thing appears as a diamond, on the 2nd look it could well be that it is a box if it would be aligned to the true-horizon-line on the HUD - and that is what can potentionally confuse the pilot. Prob. that is the reason they introduced the diamond-upside-corner-marker in reallife. Edit: the reason for the confusion is most likely because the other lines in the HUD are true-horizon-lines and at least me as a pilot tend to combine that the box must be locked to that lines.

cant find it (static obj floodlight) - where?

+1

The IFF foe-indicator in the HUD (diamond) should have the top-corner marked. Otherwise you mix up diamond ./. box very easy in a 45°-bank, since the diamond/box stays aligned to the true horizont - a diamond becomes visually a box when you bank. Reallife-video where you can see that diamond-top-corner-marker:

I didn't test the numbers yet, but: My biggest concern is, that the Hornet compared to the Mirage is first of all not able to gain any speed back. It feels like flying a 737 and not a fighter. And that with a SIGNIFICANT better trust/weight-ratio (0.96 loaded, 1.13 loaded with 50% fuel) than the Mirage (0.7 laoded weight) has. Hornet gross-weight: 36,970 lb dry thrust: 2x 11,000 lbf (49 kN)= 22,000 lbf (98 kN) -> thrust:weight-ratio: 0,595 with AB: 2x 17,750 lbf (79 kN)= 35.500 lbf (158 kN) -> thrust:weight-ratio: 0,960 Mirage 2000 gross-weight: 30,420 lb thrust dry: 14,500 lbf (64.3 kN) -> thrust:weight-ratio: 0,476 with AB: 21,400 lbf (95.1 kN) -> thrust:weight-ratio: 0,703 So in any situation the Hornet SHOULD feel MUCH more powerful, especially with AB it should feel like 1/3 more powerful than the Mirage. But the opposite is the case. We could test that felt impression in a special setup. Like clean aircraft, 100% fuel: 1. climb to 10.000, accelerate from 150 kts to 450 kts and see what time they need. 2. start at 1000 ft. 300 kts., pull 90 degrees nose up and see in what time you are at 25.000 ft. and with what speed you hit that altitude. 3. 5000 ft. 120 kts. level flight, full AB accelerate level until 400 kts. It kind of remembers me at a time in the past when the Mirage felt like a brick at low speeds before the flight-model changed. Nowadays the Mirage feels like a fighter actually, but that wasn't the case from the beginning. In the past you hadn't been able to recover from a very-low-speed-regime in the Mirage, but you fall out of the sky in full burner basically. Today that isn't the case anymore in the Mirage. But the Hornet feels a bit like that - not that bad as the Mirage was before, but close to it.

+1 I experienced several situations in which I wasn't or was barely able to recover from a low-speed, high-AoA situation due to an extreme slow aircraft response on full MIL or even MAX - it felt like there is no response at all and the aircraft just stays in a descent rate. Everything in such situation was just wrong: maintaining pitch or increasing pitch. There was just a total lag of the power I expected or an extreme amount of drag. Compared to the M2k one of them is wrong, since the thrust-weight-ratio of the Hornet is better. From my feeling I would say the Hornets engines do not deliver what the pilot would expect.

+1 PLEASE like that:

The thing is: The change IS in the mission file, but still it says FM in the radio-message-trigger instead of AM. Edit: And when I save the (changed) mission from within the ME again, the change is gone in the mission file.

...up to the 3rd plane the client hornets spawn fine on different spots (cold from ramp). Up from the 4th plane it is bugged - no. 4 spawns on top of no. 3. So only the first 3 planes spawn bug-free.

We had another flight yesterday. We just can't figure out what the "into-water-cat-shots" causing. Flight of 6 acft. yesterday, more or less same setup (spawn cold and light weight, rearm refuel, thereafter attached to the cat) - 3 splashed into the water due to extreme low endspeed of the ship, 3 launched fine with something like +50 kts compared to the others. We tried to cross-check if the splahed guys did something different than the others - but it seems like not. It seems the into-water-shots are kind of random but of course more obvious when your acft. is heavy. What could cause a too low endspeed? We kind of stuck in trying to find a 100% reliable way to reproduce it. But still it is annoying when you plan a mission and half of your squad ends up in the water after the launch :D Edit: video of the water splash shot here:

I wanna edit the file "mission" from within a miz file, but it does not take the changes. My procedure: - copying the "mission"-file from the zip to a normal directory - renaming it into mission.lua - opening it in notepad++ - doing my changes (search and exchange one false flag into true which should change the radio transmit freq. for my LSO-calls from FM to AM - saving the file - deleting the old from the zip - copying the new into the zip - opening it in the mission editor - no change - rechecking it in the miz - changes still there - resaving the mission as new miz -> rechecking the mission file -> changes gone What do I wrong?

@Jeast try it while attached to the carrier-catapult

To add - when you look at Reaper21-Raptor - sidenumber 321 - in the trk-file: he said, he did rearm BEFORE attaching to the cat, but still got shot into the water. If it was only the cat-attached guys who run into problems the "feature, not a bug" would make a lot of sense and indeed it seems to be the main issue. But still - Raptors launch-fail is very suspicious. Tacview file (broken from some later point, but the cat-shot-fails are in): https://1drv.ms/u/s!AhBj_n1DxBsaiS6wACnkPuDRJuDK

Thanks a lot!

The issue is: You have to enter degrees, minutes, seconds 00°00'00" but the HSI-Data shows degrees, decimal-minutes 00°00.00' (Or was it the other way around?) I am pretty sure that is a bug.

Use the night/day switch above the upper-left corner of your centre MFD. Not sure if that is correct, but it does switch the non-static objects brightness in your HSI (e.g. course-line). The static objects are always day-bright yet (unfortunatly).

Just because of the example in the first post: that offset-fixation does not work in MP - is that fixed anytime soon maybe?

Amazing! Does ED implement them so that everybody has them already and does not need to install them to see them (MP missions)?

@Sniper: Maybe you did not read the post: My hardware throttle has a detend already.

Same issue in Oculus VR. When I lean way forward close to the screens the text is totally crisp and sharp, but in the normal seat position it is very unsharp/soft and barely readable. Would be great it would stay as sharp as when I lean forward close to it.

Exactly. Do not forget - that numbers are for a 0.75-1NM groove! If you are longer in the groove=more behind the ship, you are most likely below glidepath and can't see the ball - not due to VR but because you are too long in the groove/ far below glidepath. I am using the Oculus and can see the ball from when I am at the 90-45 all the way until touchdown when it is a perfect approach. So first of all: Make sure your approach-technique is correct. Most pilots I see start the final turn much too late. If the ship is doing 20 kts. you can start your turn abeam of the LSO-platform or abeam the round-down.

1.) Does it break IntegrityCheck? 2.) Could you please post the code for a speedbreak-toggle? 1st one-click-press=SpeedBreak Extend to 100% 2nd one-click-press=SpeedBreak Retract to 0 % (maybe with just to stop motion of the speedbreak when button press during the motion)

Any chance to get Rampagers CAG (300) and DCAG (301) paintings? Link1 CAG Link 2 CAG Link1 DCAG Link 2 DCAG

...I can. And when I have problems I use the VR-zoom-in. PS: Normally I am able to see the ball at the 45 already, given a good approach.