Stewart Hobson
-
Posts
5,024 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Stewart Hobson
-
-
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.
-
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
-
1
-
-
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!
-
Installing PNW would solve the problem, it seems to me. Why the heartburn over Vector when PNW does the job?
-
Follow-up to my post above: FSDT's installers assume that the install location of your last FSDT install is the same one you would like to use for the current install which you are planning, regardless if it is for FSX or P3D. The trick to installing new FSDT scenery (or those installers that will use the new add-on.xml method) is to change the default location at the very beginning of the installation. Otherwise the FSDT installer will assume the install location will be the same as the (previous) FSX install location. That appears to have been my problem.
-
On 6/6/2017 at 7:03 PM, lonewulf47 said:
There is no need to move the entire documents folder. Alternatively you can also create an own folder for all add-ons on any other drive. If you happen to use an installer that supports the new system, just point the install to this folder. The installers using the "new" system I have found so far are from FSDreamTeam and FlightBeam. All other "P3D V4 compatible installers" I have seen so far still use the traditional system with an entry in the scenery.cfg.
Oskar
Perhaps someone can explain why FSDreamTeam and FlightBeam install their necessary airport files on my F: drive, the one I use for FSX, while the add-on.xml folder is correctly located in the Documents file on my C: drive? If I were to finally delete FSX, all those files used for FSDT and FB's airports would be lost. Why is their installer installing that stuff on the F: drive and not outside the P3D directory on my P: drive? It makes no sense to me. I suspect it might have to do with the fact I have those airports installed in FSX, but I can't be sure. No other 3rd party company installs their airports on the F: drive, btw.
-
Nick, Is there a performance hit with the light splashes turned on? Would this be why one would turn off the "New night lights"? To this viewer, it certainly looks better with them turned on.
-
12 minutes ago, Jack Sawyer said:
Thanks Stew! Does it seem to you that without ticking that box there are many more lights? Did they do this for performance reasons?
Hi, Jack. I haven't checked it out yet. I followed the directions and ticked the box after I installed the regions. Performance reasons? I don't really know, but that would seem to make sense--double the lights and you suffer some performance issues. Clearly, the intent is to furnish the regions with the same high-quality night lighting that OpenLC NA has, or even something better.
-
2 hours ago, Jack Sawyer said:
Thanks Nick, the screenshots were very helpful, I had no idea.
Now, I have a question. If I fly around at night in the Southeast since there's no full fat region there, there's nothing more for me to do, no ticking or unticking of any boxes right?
Thanks.
That seems correct to me, Jack. No full fat region, no adjustment needed.
-
I wish I could help, but I dumped my ATI card last year in favor of Nvidia. The ATI card and DX10 didn't agree with one another unfortunately.
-
There are freeware and payware versions of SABA, all of which are fine.
-
Hmmm....interesting how the Google Earth image looks closer to your with Vector image...
That was my reaction, too!
-
I've found that whenever I add new scenery, especially a non-Orbx airport, it doesn't hurt to run the Fixer just in case you need to take into account that airport's new lighting effects, etc. The fixer will scan the new addition and make the changes if it's necessary.
Stew
-
Thanks, Stewart! The problem with this ORBX forum is that I can't edit an old post. I have "sticky" pages on other forums that allow me to do that. I'll see if I can wake up a mod here to edit it.
However - no matter what that post says, the [external] link will always point to the newest version.
Adam.
Thanks, Adam. That's always good to know.
-
The original guide - produced by Paul "PJ" Johnson was a great help for me in checking my DX10 FSX setup. However - he decided he could no longer spare the time to keep it updated, so with his blessing (and a sigh of relief, I suspect!), I've taken over.
The REVISED "How-to" Guide (v1.04 03 July 2014)
NOTE: This is very much an "on-going" guide, so keep checking for updates - either in this thread or on the NZFSIM site: DX10 Fixer "How-to" Guide: Related files
Adam.
Hi, Adam. May I suggest that you change the above date of the "How-to" Guide to the more recent November date? Just to let everybody know there's been an update. I see you've made some corrections!
-
Hello, Adam and Paul. Thanks for your replies. I haven't installed the full-blown DX10 fixer yet, only the last "small" fixer, the Shader release v3.2.3. But so far no problems. I wanted to see how the Shader release worked (it does) in clearing up some of those pesky problems with funny textures at dusk/dawn/night, progressive taxi, etc. I just finished a longish flight from Monterey to Reno with no artifacts or spiking or whatever, but really didn't expect to see them anyway. I will install the full-blown fixer in the next couple of days and let y'all know what happens. I did use some of the suggestions in the guide for tweaking CCC, where applicable, since my version of CCC isn't quite the same as illustrated in the Guide. But no matter, it all seemed to work. My video card is a Radeon 7790, btw; not a "burner" by any means, but I get consistent smooth flying, unless there is heavy cloud cover, most of the time at 15 fps to as high as 25 fps. I chose this card because it seemed to fit nicely with my AMD 4130 OCd to 4200 Mhz. Again, not a "burner" but the combination seems to handle FSX well enough. I fly all GA single or twin engine stuff, so nothing elaborate there and no strain on the system as well.
Cheers!
Stew
-
Hello, Adam. I'm reading through the "How-to" Guide and note that it advises using CCC versions 12.8 through 12.11, and that newer versions cause spiking "...for which no cure has been found other than use the old driver." I'm using CCC v14.9, the most up-to-date version, I believe. Is the Guide's advice about using versions 12.8-12.11 still valid? Should I go ahead and install the older version (along with RadeonPro, it seems) so that I can fully take advantage of the tips in the Guide and running Steve's DX10 Fixer? So far, I've found the guide to be very clear and methodical. Nice job!
Thanks in advance.
Stew
P3Dv4 going to background process
in PREPAR3D® V4.x Support Forum
Posted
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.