Jump to content

Jim Young

In Memoriam
  • Posts

    18,287
  • Joined

  • Last visited

  • Donations

    200.00 USD 

Everything posted by Jim Young

  1. I've looked all over and cannot find anything regarding this error in the SceneryConfigEditor: As you can see, some are okay. All of the scenery works perfectly. I have a feeling this is a Java issue (although I have the latest issued). Thanks for any suggestions on how to fix this! Man must have perfection.... EDIT: Forgot to mention I have manually linked them but after a flight or I move scenery around, it goes back to this. Best regards, Jim
  2. Think you are right Charlie. Make sure you followed the directions for uninstalling in the following document - http://support.precisionmanuals.com/kb/a87/how-to-uninstall-and-reinstall-fsx.aspx. Once uninstalled, then you should run a registry cleaner like CCleaner. Restart Windows and then try reinstalling.
  3. Where can you download FSX? There is no download for FSX.
  4. The settings in the AVSIM FSX Configuration Guide will eliminate all jaggies (at least it does for me). Best regards,
  5. The AVSIM CTD Guide provides a link to BlueScreenofDeath (BSOD) view. When you view the BSOD, it provides information in pink as to the probable drivers that caused the BSOD giving you a good clue as to the cause. BSOD's indicate a hardware problem so they should not be taken lightly. I would get that issue fixed first and then try your flight again. It could be just a corrupted driver. There are many driver update programs on the Internet and it costs nothing to download one and see if you have any outdated hardware drivers (USB ports, sys bus, HDD, SATA controllers, etc.). I use Driver Booster which is totally free but has a lot of ads and nags to get you to purchase a license. Still it is free. The Affinity Mask tweak requires some computer expertise as the setting is not the same for everyone and, if it is wrong, you will have even more problems. Try turning off cloud shadows. Just leave shadows for your aircraft. I have found cloud shadows are a major resource hog and I do not have them turned on. It's just more eye-candy that can slow down a system. Nice effect though...
  6. Great video Jose. Thanks for posting! I'm moving it to the FS video forum though. Best regards,
  7. Those were awesome! Even at 51% they looked great! Changing the resolution even higher makes them even better. Thanks for posting the link. Best regards, Jim
  8. P3D is DX11 and someday DX12 capable. FSX is DX10 Preview capable and will be like that forever. DX11 and 12 provide more ah-gee-wiz stuff. DX10 is certainly better than DX9 but slightly broken as the developers of FSX did not have a chance to finish the programming. Best regards,
  9. Thanks Dave for those kind comments. As I have stated many times, FSX/P3D run great with the default setup and no addons. Heck, you can even turn up your settings higher and it will work well. Then you start adding add-ons like weather, eye-candy airports and aircraft, and fancy eye-candy ground textures and things go downhill fast. Of course each addon developer is not going to give in to making his product work as well as the default. Well, the default is, the default and they are replace it with huge amounts of eye-candy as eye-candy sells. This is why sim config settings, including the display driver have to be turned down somewhat depending on what you are running during a specific flight plan. People don't like that. They didn't have to have the settings turned down when just the default stuff was installed, why turn it down now? I like KSTL too and that's one of my top 10 destinations. I have Taxi2Gate KSTL so a lot of eye-candy. I have some issues landing there too some time especially in bad AS16 weather and in a PMDG 737 or 777. I sometimes fly from there to Wash Dulles and that's a chore when landing as my VAS counter shows I'm nearly out. It's all very upsetting especially if you have just spent two hours or so getting to the destination only to see an OOM or major stuttering. In P3D I have turned off ground shadows and that has helped a lot. Best regards, Jim
  10. I would say Reshade, like SweetFX, is not compatible with P3D unless it is configured correctly. The configuration used by others does not mean it will work on your system. For instance, you have EZCA installed (which is barely compatible with P3D) and those who have Reshade working do not have EZCA installed. For the Microsoft dotnet error, I suggest reading the information in the topic just below yours - http://www.avsim.com/forum/262-crash-to-desktop-ctd-forum/ We have a forum for SweetFX which you may or may not have seen. You might get some help there regarding Reshade which I have a feeling is another name for the ENB Series to protect the innocent. The ENBSeries hack causes a lot of crashes too. Best regards,
  11. The manual should have something about when you first start it up. There are BIOS beeps. Each beep indicates something like, no vga detected or no memory detected. If you did not detect any beeps or you do not see anything on your monitor w/i 30 seconds, then the system probably failed the power-on test and you will need to check out each jumper. Did the fan to the power supply turn on? Is the huge connection from the power supply to the MB connected properly? On mine, the huge connection falls apart so that it can fit several types of MB's and I have to make sure all pieces of it are fully connected. If the BIOS LED lights up it should also display a code if there is an issue and the manual shows what's wrong. There are several but most important would be the post state LEDs and the Q-code LED which provides a 4-digit error code. Should be in Chapter 1 of the manual. Best regards,
  12. It is impossible to determine the cause of a StackHash. It is a common error (as you state). It could be caused by high p3d settings, maybe a bad overclock (if you are overclocked). In any case, the AVSIM CTD Guide provides the list of all of the probable causes and possible solutions. For me, the first StackHash I ever got would never go away so I reinstalled Windows 7 and then FSX (P3D had not been released yet). Problem solved. On another occasion, it was a too high voltage setting in the BIOS. Got it too with MyTrafficX like many others did but that was before MyTraffic Professional 6.0a. I do not see them as much anymore. When I do get one, I think about what I did just recently that would have caused a StackHash all of a sudden. They did not happen yesterday or 3 days ago, they just started happening. If you cannot figure it out right away, you'll have to start investigating and investigating means moving your p3d.cfg, dll.xml, and scenery.cfg to a temporary directory. The p3d.cfg and scenery.cfg will be rebuilt. You want to do things like that just to see if it is one of the configs or something in the dll.xml. The AVSIM CTD Guide again provides guidance for investigating. Good luck in finding the cause.
  13. Oh! I suspect I should read the titles too! My apologies to the OP.
  14. I had to remove a few posts here because they were inciting/trolling posts. Dan started his post stating "just my opinion". That was his opinion and not fact. Members are allowed to post their opinions but responses to those opinions which are trolling or inciting Dan (and others) to respond negatively back is not appropriate. I ask everyone to please stop trolling. You can make comments like FavioSSA and others made about the product but to attack someone for expressing his/her opinion will not be tolerated here.
  15. Of course it is the Phenom 300. Can't believe no one else has recommended it yet! :Just Kidding: No really, I like it and it is my favorite right now. I know some have had issues with the G1000 but most have installed the GTN 750 to make it a lot easier to program a flight and fly. I may do that too some time in the future but right now I want to be confident I know the G1000 and Prodigy 1000 first (see barrel_owl thinks they are too complicated but I find them easy to program so far). The G600's for navigation are difficult to use too but that's what I think flight simulation is all about.... learning how to use them properly. Plenty of tutorials on YouTube for sure and the guys making the tutorials are not having any issues. Thanks for asking!! Best regards, Jim
  16. Thanks for the info. I know you know it's easy but it is not. I just do not have the time or the patience (plus I would rather blame ProATC for the bad data than blame myself for entering bad data....). I'm a strong supporter of ProATC-X but not for GA flying. Best regards,
  17. Seemed like a simple solution but who would have known. Those ad blockers are nice but they mess up other things (maybe on purpose so you won't use an ad-blocker). Best regards, Jim
  18. Like that idea but then, shouldn't there be a method where one can send his configuration of, say, the A2A 172 or other aircraft and add it to the list of aircraft available. I've tried that and it doesn't work so I gave up spending hours trying to put all the data in for one of my many GA aircraft. You make it sound so simple. It is not and the program does not always accept the data you provide even though you have the specifications for an aircraft sitting in front of your eyes. I think it is one reason why Mourad (the developer) decided not to showcase the GA. They are already having issues "perfecting" the program so we cannot be asking for them to jump into the GA arena right now.
  19. Great video with some nice scenery and aircraft! Nice landing too! Thanks for posting.
  20. All the latest versions of REX products should work without any problem in P3Dv3.3.5 Best regards,
  21. I just right clicked over the image in one of your forum posts at the weather site, saved the link to the image, and then came here and pasted the link into the Image icon in the menu. I like this one as it is slightly larger and provides some good information. I liked "Dave's" image (you responded to one of his posts) as he had used some scenery in the image. I don't really watch the sizes and the pixels anymore as the images are all linked and no longer uploaded to our site. I only get concerned if the images are too large and take up a huge amount of signature space. We still have some people who have slow Internet connections and loading of images, even from links to other sites can take some time to load if there are many on a page. Technology is changing rapidly and I'm doing all I can to try to stay on top of it but it ain't easy.... Glad I was able to help you! Best regards,
  22. Well, I'm sure SweetFX is compatible and I didn't mean to say it is completely incompatible. Only a few people have been successful in getting it to work for them (me included). So, your error is related to some sort of incompatibility or wrong setting somewhere in the profile. We have had so many crashes related to SweetFX and the ENBSeries modules. They are hacks. They were not made specifically for FSX or P3D. They work well in some other programs but FSX w/DX10 or even just FSX has issues. Some graphics experts have been successful and I applaud their ability to make it work. We have a SweetFSX forum here on AVSIM so I would suggest checking it out if you have not already. I have a lot of discussions in the AVSIM CTD Guide about the SweetFX hack. It has a list of all of the files installed in the main folder of FSX. So, if you need to remove them to make FSX work, then you will need to visit the CTD Guide. Just removing the .ini file will not fix it as every module like the d3d9.dll in the FSX main folder is loaded and the sim will crash if it does not like the way the file was hacked. Best regards,
  23. Hi Ray, I went in the Cheadle Weather forums (at the link you provided) and copied your image in one of the forums and then pasted it here. It's the upper one. Is that okay? If so, then you can remove the bottom one. Best regards, Jim
  24. Fully understand your investment. Your comments/topics get seen by many as most of our members use the "Recently Discussed Forum Topics". Not a big thing. Just that many do not like to see the same topic posted in several forums. The Menus.dll error is a new one to me but my searches indicate it happened back in the days of P3Dv1 and then LM released an update to fix the bug. When individuals have issues which are rare, I have to look at why this is happening to just one or two individuals and not everyone who has the product installed. So that's why I mentioned the EMT (Estonia Migration Tool). Many people are porting their installations from FSX to P3D to save some dollars and P3D is a different animal from FSX. It is mostly the same sim but with some bug fixes and updates which could not be made with FSX. I wish I had the expertise to find a solution for your problem with the menus.dll error. I hate doing it but I strongly suggest you search the P3D forums. I found 19 forum pages of discussions regarding this error on LM - http://www.prepar3d.com/forum/search.php?keywords=menus.dll&fid%5B0%5D=6312. The most recent discussions are in regards to the latest P3D version. Perhaps you will see something there that will relate to your situation and they have a fix. Again, not everyone is getting this crash and it has been rare when someone reported it here. Best regards,
×
×
  • Create New...