oldflyguy

@Goran_M I'm a relatively new X-Aviation customer - started when the TBM was released then SMP & RWC shortly after - and I must say I find the "new" activation system very easy to "live with". Frankly I don't remember naming my computer in the original download of the TBM but then I'm almost 73 so that's to be expected . I have given the activation system a bit of thought after watching the video (thanks by the way) and can see scenarios where a user might want to re-authorize a computer. Perhaps the new rig went South for a bit and the user might want to use the old rig in the meantime - just one example. I think LR would allow this as long as it was just one program in use on one computer - not sure as I've never attempted this but I do have two desktops in my office, the new build and the old HP. I can also see a scenario where a user could possibly not fully understand what the end result of the de-authorization process might be. Having said all that, I believe there should be severe penalties for software pirates but I don't see that happening (unfortunately).

I'm with @Goran_M on this one. I have 16GB RAM as well but have never had a crash with the TBM. Like many XP users I have far too many payware aircraft - I experience much higher FPS and much lower RAM / VRAM usage with all of them. I also use Ortho and the usual suspects for plugin's. The use of HD Mesh AND Ortho AND the TBM has the potential to overwhelm your hardware. The CPU is just "OK" for XP but it is a bit slow - all those cores (over 4) don't help. I have an i5-6600K@4.1, 16GB of 3000 RAM and a 1070 8GB - settings are HDR, max compressed and high objects. No shadows, parked aircraft or AI. Absolutely no issues with the TBM. 35+ FPS at MisterX KLAX. Try disabling the HDMesh - that may help. You have "hung" a lot of "stuff" on your XP install and may have hit a wall...

LOL! I never take anything personally and I find all this "stuff" interesting. I do appreciate your timely and informative responses. I am a SMP fan...

