Sign in to follow this  
MadDogMan

Lear 35 OOM issue

Recommended Posts

Just purchased the Lear and absolutely loving it. Great job!  The only issue i have found so far doing some testing.

 

Day flight in ORBX area with things turned up. No issues at all.

 

The second i go to night and turn on ANY dimmers in the cockpit within mintues i start to run out of memory and eventually will crash.

 

Its for sure a issue with the plane and not my PC as i have Never had a OOM.

 

Otherwise i am really loving this plane! amazing job. I plan on flying this thing for many years to come.

 

My specs.

 

Windows 8.1 64bit

P3D 2.5

i7-4770 3.8

32 GB  Ram

GTX 760 3 GB

 

Yorik C

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Same here:

 

Testing in day situation. VAS when starting at e.g. PAYA is around 2.2Gb. When selecting the Lear, it drops to 1.1Gb in an instant. Looking around in cockpit and going outside  view, it drops to 800MB. Flying around for around 15-20 minutes it drops to 220MB with the dreaded beeping from my system and OOM.

 

Love the plane, but VAS usage is a bit on the heavy side.

 

System:
I7 3770 at 4.3Ghz
16MB RAM
Gforce GTX 970  4GBVRAM
Win10/FSX ACC

Share this post


Link to post

It's mentioned on their Facebook page.  They acknowledge that the approach to dimming lights they used, uses a ton of VAS.    If you don't use any of the dimmable lights, you'll never see an OOM (within reason).  But use of the dimmers puts you into risky territory.

 

I always tend to fly through the day so it doesn't directly bother me, but I think that in their striving to make the lighting really top notch, they may have comprimised stability a bit too much here, with the VAS load.

 

I think it may be useful for them to provide an option to remove the dimmable lighting, and have a more standardized approach.     - at least as an option.

Share this post


Link to post

There were two Learjet's in development which one are folks referring to here? I don't see any release news? I'm looking to buy something tonight, my wife is out of town :smile:

 

Cheers - Martin

Share this post


Link to post

I also like this aircraft but the dimmer lights should not use this much VAS. I have no issues in other aircraft with dimmers so I'm not sure why this one is different.

Share this post


Link to post

nice looking bird


Does the model have a very poor quality fs9 like VC? like there Cessna 441? I would buy it but They only have a few VC pictures and a bunch of external pictures.

Share this post


Link to post

Alright, Thanks for the replies. They for sure need to make some changes with the light usage or memory usage. Otherwise. LOVE it. Just flying around with the memory warning beeping.

Share this post


Link to post

Version 1.0 Not BETA just released! Prob solved?..  Nice work FlyJ

Share this post


Link to post

Can we keep this on topic please. Read e.g. AirdailyX for news regarding the relaese. It is of poor taste to ask about releases of other developers in a Flysimware forum in a support thread.

  • Upvote 1

Share this post


Link to post

It's mentioned on their Facebook page.  They acknowledge that the approach to dimming lights they used, uses a ton of VAS.    If you don't use any of the dimmable lights, you'll never see an OOM (within reason).  But use of the dimmers puts you into risky territory.

 

I always tend to fly through the day so it doesn't directly bother me, but I think that in their striving to make the lighting really top notch, they may have comprimised stability a bit too much here, with the VAS load.

 

I think it may be useful for them to provide an option to remove the dimmable lighting, and have a more standardized approach.     - at least as an option.

 

Yes, I'm seeing the same thing (OOM) and agree with your suggestion. For now though, you recommend not using any of the dimmers. I'm only seeing the row of switches by the pilot's elbow, but they all seem to be dimming switches (all are rheostats). The most forward one is actually marked "Dimmer". Is that the only switch you need to avoid, or do you need to avoid all switches in that bank? If so, are there "on/off" switches located elsewhere that I haven't found yet so you can still fly at night?

 

Many thanks for your help.

 

Glenn

Share this post


Link to post

Well, After the version 1.0 i still have pretty quick OOM issues with this plane. Never had one in my history of P3D or on this PC for almost 2 years. Hope they can get this fixed as i enjoy flying at night.

Share this post


Link to post

I had it with the beta, on a day flight from KMRY to KRDD(ORBX scenery). At this moment I had no lights on.

Share this post


Link to post

Yes, I'm seeing the same thing (OOM) and agree with your suggestion. For now though, you recommend not using any of the dimmers. I'm only seeing the row of switches by the pilot's elbow, but they all seem to be dimming switches (all are rheostats). The most forward one is actually marked "Dimmer". Is that the only switch you need to avoid, or do you need to avoid all switches in that bank? If so, are there "on/off" switches located elsewhere that I haven't found yet so you can still fly at night?

 

