Ted Striker

I remember that audio channel and miss it. Occasionally the pilot messed up, which I suspect is why they ended it. I always thought it would be great to have a forward looking camera in the nose that the passengers could view on the seat-back screens. It seems like it would be inexpensive to implement with the camera technology we have today. Ted

When a doctor tells me I have a month to live I'll call you. I think I'd still jump off the snow covered side. Ted

Glad to hear you are well and enjoying your new location Noel. Ted

I'm looking forward to the stories about you showing your flight simulator to those women. 😁 Ted

The fact that it is asking you to press F1 to go into your bios before starting is a pretty good indication that the bios is not able to store your settings due to a dead battery. That is exactly what mine did. Having to reset your date and clock every time you start the computer is another symptom. Ted

I have the same motherboard and its been rock solid since I bought it but I also lost my overclock a few months ago. The reason was because the CMOS battery was old and couldn't maintain the proper voltage. I replaced the battery on the motherboard and it is fine now. The batteries are only a few dollars. I suggest you check your battery as it is probably just as old as mine was. Ted

I kept wondering while reading through this thread, what takes longer to start up from cold and dark, your simulation system or the 737NG you are simulating with it? I can sense your excitement about receiving the computers and am looking forward to your first test flight report. Ted

If Eaglesoft is willing to issue patches, make available for P3D, and add more functionality to an aircraft that has been on the market this long for free, the least I could do is help test it. It was my pleasure Ron. I just wish I had more time available to test it. Ted

I have the same priorities and I have found this aircraft addicting. Like flying a real plane, it seems like I learn something new about it on many flights. I would just like to add that all the issues I had in this thread: http://www.avsim.com/topic/490303-need-help-from-other-eaglesoft-citation-x-pilots/?hl=+citation have been resolved with the latest updates. I have the one purchase installed in FSX boxed, P3Dv2, and P3dv3 on the same computer and it works fine in all three. The only issue I am having is I get an FSX crash when exiting the sim after using this plane. I suspect that it is due to something with my FSX install as this does not occur with both P3D versions and no one else has reported the issue. Happy to be able to fly it again and with the added functionality. Really looking forward to the next version. Ted

You'll definitely want to contact Justin at Toposim if you have a life time membership. That admirable man is honoring the old life time memberships. Ted

You might have a lot of dust and lint in your cooling airflow passages. If you like the laptop it might be worth it to open her and inspect it. I have three W7 Lenovo T410 laptops that I am trying to decide whether I want to migrate to W10 to extend their life. They are working so well now I hate to mess with whats working good. Ted

Thanks for the responses guys. I thought that the ORBX regions and some airports had a lot of photoscenery and once enabled in the scenery library it was loaded at full resolution and remained in memory until the sim session was ended. I assume with the new ORBX system having all of the regions loaded simultaneously is not a problem anymore. It sounds like ORBX is working well for most now so I will give it a try. Ted

I was in the process of rebuilding my sim installations when these migrations issues started. As a result I have not reinstalled my rather extensive ORBX scenery. It does appear that the bugs with the wrong textures and blurries have been resolved, however I have the same concerns as Bruce B above. My understanding is that one of the reasons for the FTX region switching and ability to only load the regions you needed was to reduce your VAS load and improve the sim performance. With the new "migration" FTX Central I would think loading up all of the ORBX regions at once would have a significant impact on performance and VAS. How has this been addressed if at all? Stew mentioned using another third party software, Simstarter, to manage what could previously be done in FTX Central. How is this progress? I have read all I could find at the ORBX forums but have not seen this addressed. I understand that something had to be changed to allow the new NA landclass to work, but why eliminate the previous region activation options to reduce VAS and improve performance? Was the intent of ORBX that all this should be done now in the scenery library or with a third party scenery manager? Has the new post migration system improved the performance of FTX regions and airports so much that you can load everything up at once and it doesn't impact performance? These concerns are keeping me from reinstalling ORBX. That and having to block an addon from accessing the internet to keep my Sim the way I like it. I would like to reinstall my ORBX scenery and would appreciate any knowledgable feedback on this. I realize I should ask this on the FTX forums but I am afraid a question like this, no matter how sincere, would result in an instant removal and ban. Ted

