cvearl

I bought her to! Great bird. I love her in RL and in FSX. Also works in P3Dv2 as well. In FSX I installed the RXP 430 and used the linkgps feature so the magenta line is displayed on the 430's in the VC. Pop up the 430 for the RNAV approaches. Great plane. Going to be a favorite. Might jam the RXP 430's into the panel if it will let me like I did with the F33A. I love Beach aircraft. What scenery was that you used in the screens? Charles.

In the screenshots at REX website there is a little 2 seater plane pictured. Anyone know what that plane is and where to get it? It kind of caught my eye! Charles.

I confirmed 13.12 works fine in DX9 and 10. C.

13.4 is great with FSX. Lets remember... FSX is 7 years old. That driver is less than a year I think. Now. If you were later to go to DX10 or P3Dv2 DX11 version of the sim. Then the newest driver might help in that regard. The latest driver is 13.12 and was just released. If anyone is going to switch, always follow the instructions here... http://support.amd.com/en-us/kb-articles/Pages/GPU57RemoveOldGraphicsDrivers.aspx Charles.

They had to patch it as some textures were not overwritten... http://www.orbxsystems.com/forum/topic/69629-ftx-global-120-patch/ C.

Here's looking at you! Check out this flight around CYVR PNW (hacked into P3Dv2). Autogen thick and lush as as far as the eye can see. It is there before it reaches the limits of my view horizon. It's not hard to see what it's eating 2.5 GB Video memory. Makes me wonder how much my FPS will be if I get a GTX780 or the slightly cheaper R9 290 which are both about 70% more powerful than this 7970 (now known as an R9 280X).

To be honest... In this comparison, there is 3 times the autogen in the P3D shot and HDR is enabled. Now... you COULD do the butter spread thin approach and drop the density sliders down just a tick right? Then the fps would be in the same "zone" of performance. So less dense but drawn further out so you dont see clumps of houses and trees popping up 1 mile out which is a hallmark of FSX. But I would prefer to grab a faster video card and embrace the extra scenery. Both options are there. Charles.

Hey don't get me wrong. I like the Autogen in P3Dv2 and I am willing to spend a few fps (and bucks on a more powerful card) to get it! Sadly it will be a year before P3D is usable full time for me. I am waiting for all the ORBX stuff to have Native installers. Need more natives in my scenery! LOL I mean look how hairy P3Dv2 scenery can be! Love that autogen. As for Photoreal? I do alot of my flying below 3000 feet AGL and I have yet to find scenery in the photoreal catagory that makes my day. That said... If I was more into high flying and bought some well blended big airports, I would be a photoreal ######. But down low... I need trees and houses man. Love your racing stuff by the way. I used to race alot on iracing.com with a FFB steeringwheel until FSX stole all my time. Always wanted to do it in real life. No tracks near me though so no use getting into the costs associated with it. Charles.

Good idea! Here you go. Native P3D plane. Look at the very last two shots. the whole point of the thread. Look at the very last two shots paying close attention to the number of houses and trees are on the ground just beyond the Golf course and just North of the river almost into downtown Seattle. Not about "better or worse" I guess but an explanation of WHY fps seem lower in P3Dv2 than FSX under same conditions. P3Dv2 is doing more work (weather or not that is more or less pleasing to you while you "fly"). The framerates are displayed in the top left corner in case you missed it. And ya. I fly and I don't watch the fps counter. This was an academic comparison in the context of different rendering engines we have available in our sims. Charles.

