Jump to content

Jim Young

In Memoriam
  • Posts

    18,287
  • Joined

  • Last visited

  • Donations

    200.00 USD 

Everything posted by Jim Young

  1. Excellent video Craig! Thanks! Best regards, Jim
  2. Have you run AppCrashView and the Event Viewer as shown in the AVSIM CTD Guide (see link in my signature). Perhaps it was something else that caused the crash. Old programs like FSOpen that were made exclusively for FSX will probably have difficulties with P3Dv3. I was looking at the sessions and all of them are with FSX. None with P3D.
  3. You received a kernelbase.dll crash (according to the report you posted). Page 32 of the AVSIM CTD Guide (see link in my signature), states: Kernelbase.dll – No known fix but some have solved this problem by - Updating or reinstalling their video card drivers. Scanning your system for corrupt/missing files. Disable startup programs by typing msconfig in the Windows search box. When open, look at the Startup tab and disable all startups (they are all not needed for operation of your computer). User Profile Corrupted – last resort, fix possible corrupted user profile.
  4. Did you run AppCrashView or check out your Event Viewer? See AVSIM CTD Guide for links and directions (see link to the guide in my signature). A 2-3 hour flight can result in an OOM because of the loss of VAS. I have had several. Back in 2007, you could fly for hours without an OOM because the systems were not as powerful as today. Everyone knew they had to manage their settings to prevent an OOM. There was only 2-3 GB's of VAS back then too. Now Microsoft Windows has given you 4 GB's and people think they have a very powerful system and can crank up all of the sliders and, when they do, there's an unknown crash. So, unfortunately, you have to lower your p3d and display driver settings.
  5. Appears Colton is a pirate as he failed to come up with the Orbx order numbers they requested - http://www.orbxsystems.com/forum/topic/118361-scenery-library-priority-help/?do=findComment&comment=1063774. He then came here asking basically the same questions he posted in the FTX/Orbx Forums. I'm sure he is happy for the support received here!! Topic locked. Member will be banned.
  6. Okay, thanks for the explanation.
  7. The OP can post anything about Orbx here. Please do not moderate our forums.
  8. Nice! You have duplicate buildings in Las Vegas though (see the second to last picture). Looks like duplicates in the city too. Make sure you disabled KLAS in MyTrafficX scenery (if you have it). Still can't believe how crisp and clear your images are.
  9. If you go to the PMDG General Forum you will see they are working on the server - http://www.avsim.com/topic/492237-23jul16-oops-seems-we-still-have-activation-server-issues/. AVSIM only hosts the PMDG Forums and you will have to ask your question in the PMDG forum or go to their website and submit a trouble ticket. Best regards,
  10. One person fixed his by deleting or moving his p3d.cfg to a temporary folder, then restarting P3D and letting the config rebuild. Most likely your settings are too high or you put a tweak in your config (bad!). More info - http://www.avsim.com/topic/471204-constant-gdiplusdll-crash
  11. Enough is enough. Topic closed.
  12. Please check the topic just below yours regarding the G2D error - http://www.avsim.com/topic/492281-g2d-error-mid-flight/
  13. Kind of a sharp and quick response huh? This IS the FTX/Orbx Support Forum and they sometimes visit here. He may have posted on the FTX/Orbx forum too. Members get a bit upset when you make inciteful comments like yours, including me. We have user-to-user support here and the OP is looking for the user to user support. I suspect he was just letting us know he saw the scenery had a missing object. I hope you can be more tactful with your response in the future. For me, I'm wondering if the OP has his scenery complexity slider moved to the far right. Sometimes scenery is made with the scenery complexity slider all the way to the right.
  14. It is a lot of fun building your own computer! Best regards, Jim
  15. FTX/Orbx Pacific Northwest Region.
  16. Page 32, AVSIM CTD Guide, states there is no known fix but some have solved this problem by - Updating or reinstalling their video card drivers. Scanning your system for corrupt/missing files. Disable startup programs by typing msconfig in the Windows search box. When open, look at the Startup tab and disable all startups (they are all not needed for operation of your computer). User Profile Corrupted – last resort, fix possible corrupted user profile. The guide has links to "how to" for some of the probable fixes. See a link to the AVSIM CTD Guide in my signature. I also found where an individual successfully fixed his problem at the following link - http://www.prepar3d.com/forum/viewtopic.php?t=118095. It confirms the possible solutions found in the AVSIM CTD Guide. Best regards,
  17. Avast is an anti-virus program (I just checked their website and do not see any cleaning software). How can you use it for cleaning? Avast is not good for FSX users and I have heard of many getting "false positives" when installing FSX. Of course, this is what anti-virus programs like Avast is supposed to do... keep the evil people from putting evil stuff on your computer to make it go bye-bye. :smile: So, if you had Avast installed when you installed FSX, perhaps Avast quarantined a file it thought was a virus. I can tell you right now that it would be near impossible to tell you what texture file is missing. What's your best option now? I would suggest you place your FSX disk in your DVD drive and select "Repair". When that is completed, you will also need to place the Acceleration disk in and select repair for that program too. You can then restart FSX and see if the problem has been fixed. Before you do the repair option, you want to go into any anti-virus and/or malware program you might have installed on your computer and make sure the program does not scan your fsx directory or the directories of any of your add-ons. Just look for Anti-virus or Anti-Malware Exclusions or something like that. You don't need your anti-virus or malware programs to scan FSX as you know exactly what is being installed in this folder. When you buy an add-on for FSX, you know the product is safe. It's the attachments you get from e-mails or downloading stuff from unknown sites where you could get into trouble. What will happen when you do a repair of FSX? It will put any missing file back on your computer. You will want to back up your Scenery.cfg and your fsx.cfg as those files will be overwritten and returned to the default settings. After you do the repair, you can return these files back to the appropriate folders. Everything else will remain intact. It won't mess with any of your scenery installed or any add-on aircraft as it only overwrites the default stuff. If you have any further issues, let us know.
  18. Some great deals from REX. Thanks! Best regards, Jim
  19. Then I was wrong. I have no other solution to offer. Sorry.
  20. Run SceneryConfigEditor. When open it will show you the mistakes in your scenery.cfg usually in red. You can then click on edit and fix it.
  21. I'm the moderator. The post was irrelevant!!! Plus, in the OP, I placed a link to the topic. What's wrong with that? Topic closed because we have some who desire to troll.
  22. I've never seen fsx shutting down to the setup (free flight) page. It has always shutdown completely. Make sure you have Microsoft Visual C++2008 w/SP1 installed. Microsoft Visual C++2005 w/SP1 is required but PMDG used the 2008 version. Since you installed FSX into the default program files x86 folder, make sure UAC has been turned off. So you were able to use and fly the PMDG 737? But, when you ended the flight, fsx crashed and then restarted? When it was restarting, you should have been given an option to cancel. Crashes at the end of your fsx session are common. I get them once in a while but they go away. Make sure you have gone to the main FSX folder, right clicked fsx.exe and selected properties, and then click on the compatibility tab and make sure Run as Administrator box is ticked at the bottom. None of the other boxes should be checked. You want to make sure Run as Administrator for ALL users is selected. These suggestions for fixing this problem can be found in the AVSIM CTD Guide (see link in my signature). Topic will be moved to the proper CTD Forum.
  23. I did a search in this forum for error 1603 and found where one individual found a solution - http://www.avsim.com/topic/406185-solution-error-1722-and-1603-fsx-gold-edition-windows-8/#entry2653817 Maybe it will help you.
  24. I will let the following link answer your question - http://www.urbandictionary.com/define.php?term=necroposting
  25. The G2D error has nothing to do with temperatures and voltages. See the AVSIM CTD Guide, page 32, has possible solutions for this error. I suspect the dll.xml or exe.xml. If you moved your the entries in your dll.xml in the folder where your p3d.cfg is located to the dll.xml in the folder where your scenery.cfg is located, that could be the problem as your entries may be corrupted. There are some entries in the dll.xml that must remain in the dll.xml located in the same folder where your p3d.cfg are located. Currently, I have the following still located in this folder: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>ObjectFlow_P3D</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>K:\Prepar3D_v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>as_connect</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp.dll</Path> </Launch.Addon> </SimBase.Document> As stated in the CTD Guide, move your dll.xml to a temporary folder and see if this fixes the problem. If you have two dll.xml's, move only one, and see if it fixes the problem. If so, the problem is in that copy of the dll.xml. Best regards,
×
×
  • Create New...