Many thanks for your help.

 

Glenn

 

Hi Glenn,

 

Honest answer is, I'm not sure.   I never used any internal lighting on my flights so far, and unfortunately I'm currently away on business and don't have access to my sim (always painful!).   I'll check when I'm home (unless someone else can chime in before).

 

 

I had it with the beta, on a day flight from KMRY to KRDD(ORBX scenery). At this moment I had no lights on.

 

This is a little worrying - perhaps the dimmable light coding is swallowing VAS resources even when passive.  If so, as much as I really love this aircraft, FSW really should provide at least an option to remove this lighting approach.    I get what they were trying to do (their Facebook page states they were trying to offer something truly unique and I respect that), but VAS can be a dealbreaker, and I'm worried for them that a lot of people will be put off this plane, reading these early reports of VAS problems.

Share this post


Link to post

I agree JYW it can be a dealbreaker :mad: furthermore some people are very relunctant(we saw that on AirDailyX recently)to buy Flysimware products ! Too bad the plane is just fantastic! I'm gonna make some training today at KSTS with V1 to see if it happens again!

  • Upvote 1

Share this post


Link to post

The plane is great, but it's a bit heavy on my system. Fps between 16/20 in default scenery. The Mu2 and the 441 runs above 40 fps at the same conditions.

Share this post


Link to post

In prepar3d v3 I,m not having that problem, as you said maybe they should try to offer a less memory ussage option with the cockpit lights for fsx users.

Share this post


Link to post

Too bad, what I feared happened, same OOM issue :mad: . I was making some circuits(The handling is pure joy )at KSTS(ORBX), ASN off, when after 3 circuits the problem happened! This is a serious issue that will penalyze this beautiful plane and need a serious investigation. 


At the moment it happened I had no cockpit lights on. I just used the landing lights for the final!

Share this post


Link to post

Thanks for your reply JYW.

 

This is rather worrying. Now, I did do a night flight early this morning that lasted about a half hour in an Orbx fat region and used all the lights EXCEPT I didn't touch the one marked "Dimmer" (or "Dimming" - I forget the exact verbage). I had no issues on this flight at all, with apparently a very fluid run (a little hard to tell as I couldn't see much of the ground). They have a file you can download from their site now to help reduce the VAS, which may or may not be part of V1.0, but it might be worth a try to install it anyway. Hopefully it is just the interior lighting and nothing else, but it sounds like it could be a little more than that if people are starting to see it in daylight.

 

One thing I do know that can really hit you is if you do a lot of "stepping outside" and then coming back in again. I know of simmers who have had crashes under fairly benign conditions by doing a lot of view swapping during a flight. For those having issues during the day, try limiting your view swapping and see how things go.

 

Incidentally, I'm in FSX Deluxe, in case that matters (and it might). Forgot to say that earlier.

 

By the by, I tried the landing lights today for the first time. Anybody know a good Opthamologist :P ? I think I may qualify for being legally blind now <LOL>.

 

PS - Pat - did you try the lights at all during your flight? You say you didn't have them on at the time of the crash, but once they've been on, they may "stick" in memory. I'm not certain of that, but when I had my OOM, mine weren't on at the time either, but they had been and I had been playing around quite a bit with the settings. Just a thought.

Share this post


Link to post

Hi BeaverDriver!

I just tried another time few minutes ago and the OOM shut down  FSX. I never had this problem before with lots of planes including Duke, Duke Turbine, Legacy, Lear 24, Piper Cheyenne II and so on...Anyway I never touched, for the time being the cockpit lights(I perform just day circuits and ILS). I used the external, bcn, strobes, landing lights. Where did you find on their site the file to download, I checked everywhere but found nothing?

Share this post


Link to post

Can you guys use the product page and send a message to Flysimware about this issue. I have a help ticket going and it seems they havent heard about any OOm issues at all besides mine. They need some feedback before they will make a fix . Just use the contact link on there website.

Since this is "unofficial" support our info isnt helping.

Share this post


Link to post

Can you guys use the product page and send a message to Flysimware about this issue. I have a help ticket going and it seems they havent heard about any OOm issues at all besides mine. They need some feedback before they will make a fix . Just use the contact link on there website.

Since this is "unofficial" support our info isnt helping.

 