This is good news. Not knowing what the future holds with this migration thing, the Flightsim Store, and the ORBX store I spent of good portion of the 4rth downloading the latest versions of all my ORBX products. Palm Springs, Anacortes, and Felts Field were the 3 that weren't available at all, even with the old installers. Ted

Ankh, I have the same CPU, overclock, and RAM speed as you. Differences are I have a 780gtx, 8 gb Ram, HT off, and a 3960 x 1024 triple monitor setup. My performance is similar to what you are experiencing. I run at 30 FPS locked in the sim as this is the smoothest for me, I just need to adjust sliders to keep it above 30 FPS locked. As Sethos stated, if I run unlimited FPS my FPS is higher, but not as smooth. The single largest framerate killer for me is AI traffic. Next is complex aircraft cockpits. After that is heavy weather, scenery and autogen density. I do not use NI or SGSSAA and just put up with the shimmering. After awhile I get used to it.....until I go back and take a flight in FSX with DX9. I adjust the scenery density and traffic levels to depending on the weather and aircraft I am flying. Fortunately, the more clouds you have the less you notice turning down the scenery density and traffic until you arrive at the terminal. Reducing my sim window to one monitor gives me a good boost in FPS. However I prefer to reduce the graphic detail than loose my peripheral vision. Do to the heavy performance hit of ORBX scenery and complex aircraft I keep them separate. I run my GA aircraft and ORBX in P3dv2. I use P3Dv3 for complex aircraft with GEP3D/UTX. One last thing. If I load the default baron and put all of my sliders to minimum my FPS goes to 300. So unless those posting unbelievable high performance post all of their settings, I would take it with a grain of salt. Ted

I did not know that the Eaglesoft CX 750 was the only biz jet available with working VNAV and the other avionics capabilities that Gregg mentioned. No wonder I'm so addicted to it. Ted

Sorry to hear that. The only thing I can think of is to read through the CTD guide and see if you can find any other clues. Your event viewer found in the windows manage computer dialog box will state the error code and file that is causing the crash. The file causing the crash may have a section covering it in the CTD guide. Also if you post your crash log here as described in the CTD guide someone on the forums may have some other ideas. Edit: One other thing. Your video card is about the oldest I've seen in awhile. Upgrading the drivers may help if they are as old as the card. You have a good CPU. Upgrading that video card to Nvidia x70 or x80 series will give you quite a bit better graphics quality. Ted

Freezes from accessing the drop down menus has been attributed to the UIAutomationcore.dll. There is a good write up on this on page 25 of the AVsim CTD guide. You can access the guide by a link on the right side of this web page. Ted

I didn't find DTG Martin full of hot air, but rather restrained in his comments. All the "hot air" I saw was from other Avsim members that weren't happy with what DTG was proposing/released and wanted something else. I appreciate Martin and all the developers that have the courage to share their thoughts with this some times rude and disrespectful group. Both the FSX Aces and LM P3D staff initially posted here until they got tired of putting up with it. Those were sad days when they stopped. I imagine DTG had their hands full just converting FSX to 64bit for Flight School and expect they will now begin the process of activating and adding improvements. Besides introducing Flight School as an inexpensive introductory package with ORBX Global for those new to flight simming, I expect it will be used as a testing ground for their new flight sim. I am looking forward to reading Martin's reports. Father Ted

Thanks for explaining what that waypoint does Ed. Yodah, thanks for posting. That information may be helpful for Ed. I didn't get the crashes with the FSUIPC you are using either. Only with the next version 4.950 and later. Edit: I forgot to mention. I tested the Citation X in P3Dv2 and P3Dv3 last night. With the latest NAV cycle and latest FSUIPC it does not crash after takeoff with the KLAS25R BOACH6 HEC RIIVR2 KLAX flight plan if you load the flight at KLAS, let the panels inititalize, and then reload the plane before programming the FMS. Ted