Good morning Frank! I beginning to see where my issue is with layers. I also loaded up the metar I sent to you and of course I had the same result. The difference is - and you can tell from your screenshot - that the broken layer is supposed to start at about 1200' AGL and goes up to about 6000' (KVUO is at about 20') but the broken layer we see is at about 5000'. That broken layer is certainly "correct" but should be much "thicker" (?). The 2nd layer of overcast at about 11,000' looks correct but I did not fly up there. I can see now that this is where I'm seeing "incorrect" layer info - the layer is there but the altitude and extent (vertically) is still off. And yes, the cloud art looks great. I'm going to post over at the .org site to see if anyone else has picked this up as it may just be an ASXP / SMP, RWC thing...

Also, was using Soft HD...

Good morning! Man, you are dedicated - I did not expect a response until after the weekend! Here's another Metar file (seems to contain some data). KVUO BKN 012 - 060, OVC 110. Only a BKN layer at about 050 is depicted - clear below. METAR.rwx

Here you go! I flew around KLAX where OVC at 012 was reported. Didn't hit a layer until 020 - I thought that this was nit picking so I paused the sim and checked out KPDX (always dependable for layers) and found BKN at 012 through 035, then BKN at 100 as I remember. It was clear until I hit a BKN layer at 054 - I could see another layer above that I assumed was the BKN 100 layer but didn't go there. I does seem something is "off" with those lower layers. This is with SMP, RWC and ASXP. Also using FlyAGI but just for LOD (didn't make a difference when I removed flywithlua). Gotta say, where the layers exist SMP looks pretty good... METAR.rwx

Sure, thanks! I'll look for some low level layers and send them your way

I'm sure everything is working correctly and configured correctly - it isn't that difficult. (ASXP with SMP and RWC) Still not getting the lower cloud layers. KVUO just now - BKN 017, BKN 030, OVC 060. Only the OVC 060 shows up. It appears that BKN, SCT and FEW layers don't show up when they are very low - say 010 - 030 AGL. Most noticeable departing and arriving at airports obviously. Otherwise SMP cloud depictions are fine. Default XP RW WX shows the layers correctly but once you've experienced the SMP clouds you don't want to go back. What to do??

Well Frank, loving the way the latest version is looking. Unfortunately I'm still missing a layer. I just tried a flight out of LAX as there were two layers at that airport - 010 SCT and 050 SCT - the 050 layer was there but couldn't tell about the lower layer until I took off (Dutchess - easy for testing). Sure enough clear as a bell all the way to 050 when I entered the scattered layer. Now that I'm thinking about it the layer(s) I'm most often missing ARE the lower ones. Don't know if this is helpful but it's easy to check out (right now)!

I wanted you to know that all is working as it should with ASXP, SMP and RWC. The cloud layers appear to all be there and at the expected altitudes. I've only been able to find 3 layers in my recent "hunt" - hoping to find something a bit more complex. Thank you again for your response and also the quick turn around on the broken installer. Ken

Thank you for this information. Downloaded the new .8 version and was able to install RWC - going to check it out later today.

Thanks! No worries...

I can confirm that RWC is set to "external injector". Funny, I uninstalled both SMP and RWC (looking to try anything) and now that SMP is re-installed (and seemingly working fine with just XP's WX, by the way) I can't install RWC (as apparently others have found as well) . As Rosanne Rosanna Dana (SNL - yes I'm that old) would say "it's always something". I'll let you know if anything changes as soon as I'm able to install RWC 1.1... '

Same here. I will open a ticket as well...

I've had SPM (just updated today to .8) and RWC for some months now. I use these with ASXP and as much as I want to like them they don't seem to well with ASXP - the altitudes are still "off" and more importantly the cloud depiction is still missing layers. After updating SPM I tried a test flight at KVUO (looking for layers) about 008 SCT thru 060 then OVC from then on. ASXP without SMP and RWC had the layers spot on (ASXP HiRes Clouds enabled). I restarted with SMP and RWC back in the plug-in's folder and sure enough only had the 060 OVC layer. Totally missing the lower SCT layer. This is not an isolated situation - it seems (after a few months of use) that the SMP/RWC combo is always missing a layer or layers. This could be operator malfunction - if so please let me know what I'm doing wrong.

Could be, but the difference of 30 degrees or so still existed between the C172 and the TBM on the ground. Not important, though. I'm hoping the devs can fix this in the next few weeks now that 11.32 is a release candidate. Did a nice flight with ASXP, SMP and the DA-62 from Orbix KVUO to KBDN today. Love to fly over that high desert ortho although all of Mt Hood and West was in the clouds...

Hello again @DwightP980! Well, after reading your post I tried again with the two aircraft (C172 / TBM) at KFRG (Atlantic ramp) and the Deer Park VOR (about 7 miles away) and got the same result while parked at the ramp. I never did try this in the air so I fired up the TBM and took off. I turned toward the VOR and determined the direct to with the CDI, moved the heading bug to track and yes, the TBM did track directly to the VOR. So, I don't know why the discrepancy exists on the ground but in the air it seem to work OK. Just wanted to let you know... Best, Ken

Hi @DwightP980. I don't think the VOR to VOR is going to work very well. I tried that and noticed that the radials were "off". Try loading the C172 / G1000 at an airport near a VOR then see what the "direct to" is. I think you will find the VOR info in the TBM is different. It's off by 20 or 30 degrees in my sim. The TBM is addictive and when it was working properly I flew it to the exclusion of all my other payware however I'm not going to invest time in this model again until it's fixed. I'm thinking that is going to be longer than "a few days" as it seems really, really broken. The upside of this is that I'm getting back to flying a few other models and realizing how much I enjoyed them prior to the TBM. Meanwhile I will - along with many others - hope that the TBM is fixed sooner rather than later. Keep the shiny side up!

Not confrontational at all @Goran_M. Never doubted that help was on the way - and don't hesitate to let us know when submissions start to overwhelm the process...

Hi @Goran_M! I can confirm that with a fresh TBM install, new XP Pref and empty TBM "State" folder the crash still occurs with XP 11.32b1. As soon as you select the "enter" button (airport or other) XP will quietly close down. I feel your pain...LOL! However, since all my other payware aircraft work just fine and I have not experienced any other downsides with XP 11.3xxx versions it appears that you folks NEED to address this here. The crash info may have been relayed to XP but they have bigger fish to fry than "fixing" the TBM. Please do all you can to get this fixed on your end. I have been happily flying this incredible model since it's release - it is so painful to leave it in my virtual hanger... TBM900_Log.txt Log.txt

@j07rdi, we all appreciate your detective work! And yes, except for the G1000 and the AOA indicator it all seems to work fine. I'm just wondering if you can find a TBM900/A somewhere in Trade-a-Plane...really LOL! Keep the shiny side up...

There is no question that the latest XP update has "borked" the TBM. My own experience with 11.31r1 has been very positive with this exception. All of my other payware models are working. The problem areas that still exist in this update don't seem to have any connection to the TBM issues. It's looking like this is a "custom G1000" thing that the TBM devs need to address. One more thing - is it just me or did the AOA indicator stop working as well? Looks like the TBM goes into the hanger for a while - it's my favorite by far but...

Hi @j07rdi! Nice bit of detective work. My results show that upon deleting (saving first) the Pref folder and restarting XP a flight plan can be loaded. However, upon deleting that flight plan on a subsequent restart the issue returns. But that's a really nice try...

Whatever you do, don't change the destination airport...LOL!