No problems running the 777 in the heaviest scenery available. Nor the NGX. Nor the Real Air products. In fact the only OOM I have ever experienced in FSX is with the Flysimware Lear 35.

 

----------------------------------------------------

 

FYI

As posted earlier, due to continued problems with the Flysimware Lear 35 with trim, OOM and autopilot issues, I applied for a refund. I was told that software does not qualify for refunds, and that the issue is with my sim only since very few people are having the problem. That is not the case of course, as numerous people have listed problems of OOM's, trim issues, etc.

 

This aircraft is the only FS add on that has ever caused me an OOM and so I seriously doubt it is my sim that's at fault. Others have said the same thing.

 

I also reported a trim gauge problem and Flyswimware said that I was the only one experiencing that. That also is not true as it was reported first a couple of days before I reported my issue. Thence, after they declared on the forum that I was the only one who was having the problem, others piped up to say they too were having an issue. Flysimware's answer to that was that the trim gauge should not show any indication in the air, only on the ground. As an avionics tech, I can tell you if that occurred in the air, the airplane would be grounded.

 

Further, the autopilot is incapable of holding an altitude at better than plus/minus 300 feet at 25,000 ft. This issue has not been reported by me at this point as it seems pointless to do so now.

 

This is the very last time I will deal with Flysimware. You decide for yourselves if you wish to deal with them yourselves, but definitely it's caveat emptor.

 

Since I am not getting a refund, I EXPECT to receive notices about updates, even if I choose not to reinstall the airplane.

 

Glenn

I never said the trim indicator will not work in the air. I said that when the trim is in the down position the pointer does not have a scale for below zero. So during a flight your not going to see an indication until you trim up into the positive numbers. I also mentioned you can use the tool tip to see that actual scale. have you ever seen a trim gauge that only indicates trim up. Our MU also has the same type of gauge. This is common as you do not need to see that your are -1.2 trim down. So there is nothing wrong with the gauge your just trying to read it when the gauge is below zero. 

 

I also stated we have not concluded our VAS usage and only a few customers have warnings and maybe 2 actually crash. Also our VAS is lower than the PMDG products with our patch. The article above that i posted states that scenery makes VAS grow over time not aircraft. And it states to not go and blame developers for OOM issues as this is a personal sim issue. Yes i agree if you do not use our patch and run heavy settings and fly over many payware scenery addons your going to be pushing your luck because it uses 500MB more. 

 

Remember when 99% of customers have no issues and 1% do then the cause of OOM is most likely their personal sim and the article explains this. If a product was released and 50% of customers were having crash issues there would be more threads than just this one and the news would be everywhere. And i still believe it's because we have not just 1 dimmer light we have 4 that use 2048 BMP textures. And this is what adds 500MB. But with the patch the VAS is the same average of our other aircraft. Most customers do not even use the patch and have no issues. So if you use the patch and still have issues this is not right! 

 

If 99% of customers are happy and no issues then i feel my product is made correctly and the article explains why some will always have issues. Still waiting for info from Bill.....

When we fixed our compass we fixed the direction of the animation and the value was correct. But this was not the mistake. We had the font on the texture backwards. So we are fixing this for V1.4

 

We also tied the voltage power to the spoiler so it will not function unless there is power.

You're making a few assumptions here. One is that everyone who has purchased it has installed it and test flown it. It's common for folks to do some pattern work and short flights while getting acquainted with a new model. According to this thread the OOM's don't occur until a flight length of approx. 250 miles. Not everyone emails or hangs out on forums. You're assuming that just because 99% haven't contacted you in one form or another that they aren't experiencing any problems. That's if the 99% number you quote is anywhere near accurate.

 

But let's say it is only 1% that are having issues. If it's such an insignificant number then so is 1% of the revenue you've received for this model. So for the 1% that can't get your model to work on their systems, do the right thing. Give them a refund.

