TOViper

A more suitable "workaround" for the hot/cold spawn topic is to have the agressor aircraft set to immortal and ask the agressor pilot report impacts of missiles and let the agressor pilot just report "lockon" or "fox [x]" if he is in a shooting position.
This requires a buddy pilot though.

Very good, you managed it!
According to the trigger conditions that I can read in the mission editor, there is a provision for some margin for all three digits (arguments 676, 675, 674):
null

Hey ex81, you might want to find some infos here ...

Hey Smokin1469! Thanks for your report! The info has already been forwarded and the bug is now repaired internally.
For the moment, until the next DCS update arrives, you may open the lesson in the mission editor, add a few AIM-9Ls, then save the lesson, and then fly it.

Hm, maybe an issue with the canopy not opening correctly or the throttles not set to IDLE.
These are the only two things that are checked by the lesson logics at that stage.

Hey Joker62! After reading your latest post, I am pretty sure your computer has a hardware issue. Maybe overheat or undervoltage caused by high system load.

Ok, then most probably your slats/flaps switch was not set to position "OUT & DOWN", but only to "OUT".
This makes the slats go "OUT" and the flaps "DOWN", and so most people think all is good if they only check the indications, but forget about the switch.
But: The slats/flaps switch MUST be set to position "OUT & DOWN" in order to continue with the lesson.
Some users use wrong key bindings or just move the switch one step down. Carefully check your bindings here to make sure the aircraft does what you expect it to do.
Note: on ground the slats/flaps switch position "OUT" makes the slats to go "OUT" and additionally the flaps go "DOWN"; in flight they behave a little different.
Find more on the slats/flaps lever here: https://f4.manuals.heatblur.se/cockpit/pilot/left_console/wall.html#slatsflaps-control-panel
Edit: it might be the case that you accidentially set something else to a wrong position (despite this is checked duringe the procedure); in this case: carefully go through all BOLD items once more. This is why a CHECKLIST is used before moving on own power; it is important that nothing is left open and none of the systems is in an unsafe condition.
Hope you find it phinally working then ... if not, please come back here once more, I will monitor this thread carefully for the next few days.
Kind regards,
TOViper
🙂

@BIGNEWY I found the issue, but it very looks like it is caused by how DCS works (or in that case not correctly works) with fxo's:

.) I did empty the fxo folder and metashaders2 before doing anything
.) Then I start DCS
.) "Display resolution" in the SYSTEM settings was set to 256
.) After reaching the first mission, the fxo's were all created
.) It seems the WPN page is then rendered at that certain resolution (in my case at the "lowest - bad setting" of 256 for a very long time since I fly the F-16, because I struggle with fps since ever especially when I fly with TGP and MAV's and using them in parallel)
.) I then selected 1024 in the SYSTEM settings, but: The fxo's seem not to be updated anymore; I had to delete fxo's for each change of the SYSTEM settings.

Ah, and by the way: I had to use the current OB 2.8.0.33006, since I update a few days ago.
Side story: The problem with the crosshair is gone, I now managed to see the crosshair with MSAA set to OFF.

Hope this helps someone out there, but at least I hope you guys at ED will correct this problem somehow (which drove me crazy).

Thanks,
TOViper