Jump to content

Stewart Hobson

Members
  • Posts

    5,024
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Stewart Hobson

  1. Hi, Doug. Thank you. Any opinion on when this function should be carried out? It sounds like it's a cure for a problematic scenery.cfg or the Add-ons.cfg. or the terrain.cfg. And will it possibly cure the terrain anomalies I mentioned in my post? Or is that the proper use of "Verify Files"? Stew
  2. Can someone remind me what this does and when one should do it? I'm noticing some terrain anomalies up in Alaska (PFJ or SAK) since upgrading P3D4.5 to version 4.5.14.34698. Thanks. Stew
  3. Thank you for the added information. It's a beautiful area up there in Idaho and your area of Boise. I enjoy flight simming to all those small airports in Idaho once in awhile. Cheers! Stew
  4. My version was for FSX originally (in 2014), and I just ported it over to P3D. Running v4.5hf2 and it looks ok. The only difference I've noticed is that the areas between the taxiways and the runways, those areas where you saw the depressions, are not green in my version. That may be because P3D has assigned different textures to those areas. Anyway, the scenery works for me as is, so I'm going to leave it alone. There may be differences in the city of Boise itself, but I haven't checked those.
  5. Interesting! I'm curious why my version of KBOI works as is, without a corrected AFCAD. How new or old is your version?
  6. Is your KBOI installed above all Orbx products? It is the case with my installation and I don't see the "canyons" you are seeing. The fact that you do not have Vector installed is not an issue, since CRM uses its own data.
  7. Thanks for the update, Chris. I know that's the case with many of us old farts!
  8. Exactly so, Chris. Crash detection has never been accurately represented in either FSX or P3D, as far as I know. It has made no sense to me that some folks insist on keeping crash detection enabled because "it contributes to the reality of the sim", when, in fact, it does not.
  9. What I and several other users of this airport have done is spawn on the runway and then use "slew" to move the airplane to where you want to spawn next time, then save the scenario. Any fixes that have been attempted in the past have been defeated by P3D in not recognizing the "old" parking spaces which were available in FSX.
  10. Thanks for this valuable information, Louis. Cheers!
  11. Ahh...never mind. This issue is mentioned in Ben's announcement regarding Orbx Central 4.0.10. Any and all changes will not be lost. Thanks!
  12. I have previously run the auto configuration tool and subsequently have run the tool manually to correct those airports added after the auto config tool was run, and saved all the corrections to a profile. Will that profile be saved when the new Vector is installed, or will I have to run the auto AEC again, thus losing that profile which was saved previously?
  13. There is a FreeMesh available--don't know the details, but several folks here use it and haven't had any issues. At any rate, NorCal has its own mesh, so I can't say what might be the problem. Also, it's not reasonable to suppose the four Orbx products you have mentioned are somehow in conflict with each other, so there is a conflict elsewhere, I would guess.
  14. Thanks for the tip, Sherm. You are correct--these two spreadsheets are easily saved as pdf files. Cheers! Stew
  15. FYI, the airport designation is correct in the release announcement, however. Stew
  16. No problem, Larry. Thanks again for all your work on the freeware airports. It's most appreciated. Some of those out-of-the-way little airports would ordinarily escape any notice were it not for the freeware packs. Thanks again! Stew
  17. @woodhick803 and Larry Isenor: Just a heads-up fellas. I'm in the process of adding the 04/19 Update to my Google Earth kmz library and have discovered that Carlyle Airport's designator should be CJQ3, not CJQ5, which is Arnes Airport next door in Alberta. Cheers! Love these freeware airports, btw! Stew
  18. Thanks, Sumdger, that's good to know. My SimStarter NG allows disabling any add-on.xml entry--it's difficult to know what additional software folks might have that would allow manipulating such add-ons. Still, I can't imagine how UT Live has anything to do with the op's issue. But anything is possible.
  19. Smudger, Probably not. The program is activated via an add-on.xml entry, unless you somehow deactivate it. Besides, I very much doubt UT Live is the culprit--it's fairly benign in its interaction with the sim.
  20. Sorry, Dani, I can't be of more help, since this has worked for me and I haven't had to try something else to get P3D to start. I will defer to someone else who might have a better idea what's going on. Stew
  21. I've had this happen a couple of times myself. Turning off the computer, then turning it on again and starting P3D fresh usually solves the problem. Good luck!
  22. Thanks, Scott. I missed the fact that I had already transferred the product and re-installed it with FTX Central.
  23. Doug, The transfer procedure isn't working. Perhaps the airfield isn't ready to be made an Orbx airfield? Stew Edit to add: KMBS isn't ready to transfer either, for those who might be wondering.
  24. Installing PNW would solve the problem, it seems to me. Why the heartburn over Vector when PNW does the job?
×
×
  • Create New...