FalconAF

Members
  • Content count

    690
  • Joined

  • Last visited

About FalconAF

  • Rank
    Member

Contact Methods

  • ICQ
    0

Recent Profile Visitors

2,587 profile views
  1. 1. According to the downloads page for it, it says it is for P3D 4.0, 4.1, and 4.2. Sooooooo..........(hmmm) 2. Download the new file. Run it. It's an .exe that will place the FlyInsideP3D4.exe file (and another "Annotator" file) in your root P3D directory. It will overwrite (replace) any previous version you have. You may have to go reset the program's bindings again when you start P3D using it (maybe not too). 3. I saw improvements on my system. You may or may not, just like any other user. Flight sims are notoriously end user's system dependent, and will "work" only as well as the computer they are running on.
  2. Rob got it right. There are plenty of users who have been flight simming for years and decades and know how to keep their computers "healthy" and running correctly. No P3D upgrade is going to fix an issue being caused by a faulty computer to begin with. Updating P3D from 4.1 to 4.2 should not be "scary" because you are afraid you will break something. If you are scared about doing it, you simply don't understand how it is designed to work. You can ALWAYS "go back" to a previous Client by deleting the new Client upgrade if it "causes you problems" and re-installing the previous Client version. You should at least TRY it to see if it WILL improve performance for YOU. The Content and Scenery upgrades require that you understand a bit more about things that could get corrupted you already have installed, but again that is a knowledge and understanding issue. If you don't understand what each of the 3 .msi files WILL do to your sim, you need to take the time to LEARN it. I cringe every time I see a post by someone who says' "Well I'm just gonna do a complete reinstall of my entire Windows OS and then the same with P3D. That's the only way it works for me!" That post is a true indication of how much the user does NOT know about how to keep their computer as a whole, let alone P3D, running correctly. Respectfully submitted. Been doing it for 3 decades now (along with professional IT for over 26 years) and have never had to reinstall my complete OS to do a flight sim upgrade.
  3. If the winds are "calm", it will pick the LOWEST NUMBERED available runway for takeoffs and landings. Doesn't matter what direction the calm wind is coming from. This has always been an issue in FSX and exists yet in P3D. It creates totally unrealistic traffic flows at airports that have "preferred" takeoff and landing runway configurations, like KLAS Las Vegas. At McCarran here, until the tailwind component reaches about 10 kts, runways 26R/26L and 19L/19R will be used in the real world. But in the sims, with a "calm" wind the ATC is gonna have everybody using the 8's and 1's (assuming you are using a "crosswind runway" AFCAD that will use multiple runways...if not, everybody is using the 1's or 8's only, depending on the AFCAD file). Totally *ss-backwards from the real world, but 8 is less than 26 and 1 is less than 19, so those are the sim's "calm wind" runways. A savvy AFCAD developer can alleviate some of this at airports where they can close runways for takeoff/landings in the AFCAD, but then THAT creates a new problem when the winds WOULD make those closed runways the operative ones. So it makes TOTAL SENSE to have your weather engine running before the scenario loads, If you don't, as an example at KLAS if the sim's weather is "calm winds" as soon as the scenario loads, ATC is gonna start sending everybody to the 8's for takeoff. Then if AFTER your weather engine updates the winds enough to make ATC WANT to use the 26's, you will already have a goat-rope of airplanes taxiing to the 8's and it will take ATC forever to change issuing taxi's to the 26's instead. And you'll already also have spawned AI headed for landings on the 8's too. Start your weather engine first, then start P3D. It will set the "real" winds direction and speed as soon as the scenario loads, BEFORE ATC can start using "calm wind" runways (assuming of course the "real winds speeds" are higher than the sim's default "calm" wind speed).
  4. If you are running Windows you can open Task Manager, go to the Performance tab, then on the bottom select Open Resource Monitor. Then start P3D. If you know what to look for (how to use it) it will show you what is happening while your screen is black before you see the P3D logo. Jay's 15 seconds is about what I get now too, and I have a high-end system. Nothing "bad" is happening. It's just the way P3D starts depending on your own computer setup.
  5. Either way works. But if you start AS first it will begin it's first weather update immediately after the scenario loads. That can prevent YOU causing a problem by you manually interrupting something like the initial loading of a complex aircraft like a PMDG. While the PMDG aircraft is initializing, you aren't supposed to be pressing any keys on your keyboard, playing with the mouse or joystick, etc. But if you loaded AS first, it will then automatically start it's weather update (you don't have to manually "start" it) without interfering with the PMDG initialization. In many cases, they will both finish at just about the same time, and you are ready to go then. NOTE: If you are using REX SkyForce with AS, start SkyForce first, then AS, then P3D. Normally you will want to start P3D last, but there are some exceptions, like if you use Radar Contact for ATC, you would start that AFTER loading your flight in P3D.
  6. Are you using the Single Pass rendering mode? If not, can you try it and report what happens? I want to use Single Pass, but as Thiago stated, it doesn't seem to work with Oculus' recommended driver version.
  7. OK, I gotta ask this, and see what the users here have/haven't experienced because of it. There is a conflict between what LM is saying and what is shown on the main Oculus site in big red letters. 1. LM is saying you need the LATEST graphics drivers to use the VR improvements in P3D v4.2 2. See the big red notice on the top of the Oculus site in this link: https://support.oculus.com/?locale=en_US&ref=oculus-pc-app Oculus says any NVidia drivers after v388.59 "may cause problems" and you shouldn't use them with the Rift. What's everyone's take on this so far? Are you using any NVidia drivers newer than 388.59 with the Rift in P3D 4.2? If you are using 388.59 as Oculus recommends, does it appear the new P3D 4.2 VR "updates" are working OK?
  8. Regardless of what any "real time" runway report you see will tell you (like Flightradar, LiveATC.net, or even ActiveSky), if the winds in the simulator are "calm" the sim is going to use the lowest numbered runway(s) available in many cases, regardless of the wind direction in the sim. This has always happened in FSX and still does in P3D. A prime example is someplace like KLAS (Las Vegas) where their are runways 8L/8R - 26L/26R with 1L/1R and 19L/19R. In the real world here (at KLAS) until the tailwind component gets to be 10kts or greater, the "active runways" will be the 26's and the 19's. But in FSX and P3D, as soon as there is ANY wind from the east, even just a "calm" wind, the runways used will be the 8's and 1's, which is totally bogus here. It takes an act of God out here at McCarran before ATC will use the 8's for takeoffs or landings, but FSX and P3D will use them all the time if there is a "calm" 3 knot wind from the east. So sometimes you just have to go with the flow in the sim. The above happens regularly at large airports with many different runway configurations in FSX and P3D. But normally what I do in these cases is just disregard the ATC, whether it be the default ATC or even my Radar Contact. I will use the runways I know the real world would be using at whatever airport I am at. I don't care if ATC yells at me or not...it's not a "real world" life and death situation. Will you sometimes end up landing on a "real" runway with an aircraft taking off at you in the opposite direction? Let 'em. Have your crash detection turned off and run 'em over. Then after landing when the Critique Guy in Radar Contact gets the FSDO Guy to ream you a new butt, just laugh it off. Heck, it's fun listening to him yell at you every once in a while.
  9. From an earlier version of P3D's User's Manual. Scroll down and read the section about Terrain Mesh and the Tesselation slider http://www.prepar3d.com/SDKv2/LearningCenter/getting_started/options/display/scenery_settings.html Bottom line is still the same...if you increase a slider farther right than your computer hardware can handle, you will suffer the consequences. And how far is "too far" will be different for each user's computer depending on the hardware AND what other "stuff" (complex addons, etc) they are running with their own flight simulator.
  10. That's why I said "...MAY need to be the same too....". It can depend on the users flightsim configuration. With a lot of other addons that may ALSO be installed outside of the sim itself, a complete path name including the drive name "may" be needed or the other addons "may not" work anymore. Really...the OP said he was going to "copy my P3D over to it and name it the same letter...". That "may" work...or it "may" not. If you are going to copy an entire hard drive to another new drive, it just makes sense to ensure the drive is NAMED the same as the old one too. Windows may...or may not...care. But that doesn't mean a bunch of other applications on your computer may not care if they depend on linking to a FULL drive name path (drive name AND drive letter). And it can also prevent having obsolete entries in your Windows Registry after the copy too. Just sayin'. Wasn't criticizing anyone.
  11. The drive NAME may need to be the same too if you have named the current drive something special. The entire drive PATH will need to be the same as the current one, and the path includes the drive's name.
  12. As Dave said, it happens because of limited processing power. But the end user can also contribute to it happening by the type of addons they use and their simulator graphics display setting. On my "up to date" computer, I would never see any "late" popping of the terrain mesh using JUST the default P3Dv4 installation and settings. But after I add additional scenery areas (like an ORBX "full fat" region with more demanding graphics capabilities, including some areas with higher resolution terrain mesh), throw in a weather addon with 4096 cloud textures (and set my sim to display 4096 textures), max my graphics sliders to the right, and a plethora of other things, I can "make" it happen even if flying a low-and-slow GA like a Cessna 172. I'm just over-taxing my system's ability to keep up with everything I'm "demanding" it to display. Do all of the above and try to fly a complex PMDG aircraft, or even the P3D DEFAULT F22 over the scenery at low altitude and 450 knots hair-on-fire speed, and it's almost a guarantee there WILL be slow loading blurry ground textures with late loading "popping" terrain mesh...and that's assuming those files will EVER get a chance to load at a "high" resolution before I even pass over the area in question. And if you end up with THAT happening, the sim NEVER catches up to loading "clear" textures anymore...unless you PAUSE the sim and give it time to "catch up" for the LOD area nearest your airplane's current position. It becomes a vicious cycle once your sim gets "behind" in texture and terrain mesh loading.
  13. It may of may not be "the problem" for everybody, but I also have a 6700K with a GTX1080 and never had this problem UNTIL my NVidia GPU drivers updated themselves to the most current driver version. I rolled back the drivers to my previous "no problems" version and it solved it for me. The latest NVidia drivers contained "The Fix" for the recently identified CPU fiasco/security vulnerability, so if you roll back you won't have that "fix" anymore. But it's the only solution I found for now (short of maybe some of the other solutions mentioned here that might work for some people).
  14. There is a Level of Detail (LOD) "radius" of different areas around your aircraft that determines the "resolution" of the scenery you see. The closer to your aircraft, the higher the resolution displayed. This also applies to the "resolution" of Terrain Mesh...the part of the sim that produces elevation changes for hills, valleys, mountains, etc. It sounds like you are seeing the Terrain Mesh "kinda move" or "re-load" or "adjust itself" (all your words) as you are flying. The more distant scenery will be at a lower Terrain Mesh "resolution", and as you get closer to it the resolution will get "higher" and the sides of hills, valleys, etc will "pop" into place to present a more accurate elevation change of the closer scenery. Note that this "popping" will appear much closer (or farther) away depending on the ZOOM setting of the window being displayed on your screen. At a 70% zoom level, it would be happening at what would appear to be a farther distance from your aircraft. At a 100% (or higher) zoom level, it may look like it is happening right in front of your aircraft. (Your zoom level will also have the same effect on how close/far AUTOGEN looks like it is "popping" into your scenery display).
  15. And that is a main problem of threads like these. This thread is NOT P3Dv4 specific. It's in the ONLY Prepar3d forum section. And I've seen this happen countless times since Prepar3d has been released. People post "fixes" or "solutions" that work in SOME of the Prepar3d versions, but NOT others. Heck, I even see people making claims in these kind of threads, but they are using FSX Boxed or FSX:Steam and don't even have Prepar3d installed on their computer. AVSIM, you REALLY need to break down the P3D forums into SPECIFIC sub-forums for the different releases now. P3Dv2, P3Dv3, P3Dv4, etc, are NOT the same sims when it comes to what works or doesn't work with them. It is totally frustrating (and just plain confusing) for an AVSIM user to be reading "Prepar3d" topics that DON'T APPLY to their version of Prepar3d. Just a suggestion.