Folks, OOM's are more an issue of scenery than aircraft. If you fly over very sparse areas you can test that yourself. Take the Learjet or any other aircraft that you get OOM's and fly it out over the ocean and see how far you can fly before getting a OOM, then fly the same aircraft over a dense area like Southern California and see how far you get. You decide! As both planes and scenery get more sophisticated they both use more VAS, as a consequence you need to turn down the scenery sliders because you can't have both!  And yes, as you fly farther the VAS builds up until it hits the OOM limit. Now P3Dv3.0 seems to do better at dumping VAS as it leaves the area then previous version.

 

Cheers

Martin

Folks, OOM's are more an issue of scenery than aircraft. If you fly over very sparse areas you can test that yourself. Take the Learjet or any other aircraft that you get OOM's and fly it out over the ocean and see how far you can fly before getting a OOM, then fly the same aircraft over a dense area like Southern California and see how far you get. You decide! As both planes and scenery get more sophisticated they both use more VAS, as a consequence you need to turn down the scenery sliders because you can't have both!  And yes, as you fly farther the VAS builds up until it hits the OOM limit. Now P3Dv3.0 seems to do better at dumping VAS as it leaves the area then previous version.

 

Cheers

Martin

Well said. 

 

If i felt that the aircraft had a major issue i would pull it off the market and give refunds. If someone has issues after flying 250NM and pushes the sim the max they need to move to P3D but not go ask a Company to refund them. I don't know how many times i have seen posts on PMDG crashed my sim on approach. PMDG does not refund those customers. Take the advice of the article i posted and this post here. But i will still wait for Bill to give me a final conclusion and go from there. Sorry to the few having issues on long flights but FSX is known to do this with complex aircraft and high settings.

Well said. 

 

If i felt that the aircraft had a major issue i would pull it off the market and give refunds. If someone has issues after flying 250NM and pushes the sim the max they need to move to P3D but not go ask a Company to refund them. I don't know how many times i have seen posts on PMDG crashed my sim on approach. PMDG does not refund those customers. Take the advice of the article i posted and this post here. But i will still wait for Bill to give me a final conclusion and go from there. Sorry to the few having issues on long flights but FSX is known to do this with complex aircraft and high settings.

 

 

Well said? You're kidding, right? Martin obviously hasn't read through all 8 pages of this thread. You continue to completely ignore the fact that the people having OOM's have stated that NO other models even those far more sophisticated than Flysimware's Lear have ever caused them any OOM's in any scenery they own regardless of complexity. Some stating they have never had an OOM issue in their entire history with FSX until your Lear came along.

 

So you're honestly recommending that someone dump their entire FSX installation, all their payware planes and scenery, buy P3D and start all over again just to accommodate your Lear? When NO OTHER MODELS are causing them OOM's? Does your product page say P3D is required?

 

I didn't know you worked for PMDG's customer service. Glad you know for a fact that PMDG has never provided a refund.

Yes your right Bob there must be an issue with our model for the customers who have high VAS and this model went over their limit. So i have been trying more testing to produce better results. The dimmer lights are the only new feature we have on this model and never had oom complaints before. So i am soaking up info as much as i can. And i am getting confused as articles and developers are saying it's their personal sim at the same time i agree with the customers here on the thread that they did not have this issue before. So i am agreeing our model is the cause for users with high VAS as other customers have no issues.

 

What i need is someone who is in fact having issues like Beaver to remove the cab "Flysimware_DIMMER" from the panel folder and do a test.

 

Other aircraft use this dimmer feature with no issues i think and i would hate to remove it. So i am improving the patch once again tonight.

 

I do not want anyone to have to buy a new sim i only said this because some have moved to P3D because they are wanting better results as they like to push the limits and FSX is not very friendly with VAS usage. Also it's common knowledge that software is not refundable so i woud expect PMDG does not refund for those who get a crash on approach. So no i do not work for them. i was being a bit sarcastic..

Improved VAS usage using V1.4....Please for those having issues please test the new patch. For those not having issues V1.4 also has improved.

 

V1.3

FSX default scenery + Flysimware Learjet 35A : 1,350 MB
FSX default scenery + Flysimware Learjet 35A + PATCH : 818 MB (This includes our patch we made for users who have issues)

 

V1.4 

FSX default scenery + Flysimware Learjet 35A : 1,180 MB
FSX default scenery + Flysimware Learjet 35A + PATCH : 700 MB (This includes our patch we made for users who have issues)

 

