Jump to content

Jim Young

In Memoriam
 View Profile  See their activity

  • Content Count

    18,287

  • Donations

    $200.00 

  • Joined

  • Last visited

Posts posted by Jim Young

  3. Posted

    I see you run FSX in Admin mode. But, have you gone into the Realism page and enabled detect crashes and damage and then check one of the options - Aircraft stress causes damage and/or Allow collisions with other aircraft? I know some of the fsx.cfg settings return to the default like the value for TML. Perhaps another aircraft is controlling realism as it has it's own realism. Does FSUIPC have a setting that could prevent anyone turning on crash detection?

     

    Best regards,

    Jim

  4. Posted

    This is an automatic message.

     

     

    This topic has been moved from "TTools for MSFS Forum" to "MSFS Aircraft and Panel Design Forum". This move has been done for a number of possible reasons.

    • The most likely reason is that the post was off topic.
    • The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
    • The images might not have been "illustrative" or "explanatory" in nature.
    • The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

    Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums.

     

    Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

  7. Posted

    Thanks Paul (again)!

     

    I added the BufferPool entries to my FSX.cfg but left Water at 6. Still saw the black shadows on the water. Went back and changed the Water setting to 5 and that did it and it's difficult to see any difference in the quality of the water. Awesome. You the man!

     

    Are you see some jagged shadow edges in the cockpit and I mentioned above? It's not a biggy to me as shadows are shadows and they look good no matter what. But, in my earlier testing with FSX AA/AF turned on in FSX and off in the NI settings, it was a lot smoother, not perfect, but smoother lines.

     

    Best regards,

    Jim

  10. Posted

    Just forget about fsx.cfg settings for AA and set your nvidia inspector like this:

     

    Mike,

    I tried your settings in OP and I'm getting jagged lines when the shadows from the sun are displayed on the aircraft panel. Works great on the outside and for the panel itself but not for the great feature of DX10 and that's the sunlight hitting the panel or inside the aircraft. It was really bad until I turned AA back on in the FSX settings. Then it was a bit better but still get jagged lines. I tried turning FXAA on and that did nothing. I tried Nvidia Predefined FXAA usage and that didn't work. I have the EVGA GTX 580 Superclocked Video Card. I have to say the images are appear a bit better that with Paul's settings or mine but I'm getting even more of those dark flickering shadows near land over the water. Where I do my testing is at Friday's Harbor with FTX/Orbx PNW scenery enabled. Perhaps my problem(s) are associated with Texture Filtering AA Settings. Here is a copy of my settings -

     

    582DX10_FSX_Settings.jpg

     

    Thanks for the info in the OP and your contributions.

     

    Best regards,

    Jim

  11. Posted

    The event viewer on my windows 8 x64 box show errors related to d3dl.dll however (fsx crash dumps).

     

    The d3d9.dll in the FSX main folder is related to the ENB Series. If you have this addon installed, it's causing your crashes. It's a common crash and I removed it from my FSX a long time ago. Many have gotten it to work and have nothing but total praise for the addon. To get rid of the crashes, delete the d3d9.dll from the main FSX folder. Also delete enb.ini or you'll get even more crashes.

     

    Best regards,

    Jim

  13. Posted

    Jim,

     

    After a nice long telephone conversation today with Paul, it was concluded that a reinstall was my only option. Thanks for taking the time to help me out with this, I will let you know once I am fully back up and running.

     

     

    Mark.

     

    Hi Mark,

     

    I was thinking that would be the ultimate solution. Ugh! Good luck on the reinstall!

     

    Best regards,

    Jim

  14. Posted

    This is an automatic message.

     

     

    This topic has been moved from "MSFS Aircraft and Panel Design Forum" to "MS FSX Forum". This move has been done for a number of possible reasons.

    • The most likely reason is that the post was off topic.
    • The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
    • The images might not have been "illustrative" or "explanatory" in nature.
    • The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

    Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums.

     

    Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

  17. Posted

    Hi; First time posting here hope someone can help me out. I reinstalled Fs9 and Instant Scenery 2 and now when I am trying to use the thumbnail maker in IS-2 Fs9 crashes and gives me the following message " fatal error occured Error signature App Name fs9.exe App Ver 9.1.0.40901 Mod name g3d.dll Mod Ver 9.1.0.4091 offset 0003f7b1" This is completely confusing to me and I would ask someone out there to help me get things working right if possible. Thanks in advance Robin

     

    The latest version of FSUIPC.dll has the fix for the g3d.dll crash. It's a fix for FSX and I would assume it fixes the issue in FS9 too. Here's the link - http://www.schiratti.com/dowson.html. Make sure you download the FS2004 version. It's freeware.

     

    Best regards,

    Jim

  19. Posted

    I doubt the uiautomationcore.dll fix is really a fix at all. It works for some but not for all so it is not a fix. The uiautomationcore.dll belongs to the .net framework program - http://msdn.microsoft.com/en-us/library/ms747327.aspx. As stated in the article, all versions are suppose to be compatible with multiple frameworks. Most software developers use .net framework and ui automation to make there product work properly in FSX. Some of the older none FSX software was not developed with .net framework as this technology was developed about the same time as FSX/Acceleration was developed. This is why I think it's an older addon that is creating the problems. FS9 was not used when FS9 or FS9 addons were developed. Your sim crashed when the uiautomationcore.dll was being called. Something happened where FSX could not find a texture or file that was required for a program so FSX crashed. That's one possibility. So what is that program? Requires more investigation....

     

    Another piece of software that developers use to install and run their addons is Microsoft Visual C++ Redistributables 2005, 2008, and/or 2010. There was a SP1 to the 2005 MSV that was not included with Acceleration and is required. So you want to make sure that SP is installed. You might look at the MSV site and make sure you have all the SP's installed for each MSV. You'll see that on any page of the MSV downloads. If the product a developer developed with MSV 2005 does not install the way he intended (registry items are what he wanted and file location), then there may be problems. Again, developers did not use this technology to develop FS9 or FS9 addons. Perhaps that's why some say you need to buy addons that were developed specifically for FSX or were converted to be compatible with FSX.

     

    If that doesn't fix the CTD, then I think there might be a problem with BIOS settings. I see you are not really overclocked and just have Turbo Mode turned on to give you a 3.9GHz CPU speed. That means to me that you probably have your BIOS settings for Frequency set to Auto. This means your system set the DRAM voltages, frequencies, and timings automatically. For some ASUS boards, this has been reported as a problem as ASUS boards do not manage memory well in the BIOS. Your CPU voltage was also set automatically. For your system, I would not go any higher than 1.40000. Too low of a setting will also cause problems. Set a voltage no lower than 1.380000. If not properly set, these settings will eventually cause crashes.

     

    Another possibility could be a bad tweak in the FSX.cfg. You can check that by renaming your fsx.cfg to fsx.orig, then restart fsx and let the sim rebuild the config. This will bring the config back to default settings. I don't recommend changing any of the settings, especially under the scenery and AI tabs. Load your flight and see if the problem goes away. If so, there's a problem with a tweak or a high FSX setting.

     

    Hope this helps.

     

    Best regards,

    Jim

  22. Posted

    Mark,

    I see nothing in the additional report you provided above other than the FSCoPilot.dll module which has caused crashes for some in connection with FSInn. But according to the report, visualfx.dll caused the crash. Memory exception code 0000005 indicates you had a Memory_Access_Violation. So, the way I understand it, when visualfx.dll was being called by FSX, it could not find something that was required to perform a function and crashed. You said earlier that you installed Steve's DX10 Shader fix. Does the crash occur if DX10 Preview is not enabled? Are you using the Addon_Converter X to convert FS9 textures to be compatible with FSX and DX10? My Googling indicates many have had this problem if they moved or accidentally moved a texture folder. Did you delete the shader10 folder in AppData\local\FSX\Shaders after installing the DX10 Shader Fix?

     

    Best regards,

    Jim

×
×
  • Create New...