trystanv

Has it occurred to you that OPUS might be causing your issues? I've heard and seen several people having issues with it causing unrealistic wind speads, or erroneous outside temperatures both of which seem to be a possible cause of your reported issues. Just saying.

It fesible, I managed to get a -700 into Lugano (LSZA) and the glide slope was like -6.6 and a runway which was just a little over 4000 feet. Made for a very interesting approach

I would be nice to have some input from the developpement team on this though, maybe it could bring a better understanding as to how the TOD is calculated so people who like me that use a high CI don't nose dive on every descent.

I know all that and apply it when required but a plane still shouldn't nose dive at -3000 and -6000 FPM in a descent, if that were real I'd have passengers flying through the cabin

The thing with using a lower CI might work for flights in Europe because the distances are a lot shorter, but mind you in North America it is not uncommon for flight to Be cross country so cruising at M.75 cause of the low CI and on top of that battling +80 kts headwinds at cruise going less than 400 GS is a little annoying, with a Higher CI you might be burning a bit more fuel but at least you dont take 8 hours to fly a flight that usually lasts 6. Bottomline the TOD calculation should be able to compensate for this and increase the descent lenght, I don't have this problem with the MD-11 nor the 747, only the NGX so it might not be a higher CI but rather maybe a little variable that is out of whack in the calculation algorithm or whatever it uses to do the calculation.

AS for the CI being high, yes the descent speed would be faster, but in theory the FMC should compensate and put the TOD further...which it doen't, so I doubt its the CI, for example off topic FedEx uses a CI of 200 on their MD-11, before the econmy went bad they were using 685, so even with higher CIs the FMC should be able to compensate in the TOD calculation taking into account the descent speed

I followed the instructions as in I uninstalled everything and reinstalled everything with SP1 My usual CI is around 85-95, descent speed is usually excessive because the plane nosedives The route in question was rather long but it happens with pretty much all my flights, one of worst ones being the BARET4 into KSAN, the VNAV always fails or causes a nose dive, but I've also experienced it with the ELDEE5 into KADW for example. As for my gross weight is always varies so I doubt it has an influence.

Actually this problem started rearing its ugly head after Installed SP1, before SP1 it was working fine, not sure and for the tutorial flight can't say I've tried it

The TD does show up in the ND, say I'm at Flying at FL380 and this fix I need to cross at FL270, the TD will be like 30 NM from the fix I need to cross so often it will either go into a death dive or the VNAV kicks off and say the descent path is unachievable

Yep I got all that covered, but still no luck

I'm probably not the first one to report this, but for some reason my TOD is always off, resulting in the plane going into 6000fpm descent or even more often VNAV kicking off with the Descent path unachievable error on the FMC.No matter what I try it constantly does this, I always set the runway and the correct altitudes for the STAR yet it constantly happens, am I missing something here? I even try starting the descent early but no luck. Is this a bug or is it something I'm forgetting here?ThanksTrystan

Well I have done at least 6 flights now without the CTD occuring, so its either something with TCAS being on or having peer to peer activated in Fsinn

Okay, I just did the flight again online, after finding something on the VATSIM forums, this Flight I turned the TCAS off and also disabled peer to peer in the FSinn menu, so one of these things seems to have done the trick cause it didn't CTD

Somebody suggested I check my event viewer to see what caused the crashes and this what I found for the crashesLog Name: ApplicationSource: Application ErrorDate: 17/08/2009 2:19:34 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: Trystan-PCDescription:Faulting application fsx.exe, version 10.0.61637.0, time stamp 0x46fadb14, faulting module TCAS2v7.dll, version 1.1.6.0, time stamp 0x4633aecd, exception code 0xc0000005, fault offset 0x00006186, process id 0x100c, application start time 0x01ca1ee21b2a1d5c.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-08-17T06:19:34.000Z" /> <EventRecordID>2647</EventRecordID> <Channel>Application</Channel> <Computer>Trystan-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>TCAS2v7.dll</Data> <Data>1.1.6.0</Data> <Data>4633aecd</Data> <Data>c0000005</Data> <Data>00006186</Data> <Data>100c</Data> <Data>01ca1ee21b2a1d5c</Data> </EventData></Event> Also Log Name: ApplicationSource: Application ErrorDate: 17/08/2009 8:29:55 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: Trystan-PCDescription:Faulting application fsx.exe, version 10.0.61637.0, time stamp 0x46fadb14, faulting module PMDG_747400_Main.DLL, version 10.0.61355.40, time stamp 0x483af60e, exception code 0xc0000409, fault offset 0x0007a848, process id 0x1158, application start time 0x01ca1f9a3922323c.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-08-18T00:29:55.000Z" /> <EventRecordID>2711</EventRecordID> <Channel>Application</Channel> <Computer>Trystan-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>PMDG_747400_Main.DLL</Data> <Data>10.0.61355.40</Data> <Data>483af60e</Data> <Data>c0000409</Data> <Data>0007a848</Data> <Data>1158</Data> <Data>01ca1f9a3922323c</Data> </EventData></Event> hope this might be of use, the most common error is whith the TCAS module

.