We have updated the hydraulic system. Auxiliary switch produces 875psi with engines off and both engines running produces 1,750psi. Also there is a reserve for an emergency and the flaps will work but it moves very slow.

 

I updated the fuel motive flow switches so the amber light is off when the fuel valve is open.

Folks, OOM's are more an issue of scenery than aircraft. If you fly over very sparse areas you can test that yourself. Take the Learjet or any other aircraft that you get OOM's and fly it out over the ocean and see how far you can fly before getting a OOM, then fly the same aircraft over a dense area like Southern California and see how far you get. You decide! As both planes and scenery get more sophisticated they both use more VAS, as a consequence you need to turn down the scenery sliders because you can't have both!  And yes, as you fly farther the VAS builds up until it hits the OOM limit. Now P3Dv3.0 seems to do better at dumping VAS as it leaves the area then previous version.

 

Cheers

Martin

 

Or, how about the TT ("Terrible Triangle" - Vancouver-Victoria-Seattle) - known to have some of the worst performance issues in FSX due to the amount of scenery there and the complexity of it, even in the base sim? Well Martin, I won't spend much time on this because this has been stated umpteen times already in previous posts of this thread (would be a good idea to actually research a topic before you write on it), but if what you are saying is true, then explain to me how I can do an instrument approach into CYVR to minimums employing the Autoland function of the PMDG 737NGX (one of the, if not THE most complex airplanes ever built for FSX) in the fully fat PNW region with a freeware 3rd party addon airport in CYVR, after having let down through clouds whose bases are at 200 ft AGL and that top out at 15,000 ft, with several further layers of CI starting at FL250 and topping out at FL330; all the while getting not much more than a few stutters as I break out under the overcast and all those approach lights, strobes and runway lights, not to mention the lights from the terminal suddenly bursting into view? All the while I have  Skyvector and ASN running on my second monitor in the background. And yes, I have done that many times. And that's there. Flying in Norway, while a fat region, is a FAR, FAR cry from the complexity of the scenario I just described. If you aren't getting an OOM there my friend, then it ain't the sim or your computer. Please research first. The last thing we need is more pot stirring here right now. Thank you.

 

Yes your right Bob there must be an issue with our model for the customers who have high VAS and this model went over their limit. So i have been trying more testing to produce better results. The dimmer lights are the only new feature we have on this model and never had oom complaints before. So i am soaking up info as much as i can. And i am getting confused as articles and developers are saying it's their personal sim at the same time i agree with the customers here on the thread that they did not have this issue before. So i am agreeing our model is the cause for users with high VAS as other customers have no issues.

 

What i need is someone who is in fact having issues like Beaver to remove the cab "Flysimware_DIMMER" from the panel folder and do a test.

 

Other aircraft use this dimmer feature with no issues i think and i would hate to remove it. So i am improving the patch once again tonight.

 

I do not want anyone to have to buy a new sim i only said this because some have moved to P3D because they are wanting better results as they like to push the limits and FSX is not very friendly with VAS usage. Also it's common knowledge that software is not refundable so i woud expect PMDG does not refund for those who get a crash on approach. So no i do not work for them. i was being a bit sarcastic..

 

 

