kentwerickson

This occurred to me, yet also strikes me as kind of a strange (non-standard) protocol; e.g., suppose all I want to do is download some liveries that I bypassed on a previous install? On the other hand, if I select nothing then it seems that what should happen is nothing; i.e., the installer simply terminates. At any rate, thanks for your suggestion.

Just checking in to see if the graphics resolution issue reported above had been investigated. Today it occurred to me to re-download the 340 from X-Aviation. However when I ran the installer the option to download the passenger version was disabled (ghosted out so I could not select it). Any idea what's going on with this? EDIT: While the passenger variant was not selected in the installer, it seems to have installed anyway. Also, upon first inspection this seems to have resolved the text resolution problem reported earlier; I will report back in the event that it reappears again in the future. While I'm at it, I wanted check the status on a couple of promised updates to the current v1.4.1 version for XP10. First, I am still hoping for an update (or patch) to fix the altimeter problem with the cargo variant (the primary altimeter stops incrementing at or above 10K feet, whereas the standby continues to record the correct altitude above 10K ft -- this seems to be a function that got broken in the v1.4.1 update, as it always worked fine for me prior to that update). Second is that I am rather hoping for a keyboard assignment for the nose wheel tiller on/off function (this can be quite difficult to locate and operate while keeping one's eyes on the runway during landing). I would be just as happy if the tiller control worked as toggle; i.e., on/off with a single mouse click (as opposed to click-and-drag). Finally there is the issue with the course selector (I've forgotten the details, but it's documented somewhere in this forum). Thanks.

Fair enough, and thanks for your help. In the meantime I will continue to play around with XP settings to see if other rendering options make a difference.

I notice that if I increase the texture resolution in XP (via rendering settings), the resolution of the console texture improves (but is still not as crisp as the passenger variant under the same settings).

Near as I can tell, yes. The file size itself (for both variants) shows 3,289 KB.

Not positive how to do this, but I opened both files with Paint.net. And under "Image/Resize.." it reports a resolution for both of 72.01 ppi (2048 x 2048). Does this sound about right?

Thanks Goran; I should have volunteered this from the start. Compare Exhibit A (cargo variant) to Exhibit B (passenger variant):

Hmm. I just noticed that the textures (graphics/text) on the transponder panel of the cargo variant of my Saab 340A (v1.4.1) are severely blurry (I'm still running XP10.51). As with the rest of the cockpit textures on the 340A, this looks great on both the passenger and airborne variants. But for some reason on the cargo variant these textures (only on the transponder panel) again seem to be severely degraded (to the point of being illegible). Can anyone offer an explanation and/or potential fix for this problem? Thanks.

Also something I requested a while back, for the same reason, and looking forward to having it! One more thing, while I'm at it. I notice that the GNS 530 "power on" button occasionally makes a "click" sound (which I like because of the audible feedback), but more often than not it makes no sound. Could you please look into this as well? Thanks. XP 10.51, Windows 10

Thanks for the update Goran. So far as I know, the altimeter issue was reported some time ago, and slated to be fixed in the next update. Also, as I recall, there is a problem with the NAV 2 bearing selector (among perhaps other reported bugs in this and other threads). Oh, and wait: I meant to say above that the altimeter issue (for me) occurs with the cargo variant, not the passenger variant.

Will we be seeing a 340A update for XP10 any time soon that fixes the bugs introduced in v1.4.1? In particular, the broken pilot's side altimeter in the passenger variant is problematic. I'd be happy with a downloadable patch, if an official update is not on the horizon. Thanks. While I'm at it, I wanted to ask if anyone knows why my 340A cruises in a conspicuously nose-up attitude (looks to me to be about 5-8 degrees). I've tried shifting the center of gravity forward, yet which doesn't seem to help much. For the same reason, this plane can be difficult to land without scraping the tail cone on the pavement (i.e., it always appears to be tail heavy). Maybe this is just the way the plane was designed to fly. But if someone could confirm I would be much obliged.

Great news; thanks very much.

Thanks Jim. Can you confirm (or deny) whether this update will be XP10-specific? I hope so, as I have not yet made the leap to XP11, and don't plan to anytime soon.

Attached are details related to my most recent failure. Log.txt

Ok, thanks. I'll do as you ask on the next occurrence. I sense that this might have something to do with mouse control. As the last time it happened I simultaneously lost mouse scroll wheel support. This kind of error dialog also sometimes appears when I monkey with the CRS-2 knob (though I read that this may be a known problem).

I've been pretty routinely seeing the error dialog below, typically at the end of a flight. Any ideas? (if necessary, I'll provide my XP log file next time this occurs, but in the meantime...???) LES Saab 340A v1.4.1, XP 10.51, Windows 10

Fair enough, and thanks for your reply.

This is somewhat of a nit, but I've meaning to ask why (or at least in my experience) storm/rain clouds often appear so small, and isolated? Specifically, I will often see a storm cloud against the backdrop of an otherwise crystal blue sky, yet which looks more like part of a small forest fire (see image below). I wonder if you couldn't somehow just artificially stretch out the cloud coverage in these situations to make it appear more realistic... Thanks in advance for considering the matter. SMP v4.5 (+RWC, +NOAA Weather), XP 10.51

As mentioned, I have noticed this problem (so far) only at KPHX (Phoenix AZ, MisterX6 scenery) and KTUS (Tuscon AZ). I tried again last night (both airports) and had no similar problems. However, the weather/cloud layer was also different (don't know if that matters). For now, I'll just write this off as a scenery issue and report back should it reoccur (if it does, I will be sure to immediately re-test with all third-party addons disabled). But thanks again, all the same, for your support.

Okay, thanks--if all else fails, I'll give this a try. Also, and perhaps importantly, I neglected to mention earlier that these gaps in cloud rendering (e.g., as shown in the image above) go away by adjusting my camera view ever so slightly (e.g., by panning up/down, or left/right, with my mouse). In other words, the anomaly is visible only from certain viewing angles. Don't know if this is indicative of a culprit, but seems worth mentioning.

Thanks for your reply. I have no idea what's causing the problem. I have HDR on, and XP rendering settings are nearly maxed out. I'm running an NVidia GT755M (2GB) graphics card with the latest drivers; not top-of-the line, but in my 3+ years of using it with XP 10 and SMP I've never experienced anything like this (not even in the 3 months or so since the last SMP update). If I have time this evening I will attempt to reproduce and attach the log file (my post here was just a first crack to see if this is a known problem with perhaps a known solution).

Any idea what's going on here? (see below). Image taken at KPHX, and I've only noticed this problem (so far) in Arizona (also at KTUS). SMP v4.5, NOAA, RWC, XP 10.51.

That's fine as long as I can eventually do this via key command; otherwise it's kind of distracting after touchdown trying to find and set the 3D tiller control (I'm all for realism in XP, but not at the cost of usability/safety to my passengers I misspoke here; I have the throttle levers mapped to an axis, but use two spare buttons for prop control (forward-a-bit/back-a-bit) on all my other payware aircraft. I am again unclear as to why assigning prop control to an axis should be the case. But having the button option is important because I don't have a super-fancy joystick with endless amounts of axis controls -- it has only enough axes to control the flight surfaces (pitch/roll/yaw) plus throttle. In any case, not a huge deal as on the 340 I've grown accustomed to doing this manually (using the mouse/3D levers). Thanks for your reply.

Can you please explain the tiller logic in greater detail (seems that there has been no update to the systems documentation that explains this)? It seems that the tiller automatically turns itself OFF at some point, either after takeoff or after landing. The observed problem is that if, after landing, I come to a stop (say at a runway crossing), I find that the tiller is OFF (yet I left it ON) and thus no nose wheel control. Also, can the tiller be mapped to a keyboard toggle (the 3D knob is not especially easy/intuitive to operate)? I tried the XP default "nose wheel steering toggle" data ref and that doesn't do it (also, I see no obvious choice within the LES/Saab 340a custom commands). A second question: I've never been able to control the prop levers with a joystick button (though I can control the throttle levers this way). Maybe I'm mapping the button to the wrong command, or maybe it's confined to a joystick axis (never tried this, but don't see why this should be). In any case, if mapping the prop levers to a joystick button is possible can you please just tell me which is the correct mapping? Thanks.

Only right side windshield wiper operates; i.e., is animated (can't remember if this was different in v1.3, as I rarely use the wipers).