Never say Never!

falcon409

falcon409

Moderator
Staff member
When I saw this, I had to post it. Actually it was 20fps higher than this, but that didn't stay long enough to capture it on the screenshot. If you can't read it, it says, "Frames/Sec.-68.8 (Unlimited)". Now I doubt that my browbeating of the Sim had anything to do with it suddenly jumping the fps up. The only things I've done since trashing it verbally and physically (I uninstalled it), was to move it from the C:/Program Files (x86) Folder to a separate drive and then run the "Bojote Tweak". To be fair, that fps didn't remain that high for long. By the time I had taxied out and took off it had settled at between 35 and 40fps (double what I had seen up to this point). Most all of my sliders are set right of center, a few are maxed and I'm not using a lot of "reflection". Texture size I left at 1024x1024, although moving it up a notch didn't seem to change anything. AI is minimal and Traffic is light. I am using TrackIR (TrackClipPro) and a registered version of FSUIPC. Beyond that, scenerywise I installed my Sherman Municipal and it looks terrific in P3D.

So, I've gotten back on my Meds, my Yoga Master will be here in the morning to work on some new relaxation/meditation exercises (JK Folks). . .and I'll continue to progress with P3D. Oh, also, the Runtime error has been fixed, not by LM, a remedy from another contributor in the P3D Forums.
 
Lionheart said:
Congrats!
Feels good to see such high frame rates, doesn't it.
Click to expand...
Indeed it does. For now, I'll continue with the base installation only and get a feel for where the settings should be for the best performance. Once that seems to settle in, then I'll slowly start moving things over from FSX (Only Native FSX). Much of my Ground and Environmental textures may have P3D installers by now, I'll have to check on that.

Update: A quick check shows that, at least for GEX, it will not be usable with P3D and UTX is going through some legal stuff to see if there's will be or not.
 
Last edited:
It took me a while to find the sweet spot too. In photoreal scenery with sliders about where you are I was seeing 30 FPS until I began tweaking. Performance went way up once I found the right setup. I've seen over 80, but lock 30 for normal flying.

Careful on the installs. I've been OK with aircraft using the migrator tools, but scenery can be edgy. PR with the P3D v2 SDK autogen is fine. Third party can cause problems. I re-installed V2 four times because of this. I'm waiting for the first patch from LM and the approved installers from third party before installing much more.

Glad you got the FPS up to your liking.
IMHO this is a great platform with a lot of possibility. It would be a shame to see you miss out on the fun.
 
gman5250 said:
It took me a while to find the sweet spot too. In photoreal scenery with sliders about where you are I was seeing 30 FPS until I began tweaking. Performance went way up once I found the right setup. I've seen over 80, but lock 30 for normal flying.
Click to expand...
Yep...there are improvements with ver2 that I'm being cautious about right now...inching them up a bit and then running the sim to see the effects on performance.

