ksp0011

I've played around some more and found out the cause of my problems. If I want to enter a track waypoint for a navaid (such as GEG), I have to line select the appropriate entry on the LEGS page to bring the three letter name down to the scratchpad and then type /-10 or /10 (or whatever distance I fancy) as appropriate before line selecting the entry again. For a fix, i.e. I can either line select it to bring it down to the scratchpad and do as above, or alternatively I can just completely type in the whole fix with the /-10 using the keypad before then selecting the relevant LSK. Now I have no idea how the real FMC behaves. The FCOM doesn't seem to imply that you should line select the waypoint to bring it down to the scratchpad before appending the distance but that seems to be what you need to do. Hopefully that makes sense. Oh, and I checked, SEA and PAE are 29nm apart according to my low enroute chart and with the above method I can now enter track waypoints less than 1nm from the original (although even I'm not sure why I'd want to!) and if you type a distance which is further than next waypoint, it will rightly come up with 'Invalid Entry'.

Just been doing circuits at KMWH again getting a feel for the aircraft and noticed your post. Dan, you are correct it is line select the waypoint you are creating a track waypoint for - so in my case for GEG, you would always select GEG. So whilst on the downwind, I created a RTE2 plan from KMWH to KPAE with direct waypoints of MWH, GEG, SEA and PAE. When I entered a SEA/-20 or SEA/20 it worked and I ended up with SEA51 and SEA52 (as they were RTE2 psuedo waypoints. Flushed with success, I tried to enter one as GEG/20 and it failed. Then no matter what I tried to add it came up as invalid entry. Even if i deleted SEA51 and SEA52 it still would then not allow me to enter a track waypoint relative to SEA. Back on the ground, I have been playing around some more and have the following initial findings: i) it will not accept a track waypoint relative to the first fix in your route. i.e. if i enter SEA as my first waypoint and PAE as the second, it will not allow a SEA/10. ii) it does not seem to like MWH, GEG or MLP for any reason. iii) once you get the 'invalid entry' message it will not work with any waypoints until you reset the route on the init ref page. If anyone fancies seeing if they get similar results, please let me know. When I get a chance, i will try a different location in the world in case there is something wrong with the database although I am not quite sure how that could affect it (I am using the default).

Dan. I can confirm that is what I have been trying and it gives me an error when I use a waypoint that is a navaid (i.e. one with a three letter descriptor such as GEG or MLP). I line select either the line with the waypoint or the one after depending on whether I want it before or after and it always comes back with 'Invalid Entry'. Five letter waypoints are fine. And to answer's Brian's question, I made sure there was at least fifty miles around each waypoint as I can imagine that would throw an error. Perhaps you could both give it a try and see if all have same issue or if it is a quirk of mine?

Hi all, I'm really loving flying the new -400 on P3dv4 but I'm having a problem with one function of the FMC. Before I explain, I have done the tutorial, read the FCOM and searched the forums and known issues list but can't find the answer. If it is there and I have missed it, I apologise. The problem I am having is with "Manually Entered Along-Track Waypoints" as described on page 11.31.17 of the FCOM. I am currently doing short flights out of Moses Lake, and if I enter one relative to a fix, such as UPBOB using the format UPBOB/-10 it works. If I do the same thing relative to a navaid such as GEG or MLP using the format shown in the FCOM as GEG/-10 or MLP/10 and line select above or below the respective LEGS entry, I get the FMC message "Invalid Entry" and it won't accept it. Does anyone else have this problem or am I doing something wrong? I am running the latest -400 update and P3Dv4 is at version 4.1 Many thanks

Thanks Jim, Fantastically quick response. Not usually keen on those programs that scan your computer and tell you what needs updating but tried it and it suggested a more recent Intel HD driver. Wasn't available to find it on Intel's website but found a version to download with a Google search (even more nervous about drivers from unknown sources!). Touch wood, it seems to be working fine - I can change settings over and over again and it hasn't crashed one yet. For those in a similar situation the driver I used is 10.18.10.3325. I will report back in a few days with an update. Kevin

Hi, Just built a new system and keep getting Fatal Error CTDs with the faulting module being shown as igdumdim32.dll. Simple specs are : i7-4770k on an ASUS Z87-A board 16Gb ram of 1600MHz (memtests OK) No graphics card - using the onboard Intel HD4600 Windows 7 64 Ultimate Using latest ASUS drivers Runs fine on opening with 1920*1080 and most settings to the right (Autogen at Medium to low) with 20fps locked. (even with Orbx PNW installed) HIGHMEMFIX=1 mod has been applied. Tried uiautiomationcore.dll but makes no difference. Basically what happens is if I keep selecting the menu to change aircraft or graphics setting it eventually crashes when going to reload the textures, autogen, etc. with the above error - copy of Event Viewer info below Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3 Faulting module name: igdumdim32.dll, version: 9.18.10.3257, time stamp: 0x51f73fa8 Exception code: 0xc0000005 Fault offset: 0x000b0581 Faulting process id: 0x1664 Faulting application start time: 0x01ced413a53041ab Faulting application path: E:\FSX\fsx.exe Faulting module path: C:\Windows\system32\igdumdim32.dll Report Id: 235121ee-4007-11e3-bf85-74d02b92c925 Set application compatibility to Vista (SP2) ; Run as Admin but still crashes. Tried different Intel graphics drivers (new and old) but makes no difference. Even tried installing on fresh Win 8 Enterprise trial but get the same error. From a bit of experimenting seems error occurs after installing FSX SP2 although that could be imagination. Any thoughts? Anyone else suffered with this - and would a dedicated graphics card help although trying not to spend too much more (and 20-30fps is fine for me!) Thanks, Kevin