Thanks FSPS for the new version 1.3!

The 1.3.1 patch was launched after only 2 days (wow, that's fast!).  It fixed the two most apparent bugs: GUI error message when FSX not ready yet and the AGL/MSL confusion.

Great to see you guys hard at work also for a P3D release. I hope LM "treats you right" so that you can benefit from your "real time tweaking" idea.

There were endless discussions on the P3D forum if something that I called "downstream tweaking" could be possible. You made it possible although LM sticked to the opinion that it would be impossible due to too many different PC setups out there...

Congratulations and thanks for making it possible to fly the PMDG T7 SP1B even on my "little" notebook...

 

 

Still couldn't see a difference between when it's off or on

 

It works...I can gain as much as 10 FPS at congested airports, and now,when used in conjunction with Duke's A.I. software...you can even gain 15 in some cases. That is simply amazing, to say the least.  The secret to this software...is the manual it comes with.  I'm not suggesting that you did not read it...but, I am mentioning for the express purpose of anybody else in general...you need to run this program, with the manual as your guide....

 

 

It works...I can gain as much as 10 FPS at congested airports, and now,when used in conjunction with Duke's A.I. software...you can even gain 15 in some cases. That is simply amazing, to say the least. The secret to this software...is the manual it comes with. I'm not suggesting that you did not read it...but, I am mentioning for the express purpose of anybody else in general...you need to run this program, with the manual as your guide....

 

Well, *grin* I started out like I usually do and didn't read it.  But when I wasn't seeing any effect I read through it and did what it said.  That's how I found out I needed to overclock.  Still...puzzling.   I was flying little complex Orbx airports and KRDD (also Orbx but bigger) with a fair amount of AI.  Weather ranged from slightly poor to fair.  The left gauge was solidly in the green...sometimes way up.  The bottom gauge was (if I remember) running about 30%.  The right gauge was bored...not moving much.  I was seeing a decrease in frames (not surprising since it had set a lower value than I typically use in the 'low' scenario.)  Still, there must be some benefit to that so I went with it.  Still, didn't see any benefit...at least not visually.  Tried the 'middle' setting too.  Anyway, while I'd like to figure it out, I'm not going to pay that much to find out if it *might* help.  I think they'd be better off with 20 days of demo than what they're doing.  It takes a while to sort this stuff out.  If it helps people will fall all over themselves to buy it given the vast number of hours we spend tweaking.  With 5 tries...all used in one day...I didn't have much time to investigate.

 

 

GUI error message when FSX not ready yet

Quoting myself this one goes out to FSPS:

Is it possible that this "effect" in v1.3.0 was caused by the FSX.cfg tweak

[Main]
DisablePreload=1

which disables the preloading of the selected default flight?

Just an idea and you solved it in v1.3.1 already anyway...

 

 

Well, *grin* I started out like I usually do and didn't read it.

 

Hi Gregg, well, all I can type...is that with F.A. 1.3 and the latest A.I. Opto from Duke....I have never had better FSX FPS performance.  I really didn't have a clue, as to how much (flight spawn) A.I. could consume, in system resources.  I do now!

 

Happy FSX Camper.

I think they'd be better off with 20 days of demo than what they're doing.  It takes a while to sort this stuff out.  If it helps people will fall all over themselves to buy it given the vast number of hours we spend tweaking.  With 5 tries...all used in one day...I didn't have much time to investigate.

 

I agree Gregg, I used all the 'tries' and then realised I had not had a fraction of the time I needed to fully understand and test the software. So, I contacted the developer and asked very politely if they would perhaps consider extending a further demo to me, they didn't reply and so off the back of all the good reports on the forum, I purchased a copy! Silly me, money down the drain :(

 

I sometimes wish I could share in all the fun that some of the guys rave about on the forum. You know, this fix, that fix, the 'magic bullet' for this and the 'magic bullet' for that. But it never seems to work out. Even with P3D, all the shouting and enthusiasm has fallen on deaf ears with me, as I have seen worse performance in many areas compared to FSX. Maybe I have the cloud of doom over me :unsure: :smile:

Rockcliffe,

 

Your not alone...fear not !! it did absolutely nothing for me either..again wish I could see the great results but alas no....there really is no magic bullet for FSX...it is old coding and without being re programmed it just cannot do what we all want it to do...

 

Even P3D has issues..

 

One day one day!!!

our not alone...fear not !! it did absolutely nothing for me either..again wish I could see the great results but alas no...

 

Interesting to say the least!   The first day it was released and made mention, I downloaded the trial copy, flew at about 1,500 feet around the ORBX Northern California  SP1 San Francisco Bay area, and normally where I would have (due to my high settings)  (and I think that is where some are seeing performance, and some, with settings low to mid...are not..) only about a clunking (FSX...) 5-12 FPS, after I read the manual and set the RTM trial to the recommended settings...I took the exact same flight, and my jaw dropped. I was at 18-22 FPS!  The graphics were not much changed, as I could see with a non-critical eye. I had smooth animation as well, right down to a spot where I did still dip to 10 FPS.  

 

I didn't need another second of flight....I shut down...sought out a seller, and did the deal.  I have never regretted that fact, since.  I now use as a duo FPS Increase software team,...FA 1.3 and Duke's latest A.I. Flight-Spawn Management build.  They have both on average kept me 10-12 FPS higher in any flight situation within FSX, then by not using either, or both of them.  After reading about a few user dissatisfaction posts...I personally believe that unless you normally ran with FSX pretty much full-bore open....where there would be such a visual and drastic change in FPS, due to your CPU/GPU loading of it...then some will come back here to say, "Nope, no change for me...nothing to write home about...".  I could understand this.  My simulation needs, are such that I require both FSX and P3D to run with every visual and atmospheric option, not only enabled, but to the max of its setting. If you do that...then most will see a dramatic improvement of  a figure for a mean-average FPS reading throughout the flight session. That has been my case from the start, with this program.  Adding in , as I said here...A.I. Flight-Spawn Management post purchase of F.A., has only increased the FPS leverage to my usage.

 

Mileage will vary, the same as the demand of each User of FSX.....in the settings menus, and levels thereof.....  That's the difference, I'm sure.... 

 

 

I didn't need another second of flight....I shut down...sought out a seller, and did the deal. I have never regretted that fact, since. I now use as a duo FPS Increase software team,...FA 1.3 and Duke's latest A.I. Flight-Spawn Management build. They have both on average kept me 10-12 FPS higher in any flight situation within FSX, then by not using either, or both of them. After reading about a few user dissatisfaction posts...I personally believe that unless you normally ran with FSX pretty much full-bore open....where there would be such a visual and drastic change in FPS, due to your CPU/GPU loading of it...then some will come back here to say, "Nope, no change for me...nothing to write home about...". I could understand this. My simulation needs, are such that I require both FSX and P3D to run with every visual and atmospheric option, not only enabled, but to the max of its setting. If you do that...then most will see a dramatic improvement of a figure for a mean-average FPS reading throughout the flight session. That has been my case from the start, with this program. Adding in , as I said here...A.I. Flight-Spawn Management post purchase of F.A., has only increased the FPS leverage to my usage.

 

Well, I overclocked too (only to 4.0 for now) and the gauges were doing their thing.  My settings are high.  Would overclocking more make it work better?  Dunno.  Some other change?  I'd have thought that having a target frame rate higher than you were getting might make it work.  Perhaps it has something to do with the way Orbx sets down scenery objects around their custom airports.  What is the magic potion that makes it work?  Since they don't say (perhaps, don't know) and we can't experiment then we're dead in the water.

@Gregg, 

when you will be able to test again  try with the Frame Limiter completely disabled. Some users reported positive results even using an external frame limiter, some others still struggle about it. 

 

We cannot confirm it or even able to reconstruct this in our systems, - technically there is no reason it wouldn't work , especially if the limit of the ext.limiter is too high like your case 58 - but you don't lose anything in trying...

 

 

A.I. Flight-Spawn Management

 

Which tool is that?

 

 

@Gregg,

when you will be able to test again try with the Frame Limiter completely disabled. Some users reported positive results even using an external frame limiter, some others still struggle about it.

 

I can't.  My 5 trials are over.  All used up in a single day of trying to get it to work.  You guys might consider that getting a system working with a tool like this might take folks longer.  A week or two.  Trust me, that's a lot of work, and if it did work, someone would be a fool not to get it after all that work.  I can respect the need to fight piracy but it's tough (for me) to validate the tool.

Which tool is that?

My name for Duke's offering, I think he calls it A.I. Optimizer.  I call it, for what it does....it sniffs out, and deletes any flights spawned by the A.I. engine, past the limit you dial in from your x/y.

 

So, if you are using Duke's program (thread in this and P3D's forum) then you already have what I reference.

Well I gave it a go on my Win XP machine and can confirm that it actually slowed everything down. Yes it killed FPS. Switched it off returned to normal FSX working and back to my higher FPS.

 

It doesn't do it for me I'm afraid.

 

Cheers, Michael.

Initially I agreed with those posters that found Fiber accelerator to be of little or no use. I too came close to removing it from my system. However thinking about it I wondered if there was a clue in FIBER as part of the name.

 

A tweak than many use is Fiber_Frame_Time _Fraction=*.*  Could setting this aggressively to improve fps prevent FA from operating correctly? So I removed the entry from the fsx.cfg, fired up FSX and FA and following the instruction manual FA performed on my system as the developers claimed. And textures were sharper than ever before.

 

I have set 30fps in fsx, 24fps lower rate in FA with 30fps as the middle rate. The AGL is set at 10,000 ft and 40000 ft. The latter figure to ensure that FA is always operating. Important for me as Active Sky Next often throws storms at altitude or overcasts and FA does the job of keeping up the frame rates.

 

Could I suggest that those people who cannot get it to work and have the FFT Fraction tweak in their cfg - try it without. You never know it may work for you too.

 

Martin