Lets get ready to rumble!!!!! Never in the history of Microsoft Flight Simulator 10 have we had so many graphic choices. DX9, DX10 with the DX10 Fixer and now P3Dv2 DX11. Wow. So I got to thinking it was time for a showdown. This is the same scenery loaded (FTXGlobal 1.2), same plane (Duke v2.0), same time and season (Summer Day), same weather (Cold Fronts) and same airport (KSEA) with P3Dv2 dialed as closely to the same settings I have for FSX (DX9 and 10 have the exact same settings and I have all shadows turned off in P3D although some cockpit shadows only cost a few fps). As you look at these you will notice that P3Dv2 has lower fps. But looking at the last comparison, you will see why. Autogen sprite draw distance. It will be grossly evident that P3Dv2 is drawing up to 3 times the autogen sprites. Not in density but in distance from the plane. The AG radius is at least 3 times if not more further out. You can see below the plane that the density is the same but as you go further out away from the plane, a huge reduction in the number of objects drawn in FSX. This, IMO, accounts for the lower fps in P3Dv2. NOTE: You may also notice that some of the objects at KSEA are missing in P3D even though all are using FTXG 1.2. Ah well. Settings are simple. 4xSSAA 16xAF with vsync on but fps unlimited. Scenery Complexity Very Dense and Autgen at Dense, cloud density high and 70 miles, water Low2x. LOD radius 4.5 ect... so on and so fourth. Very few changes to FSX.CFG. Highmemfix and wideviewaspect and that's it.

This is for those that have EZCA+TIR already in their FSX install. It also requires the Estonia Migration Tool. Is there other ways of doing this? Sure. Fill your boots. This is how I did it. OK so what I did was this... 1. Copied the BETA EZCA P3Dv2 executable (EZCA.EXE) from here (link below) into "C:\Program Files (x86)\EZCA" folder after backing up the original of course. http://www.simforums.com/forums/ezdok-and-prepar3d_topic40274_post236510.html#236510 2. The I opened the "EXE.XML" file in my "C:\Users\Charles\AppData\Roaming\Microsoft\FSX" (Right Click and Edit) and copied these lines from it... <Name>EZdok camera addon</Name> <Disabled>false</Disabled> <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path> And pasted them into the <Launch.Addon> section of the same filename (again Right Click Edit the file) in "C:\Users\Charles\AppData\Roaming\Lockheed Martin\Prepar3D v2" NOTE: to see your AppData folder you have to enable "Show hidden Files, Folders and Drives" in your Windows Options. Google it if you are not sure what I am saying. Otherwise the folders are invisible and you cannot reach them. So it now looks like this in the EXE.XML file in the Prepar3D v2 folder. <?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>EZdok camera addon</Name> <Disabled>false</Disabled> <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path> </Launch.Addon> </SimBase.Document> 3. Then I ran Estonia Migration Tool and activated virtual FSX. This is migration state for the tool fooling installers into thinking the P3D folder is FSX. 4. Ran the EZCA Config tool and clicked Configure FSX (really doing the P3D folder planes) 5. Then in the Migration Tool I de-activated virtual FSX so FSX will work normally again. TEST: Fired up my P3Dv2 and lo and behold... EZCA and my TrackIR work exactly as FSX. My cameras are working from FSX without copying anything over anywhere. NOTE: one thing I did with P3D to make it match FSX controls settings (keybindings and so on) really fast was I copied over Standard.XML from C:\Users\Charles\AppData\Roaming\Microsoft\FSX\Controls into C:\Users\Charles\AppData\Roaming\Lockheed Martin\Prepar3D v2\Controls... I always make backups first. Since I have 3 or 4 of the same Carenado and RealAir planes ported over to P3D, I was able to check if all my Cameras from FSX were there and they were. Now I still stand by my recommendation that LM just write a script to a key that takes the current EYEPOINT coordinates and inject them into the camera file for the plane you are currently in so that people can adjust and save the default pilot view (most important and used view of all). It would be simple I bet for someone smarter than me and it would prevent people from having to worry about workarounds and other crap like this. Charles.

Finally. Now I can leave the insane asylum. I am been reporting this since months ago. And.... Everyone will be glad to know that it is specifically ORBX Car headlights in their region scenery's and can only be seen late at night. In the distance. Even the cars on the roads do it. Paparazzi on motorcycles! Now.. Here's the clincher... P3Dv2 has the same problem. I installed PNW SP5 in it with the Estonia Migration tool into P3Dv2 tonight and did some major night flying all over Vancouver area and it does the exact same effect! It is confirmed. DX10 and 11 no like the ORBX Headlights. Damn... I wish LH would fix it like you did Steve. Nice work on the patch brother! Charles.