OK, this is the first sign of hope for a resolution and contrition I have seen from the developer on this. Believe me, people get their backs up in a hurry if they are told they are one of a very few with a problem. We get left with the feeling that we don't count, and "too bad for you". You may not have said that out loud, but it's sure how it's come across. Thus my reason asking for a refund. Oh, and by the by? I have been offered refunds by 2 FS addon companies in the past. One has a policy of refunds if a product doesn't work, and one did it as a goodwill gesture. In the first case I took it because there was no hope of a resolution (and not through their or the developer's fault), and the other I declined it because I knew what I was getting before I bought it so I felt the responsibility was mine and they shouldn't have to pay for me "taking a chance".

 

OK, enough said on that. Yes, I will remove the dimmer switch CAB and install V1.4. Let's see how that goes (believe me, I really, really want to get this airplane working - it still has immense potential in my view). What I won't do though is go back to the base sim. It doesn't matter to me if it works in that because I won't ever be flying the base FSX anymore. Also though, in order for an experiment to be "controlled" you can't change too many parameters at the same time. Since everything else I have works in FSX as I have it set up now, I'll focus on the object that has the problems so I know where to look if things are going south on us. I will report back tonight (EST) on how the flight goes.

 

Thank you for this.

Beaver also try the new patch! This overall VAS is very low and i hope this did the trick! 

I didn't try that, but see here for my flight test report. Results as far as the OOM go were very positive, but please read the full report. Thanks.

I am having VAS OOM's as well. I don't have access to V 1.4 yet as I bought my L35 from Flightsim.com Pilot Shop. I ran a number of tests and like other users who have reported this issue, I can confirm that on most short range flights, there is no issue, evne with high end scenery in place for both airports. I did discover that most types of high end 3D ground lighting will eat up a good bit of VAS as well and depending on the aircraft model, OOM's are likely to occur. As a side note, I am able to use the MU-2 and C441 with night lighting and high level scenery without OOM's. Back to the Learjet, I did download and install the latest dimmer cab file and ran a day flight from ILM to FLL (with FLL being the high end FS Dream Team version). Using the FSX Scenery Configurator to disable all 3D ground lights and scenery not used. I had strictly a freeware version of ILM and FLL with Drzewiecki design's Miami scenery enabled. I was able to complete the flight to landing but during the rollout, an OOM happened. It's important to note that this was done during the day with no useage of the onboard aircraft lights other than the landing & taxi lights. On another test, I enabled various freeware photoreal Caribbean scenery and ran a flight from ILM to Barbados and other Islands. No OOM's occured but most of the flight was over open ocean.

 

Regarding other high end models with high end scenery, again using the FSX Scenery Configurator, I was able to run the ILM to FLL flight (including the Drzewiecki design's Miami scenery) with my Aerosoft A319 and PMDG 737NGX without OOM's.

I am having VAS OOM's as well. I don't have access to V 1.4 yet as I bought my L35 from Flightsim.com Pilot Shop. I ran a number of tests and like other users who have reported this issue, I can confirm that on most short range flights, there is no issue, evne with high end scenery in place for both airports. I did discover that most types of high end 3D ground lighting will eat up a good bit of VAS as well and depending on the aircraft model, OOM's are likely to occur. As a side note, I am able to use the MU-2 and C441 with night lighting and high level scenery without OOM's. Back to the Learjet, I did download and install the latest dimmer cab file and ran a day flight from ILM to FLL (with FLL being the high end FS Dream Team version). Using the FSX Scenery Configurator to disable all 3D ground lights and scenery not used. I had strictly a freeware version of ILM and FLL with Drzewiecki design's Miami scenery enabled. I was able to complete the flight to landing but during the rollout, an OOM happened. It's important to note that this was done during the day with no useage of the onboard aircraft lights other than the landing & taxi lights. On another test, I enabled various freeware photoreal Caribbean scenery and ran a flight from ILM to Barbados and other Islands. No OOM's occured but most of the flight was over open ocean.

 

Regarding other high end models with high end scenery, again using the FSX Scenery Configurator, I was able to run the ILM to FLL flight (including the Drzewiecki design's Miami scenery) with my Aerosoft A319 and PMDG 737NGX without OOM's.

Have you tried our patch? This will make the Lear less VAS than the MU-2B! See how this goes as Beaver has shown it is our dimmer lights which is a new feature that uses much more than our previous aircraft usage.

Yes, I did so before making the second set of test runs. There was an improvement but just after landing is when the OOM occurred,

Okay, just ran the same route once more ILM-FLL but this time I made two changes, I completely deleted the original dimmer cab file and dropped the new one in the proper locations, then I also disabled the Miami scenery which is a large plot of 3d and photo scenery to the south (in hopes of reducing the VAS footprint). I made it into FLL and parked, shut the engines down with no issues.

I will say, whatever the issue is with the VAS usage (related to the dimmer cab and/or whatever else may/or may not be causing it), there are clearly some sceneries which we know are not VAS friendly. Managing the unused scenery as well certainly helps.