That's a very good idea. I hope they told you this prior to yesterday Yorick, because I've been in touch with them as of yesterday and sent a follow-up message this morning on this matter (and the ADI which needs calibrating). They have (at least now) heard about this from more than just you, so if they are saying otherwise and you have been in touch with them since early yesterday, then you aren't getting accurate information. I agree - we need to make this known to them through their ticket system for sure, but let's keep up a dialogue here as well. It's not impossible (in fact, given Pat's info, it's probable) that this issue isn't necessarily the lights at all, but something behind the scenes. The more info we can pool here, the better the info we can give Flysimware via the ticket system which hopefully will lead to a faster and maybe more accurate fix.

 

@Pat - that's discouraging alright. It's the same for me. I've been flying FSX for almost 9 years now and this is the first OOM I've had as well. They definitely need to do some serious research into this, but I'm a little surprised they didn't see it on their machines as well. This doesn't sound like an isolated incident. Please keep flying it as much as possible if you can and document failures as you come across them. I'll do likewise, but I have to tell you, I have a bit of a short attention span for this sort of thing. If this is reasonably widespread, then they should have addressed this in beta and not after release. As one fellow admitted (quite correctly), something like this can really kill sales of an otherwise really great aircraft. Were this not a Lear 35, I might already have shelved it with a request for a refund. However, if Flysimware treats this seriously and listens to us, I'm quite willing to help in troubleshooting and give them a chance to find a permanent (and effective) fix for it. Let's hope that's forthcoming.

Share this post


Link to post

That's a very good idea. I hope they told you this prior to yesterday Yorick, because I've been in touch with them as of yesterday and sent a follow-up message this morning on this matter (and the ADI which needs calibrating). They have (at least now) heard about this from more than just you, so if they are saying otherwise and you have been in touch with them since early yesterday, then you aren't getting accurate information. I agree - we need to make this known to them through their ticket system for sure, but let's keep up a dialogue here as well. It's not impossible (in fact, given Pat's info, it's probable) that this issue isn't necessarily the lights at all, but something behind the scenes. The more info we can pool here, the better the info we can give Flysimware via the ticket system which hopefully will lead to a faster and maybe more accurate fix.

 

@Pat - that's discouraging alright. It's the same for me. I've been flying FSX for almost 9 years now and this is the first OOM I've had as well. They definitely need to do some serious research into this, but I'm a little surprised they didn't see it on their machines as well. This doesn't sound like an isolated incident. Please keep flying it as much as possible if you can and document failures as you come across them. I'll do likewise, but I have to tell you, I have a bit of a short attention span for this sort of thing. If this is reasonably widespread, then they should have addressed this in beta and not after release. As one fellow admitted (quite correctly), something like this can really kill sales of an otherwise really great aircraft. Were this not a Lear 35, I might already have shelved it with a request for a refund. However, if Flysimware treats this seriously and listens to us, I'm quite willing to help in troubleshooting and give them a chance to find a permanent (and effective) fix for it. Let's hope that's forthcoming.

I agree with you BeaverDriver! We have to insist(I sent a message to Flysimware as suggested wisely IPG1939), I'm pretty sure we are not alone with this problem! Too bad because this is otherwise a fantastic plane to fly.

 

Best regards

Share this post


Link to post

Check out the product page folks. There are already a couple of different fixes up to address the dimmer/VAS issue. One being the above mentioned lights on/off solution. Check them out and see how they work for you. But don't hesitate to email mark either. I think you will all find he is one of, if not the most, accessible developers in the business. He genuinely cares about you guys and your level of satisfaction. Take care.

 

 

http://flysimware.com/website/LEARJET_35A.html

Share this post


Link to post

Check out the product page folks. There are already a couple of different fixes up to address the dimmer/VAS issue. One being the above mentioned lights on/off solution. Check them out and see how they work for you. But don't hesitate to email mark either. I think you will all find he is one of, if not the most, accessible developers in the business. He genuinely cares about you guys and your level of satisfaction. Take care.

 

 

http://flysimware.com/website/LEARJET_35A.html

 

Oh for sure Matt. I have mentioned about the downloads available and will try them tonight, and I believe others have noted it as well.

 

I agree with you regarding Mark. If I didn't, I'd already be asking for a refund. I don't think anyone here is interested in hanging Flysimware over this :wink: . I don't know of anyone who doesn't like this plane (at least of those posted here), and who isn't willing to try and help solve this problem. This is a more systems-heavy airplane than most and there are bound to be oddball bugs because of that. I'll bet that if we solve this, the next release won't have this problem at all, so it's worth pursuing a fix for sure. I hope if Mark has read this thread, he's not interpreted anything here as being overly critical of Flysimware. That's certainly not my intent, and I don't believe it's anyone's intent here. Of one thing Flysimware can be sure - if the airplane wasn't worth fixing, we wouldn't be here :wink: .

 

Thanks Matt. I'm sure this will get resolved.

 

Glenn

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this