gman5250 said:
Careful on the installs. I've been OK with aircraft using the migrator tools, but scenery can be edgy. PR with the P3D v2 SDK autogen is fine. Third party can cause problems. I re-installed V2 four times because of this. I'm waiting for the first patch from LM and the approved installers from third party before installing much more.
Click to expand...
Is there a single tool that will migrate FSX Native aircraft? (If the developer hasn't yet done an updated installer).

gman5250 said:
Glad you got the FPS up to your liking.
IMHO this is a great platform with a lot of possibility. It would be a shame to see you miss out on the fun.
Click to expand...
I agree. . .I can get almost giddy at how smooth the performance is. . .and no stutters. Lovin' it.
 
falcon409 said:
Yep...there are improvements with ver2 that I'm being cautious about right now...inching them up a bit and then running the sim to see the effects on performance.
Click to expand...

ORBX has some shared texture names for trees which can really mess up autogen, so be careful. Many people have reinstalled because they brought over Addons that freaked out V2 and required a reinstall.

falcon409 said:
Is there a single tool that will migrate FSX Native aircraft? (If the developer hasn't yet done an updated installer).
Click to expand...

None that I know of. But with all the small components in some packages, I would either use the installer and see if it can install (be directed to) V2 or check with the developers to see when installers will be available for V2 users.



falcon409 said:
I agree. . .I can get almost giddy at how smooth the performance is. . .and no stutters. Lovin' it.
Click to expand...

One of the things that they improved, (part of the performance boost when redoing the code and putting the scenery cache in VRam) was that when you fast forward over the countryside, it should stay crisp and not go blurry. THe scenery 'also' will delete cache that is no longer needed, so as you go along in the countryside, the program is deleting used scenery cache instead of just building it up more and more till it crashes. Mind you, people are still getting crashes, but probably far less then they would in FSX with high sliders.
 
The default FSX planes are easy enough to port over.
All the effects files are already present in P3D so no need to copy them over, also all the gauges except EH101.dll and FA-18.dll so just copy over those two.
As for the planes a lot of the ones that are present are missing things like panel and sound folders as P3D is just using them as AI.
What I did was to first back up the planes in P3D then delete all the old FSX ones and copy over all the planes from FSX to P3D, they work great and as an added bonus are listed in P3D by there proper makes rather than Acme.
BTW if you cant find it the Airbus is in P3D as Commercial Airliner so dont forget to delete that one or you'll get conflicts when you start P3D after copying the planes over.
 
falcon409 said:
Is there a single tool that will migrate FSX Native aircraft?
Click to expand...

I've been doing the aircraft one by one. I've used the migrator tool, but will refrain with most installs until the manufacturers provide the V2 installers. I'm not comfortable with mixing the .cfg files and extra app data. Nothing against the migrator....it's a good tool, just my personal preference.

Most aircraft are working fine, but I've had issues with the Turbine Duke hopping. I've tweaked the contact points, center of gravity, compression stats in the .cfg with no results. Tweaked the mesh settings too...no joy. The devs will take care of that...I'll wait for it.

ORBX will sort out their issues working together with LM, so that will be straightened out soon. FTX Global is approved and the rest is coming. Most of the devs are having to re-do their airports so that will take a bit of time, but it is dependent on LM coming up with a patch also.

Looks like the transition will take a bit of work and time. I'm flying mostly my own PR w/autogen in V2. This works absolutely flawlessly with big FPS, even using high def PR and high sliders. This will keep me satisfied until the rest gets brought up to operating temp.
 
Last edited:
I'v been getting the plane hopping with some add ons too.
The only other problem I'v run into so far is if a plane has gauges that use the .gau extension they don't work and you get missing gauges, so only bother porting stuff that uses .dll or .cab for the gauges.
 
Dangerous Beans said:
The default FSX planes are easy enough to port over.
All the effects files are already present in P3D so no need to copy them over, also all the gauges except EH101.dll and FA-18.dll so just copy over those two.
As for the planes a lot of the ones that are present are missing things like panel and sound folders as P3D is just using them as AI.
What I did was to first back up the planes in P3D then delete all the old FSX ones and copy over all the planes from FSX to P3D, they work great and as an added bonus are listed in P3D by there proper makes rather than Acme.
BTW if you cant find it the Airbus is in P3D as Commercial Airliner so dont forget to delete that one or you'll get conflicts when you start P3D after copying the planes over.
Click to expand...

ah soo...... That's why mine came out all white, lol. Thanks for the heads up.



Bill
 
if you can make a copy, so if something goes wrong in any installation you have the copy of what works well.
No Retreat, No Surrender
 
Lionheart said:
ah soo...... That's why mine came out all white, lol. Thanks for the heads up.



Bill
Click to expand...

That reminds me I missed a step DOH!
LM fixed an old FSX bug where the planes would duplicate there paints
This bit takes a little longer to do but is worth it

In each plane copy the Texture folder and rename it Texture.0
Then in the aircraft.cfg find the paint that has texture= with no number after it and edit it to read texture=0
 
Dangerous Beans said:
In each plane copy the Texture folder and rename it Texture.0
Then in the aircraft.cfg find the paint that has texture= with no number after it and edit it to read texture=0
Click to expand...
That is an acceptable workaround for those aircraft who's developers never learned how to use the texture.cfg system properly... :frown-new:

The basic idea is that only "common textures" that are used by all liveries should be in the root ..\texture folder. All liveries should be in named or numbered ..\texture.number or ..\texture.name folders.

Whenever ..\texture.blue is loaded, the sim will look first in the ..\texture.blue folder and load the bitmaps. It will then parse the texture.cfg file and "fallback" to the ..\texture folder for the rest of the bitmaps.

However, developers had become used to using the root ..\texture folder "the old way" by placing their first livery's bitmaps there also, which quite frequently "broke" the fallback system by stubbornly using only that same livery, irrespective of the one actually chosen!
 
n4gix said:
That is an acceptable workaround for those aircraft who's developers never learned how to use the texture.cfg system properly... :frown-new:
Click to expand...

Yea I know but I wanted to keep it simple so anyone could do it and it will work just fine that way. For myself I get all OCD and clean out all unneeded files and suck like so its all neat and tidy :)
 
You must log in or register to reply here.
Back
Top