E-Rock

You may be right. I am not versed with the other files you mentioned. I went as far as starting the first mission, checking the AI flights took off as scheduled and that was it. I haven't gone as far as playing through a few missions to make sure all the mechanics were still working. I also notice in the Hornet over PG campaign which is what I am playing at the moment, the CVN-72 Lincoln home carrier is actually using the CVN-74 Stennis model but called CVN-72 Lincoln in the campaign. So what I did was replaced the old CVN-74 Stennis model with the super carrier CVN-72 Lincoln for "CVN-72 Lincoln" in the base mission. Perhaps the CVN Stennis references in the files you mentioned will still work since it is just a name, irrespective if it's using the old Stennis model or any of the super carrier models. I guess we should wait for the DCE experts to chime in.

I did just that (switched the standard carrier to super carrier in the base mission) and it seems to be working okay. A handy tip.....Unlink all the static aircrafts before switching the carrier and relink them again after so they remain in the same location on the deck and not all bunch up in the middle. Also what is interesting is that spawning on the deck is now okay with the static aircrafts in the latest open beta.

The command prompt sometimes pop up automatically and sometimes it doesn't. As long as you remember to generate the next mission before continuing the campaign you should be okay. Regarding the HARM behaviour there is a script in the campaign which switches off the SAM radar when a HARM is detected to simulate what the operator does in real life. So I think it is working as intended. During a SEAD mission you only need to suppress the SA threat by forcing it to shut off its radar. It is the strike group's job to take them out (safely) after they have been suppressed.

When you quit the mission the game should take you to the debrief page (inside DCS) where you can select to close, fly again or end the mission. Here you must choose end the mission to save your progress within the campaign. After generating the next mission using the command prompt you should be able fly it by continuing the campaign in the campaign menu. It sounds like your game locked up after quitting the mission so it didn't save your progress.

I found deleting the first static closest to the starting position (can't remember off hand what it was) was sufficient to get going with the mission.

A few other people including myself have reported the problem of logbook not recording kills. https://forums.eagle.ru/showthread.php?t=245186 If you try the same mission and end the mission before landing it will probably work.

What is odd is that I never had this problem until now in the 8 years of using DCS. I have also tried repairing the installation and rebuilding the DCS save game folder. The only thing I haven't tried yet is a clean reinstall but I am not confident it will fix the problem.

After some more testing tonight, my problem is also that the kills are only recorded if I exit the mission before landing. If I fly the same mission and land then exit only the flight time is recorded. Strange.

I use Voiceattack to trigger the key press combinations needed to drive the Jester wheel. That way I don't have to screw around with the wheel during the critical moments. The process is almost instant so the wheel pops up only for a split second then disappears.

The speed brake trick someone posted earlier to set full MIL power at the detent works quite well. I bumped up the throttle curves bit by bit and tried the detent position until the brake retracted.

Judging from the mini-update, I reckon the team decided to delay the release to further enhance the TPOD with more functionality for its debut.....or they discovered a problem with it at the last minute and it needs some reworking.

I started having this problem just recently, logbook records flight time and landings but not any of the kills. I fly exclusively SP using home brew missions and I am running the latest OB. Both the Hornet and Tomcat module have the same problem. I have also tried creating a new logbook but to no avail. I have no mods installed except for Tacview.

The actual improvement is probably more like an absolute value instead of a fixed percentage. So the results are mixed when presented as a percentage depending on the individual's baseline performance.

I am very happy with the prescription inserts I have from VR Optician for the Oculus Rift. I am slightly short sighted at -1.25 SPH and the Oculus focal length is more than 1m so the image is blurry without the inserts. But I don't need any inserts for the Vive Pro fortunately because its focal length is much shorter at around 75cm and I can see clearly at that distance.

With so much anticipation for the VR optimisation and the miracle 50% gain, I can only see further backlash when it comes out and people don't get what they expect on their 10 year old PCs.