Level-D 767 SP3 released!

[VulcanB2]

Hi,

This is the last SP for the 767. You can get it here:

http://www.leveldsim.com/sevensix_downloads.asp

Note for users of SP2.1 with VNAV issues: The VNAV is *not* fixed in SP3, and will *not* be fixed now, even though before the release of SP3 they acknowledged the VNAV mode was still broken. Apparently if you want fixed VNAV, you need to get the 757. They are not saying though whether they will ever return to the 767 as it is a "seperate product". Not very helpful if, like me, you find it randomly nose-dives in the cruise. :(

Best regards,
Robin.

[chris]

Ooh, that doesn't sound too good. :eek:

I'm still somewhat tempted to try Level D 767.. Or maybe the PMDG 747-400. I'm terribly interested to see how both supposedly realistic Project Opensky and Level D 767's compare for flight dynamics.

Obviously if one is wildly different than the other, only one can be realistic - and therefore somebody is telling little porkies, to use the old saying. ;)

[VulcanB2]

........and I think I know who. ;)

The Level-D doesn't simulate "Drag Required", VNAV doesn't decelerate to descent speed before it actually descends - it tries to do both at the same time (something the 767 is particularly bad at as it is so clean). ALT HOLD has its moments (I had it nearly crash on me again last night) where it thinks it is either in Pitch Hold or VS Hold mode - I haven't been able to determine which yet.

It was in VNAV, and should have descended to an FMS altitude constraint of 8000ft from 10000ft. Things started to go wrong when it didn't draw the ToD point...... VNAV then disconnected itself (for some reason), no FMC messages ("Reset MCP Alt" etc) and the MCP was corerctly set. After VNAV dropped out, ALT HOLD and SPD HOLD activated themselves, where it proceeded to follow the LNAV OK, but started descending at a suspect 1,500 FPM. It seemed obvilious to this, and activation of VANV yeilded no results (it kept on dropping out). I let it go down to 500ft RA to see when (if) it wolud get itself together, before kicking everything out and taking control. :( This was just a test flight.

I had been monitoring VNAV knowing this has been broken from day 1 and noticed that even in the cruise where it had 20 miles to fly at the assigned cruise altitude, that the FMC already thought itself in the DESCENT! I'm trying to find out under which circumstances it drops into descent mode. It was stuck in that mode until I reset everything (on the ground).

Based on the above alone, the PMDG 744 is definately the more realistic. ;) It is also safer!

In the screenshot below, I know the MCP is set at zero feet, however, ALT HOLD should be trying to capture the altitude it was at when it weas armed, not anything else! ;) If it is trying to capture the MCP alt, this is still totally wrong. You'll also note that it is failing to hold the target speed, which was another interesting thing with VNAV - it didn't quite know where it wanted to be. Looking at how it reacted to the increase in the speed, I think it is in VS Hold mode as this remained fixed despite the acceleration (it had already descended 5000ft like this).

If I find a work-around, I'll be sure to post it here.

Level-D 767 Alt Hold Prob:

http://www.antarctic-networks.co.uk:47392/images/vnavrunaway.jpg

Best regards,
Robin.

[chris]

Interesting bugs. VNAV is a particularly important system indeed.