Jim, I only get the "DATA LOAD 128" message when the flight doesn't crash and about the same time that the crashes were occurring. To prevent the crash I ended the flight then reloaded it before programming the FMS and proceeding. Aerostar, good thought and you are probably right. I am not loading that waypoint, it is entered automatically when the SID is selected. But as you said maybe it is not spelled correctly in the database. I zoomed in and it is hard to tell whether it is a 0 or an O. It makes more sense that it would be ALTernate 01 rather than ALTO. I didn't think about it before I made the post above. Ted

I'm interested Ron. I will PM you with my contact info. You are amazing Jim! How do you find this stuff? Ed, I'll volunteer. I also just discovered something else today. Just after I made the post above about the *ALTO1 way point I was bouncing around the country trying out different airports and I was able to depart a SID with the *ALTO1 waypoint. So I went back to KLAS 25R and tried it again there. It didn't crash but instead I got the DATA LOAD 128 message in the FMS at the same time as I used to get the crash. The only thing I did different was to start the sim at a different airport first. I then shut down the sim and tried again at KLAS and it crashed. Then I restarted the sim, loaded the flight at KLAS25R, ended the flight, then reloaded the same flight and it didn't crash. So it appears, for me anyway, that reloading a flight before starting gives me the DATA LOAD 128 message instead of a crash. Both occur just after passing *ALTO1 waypoint and testings was only done with FSX. I haven't tried P3D yet or just reloading the plane instead of the whole flight. Hope this information helps. Ted

Jim, I have the same results. If I do not use the BOACH6 SID it does not crash. For me it is a strange frustrating Bermuda Triangle that requires a SID with *ALTO1 as first waypoint, recent Nav Cycle, and recent FSUIPC. That is the witches brew for a crash on my computer. Ted Pat, It is specific to this flight and others. What I have found is that with this flight and others that have *ALTO1 as the first waypoint I get the crash. If I use the PERFUM3 departure from KLAS 25R which does not have *ALTO1 as a waypoint I do not get the crash. Any SID I use at any airport with the *ALTO1 as the first waypoint crashes. I have flown the CX for years without this problem. It is just recently with the latest Nav cycles and latest FSUIPC versions that I am experiencing this issue. I am trying to determine if it is specific to my ( and now also Jim's) computer or if it is occurring with others as well. Would you mind trying the flight plan I posted above on my original post? Thanks, Ted

Thanks for testing this Jim. Sounds like you are having the exact same issue that I am experiencing. Hopefully someone else will participate that has an idea of what is causing this. Ted

I have recently been getting a consistent sim CTD with this plane on takeoff at a number of airports when using the FMS. I am trying to determine if it is isolated to my computer or if others experience the same. I would appreciate it if others with this aircraft would try this short (due to crashing) flight and report back on this thread. The Flight Plan is KLAS 25R BOACH6 HEC RIIVR2 KLAX. If it is going to crash it will happen before you get to the second way point so it is a quick test except for initially setting up the flight. I only get the crashes using the latest Navigraph updates (1605 and 1606) combined with the latest FSUIPC versions 4.950 or later. What has me baffled is that if I use the default NAV database that comes the plane (1107) I do not get a crash with the FSUIPC v4.950 and later....or if I use an FSUIPC version earlier than 4.950 I do not get a crash with the laatest NAV cycles. So if you don't have both a recent FSUIPC version and the latest NAV updates you don't need to try this test. I have enjoyed this plane for years until just recently when these CTDs started occurring. When Eaglesoft updated the Citation X for P3D I uninstalled the old FSX only version and installed the latest version along with the latest NAV data and FSUIPC. That's when my problems started. For me this issue is not sim specific and occurs in FSX, P3Dv2, and P3Dv3. I have tried the manual and FMS Data Manager installers for the NavData with the same disappointing results. I have reinstalled my sims and the only active addons are the Citation X, Navdata, and FSUIPC. I have posted about this on the Eaglesoft, FSUIPC, and Navigraph support forums. All three do not know what could be causing this with their respective software. I have tried everything that has been suggested to me and everything I can think of to correct this on my computer. So before I rebuild my otherwise fine running computer I thought I'd ask here if anyone else was running into the same issue. Appreciate any help with this, Ted