This comes with a grain of salt. No matter what setting I use, I cannot match nVidia DX9 FSX 8xS+4xSGSS for sharpness and shimmer elimination. Closest I can get with ATI is 8xSSAA and that is only usable in DX9 for me. In P3Dv2, 8xAA set in game combined with forced SSAA in the driver results in low to mid 20 fps range and not as smooth as going 4xAA in the game setting. Charles.

This is FSX DX9 at about the same settings and situation and using ORBX PNW region and setting my driver to 8xSSAA and 16xAF

Purely reference only for those discussions centering around P3D VAS usage when you add FTX Global. I see almost no change after installing Global. Charles.

Standard FSX DX9 with 8xSSAA roughly same settings as the rest of the tests in the first screenshot. The rest are P3D.

Just out of interest sake.

Thats silly. Just get this. http://www.rexlatitude.com/Home/

Well I plan on installing this here in a bit and I guess I will see what VAS is at default first and then with Global 1.2 installed. Will report back. C.

Is there a link to this "white lights" thing? I would like to test that. I refrained from using P3Dv2 until this 1.20 for Global released. Now I am going to do some more test flights. My 7970 really seems to like it. Sort of. Still the most glaring omission for me seems to be RXPGNS but hey. What ya gonna do. Charles.

P3D V2 ?

GTX770 is the GTX680 re-branded to fill that price point in the 700 lineup. AMD did the same thing... Released an R9 290 and 290X and needed a 280X so they tweaked and re-released the 7970GHz edition as the 280X. The R9 280X was released at $329 but sold out everywhere. I see prices are now over $349 and up. Sheesh. The GTX770 Superclocked editions (about the same performance) is in that range as well. There is stock everywhere for those. AMD did not count on the bitminers buying up all the R9 series cards so quickly. /sigh Anyway. The 770 at ~$360 is a heluva sweet deal rebranded 680 or not! Charles.

Well in DX9 you can get vsync with a line... [GRAPHICS] ForceFullScreenVSync=1 http://fsxtimes.wordpress.com/2011/08/14/fsx-cfg-verticalsync/ So there. You can fly FSX in DX9. Without RadeonPro you can lock fps in FSX to 30. Also in DX9 8xSSAA set in CCC works great. Especially that card! Now for DX10 or RadeonPro crashing FSX... There are a few FSX addons that crash with RadeonPro. Ground Traffic Extreme or some such thing. Sweet FX in some methods SMAA Antiailiasing setting in RadeonPro with DX10 ENB Series Mod for HDR lighting in DX9 mode Setting Direct X based Tripple buffering. Is your FSX stock or have you added a bunch of stuff? You need driver version 13.4 Beta 9.5 http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspx Also might want to make sure you have antivirus disabled as a test? Make sure you have UAC (User Access Control) disabled Just off the top of my head. Maybe if you ask this guy for help he can shed light? http://www.radeonpro.info/2013/11/new-build-with-support-for-amd-radeon-r-series/ Charles. I wish I could edit the original post... Regarding artifacts in DX10 mode longer flights... To avoid artifacts disable the cloud shader in the fixer and set water in FSX no higher than 2xLow and run with 4xAA instead of 8X C.

Dont have an nVidia card to compare. But I guess I would say that fps is 30 - 40 fps in most of those shots and most are at KSEA. I am waiting for Vector and Global to be installed in both FSX and P3D and then I can compare with fps screenshots. nvidia SGSS is a tick better looking than SSAA though IMO. Not enough so that I would switch just for that reason. Sadly 8xSSAA is not usable in P3D for me. :( Stutters. 4xSSAA looks good nuff I guess. Charles.

Thanks