Cameron

I remember you from just a few days ago. Your actions are definitely not forgotten. Oh the fun road that lies ahead for us!

What location do you have X-Plane installed to? It is highly recommended that it not be installed into the Program Files folder.

Hi, there, Again, we're unsure at the moment. As soon as possible is the best answer! The update is really under the hood items. Some people had an issue that others do not, so it works to solve the issue. Overall visuals will remain the same!

1.4 is dependent on external parties as well, and as such the "soon" title is the best we can give at this time. We'd like to assume sooner than later at this point and time but do not have a definitive date.

Disc 1.

The post in question is here:

Hi, Charles, No, that is not the topic I speak of and pilotview was not anything I was referring to!

This has already been discussed and answered, and a quick search of "popups" would have answered your request/question. As has been previously specified by Philipp, location saving of display popups is on the list of things to do.

I will reserve comment until this has been further tested on our end. We have no control as to when or how these show up. That's something better taken up with Laminar for. It's a matter of 3D-Space and X-Plane's interpretation of when manip handles should show.

Nice, Leen!

A couple of things: 1. Please make sure you are running the latest version of X-Plane 2. Please make sure you installed this using the installer and not dragging from one version or copy of X-Plane to the other. This will NOT work! If the problem persists, re-run the installer.

Nicely done!

No problem. Glad we got this sorted!

It is not a problem at all to run it on two versions of X-Plane. This is completely within your right. The problem you are likely facing is memory exhaustion. We have seen this a number of times across various products now with X-Plane 10. It's a very hefty 32-bit application and some systems just aren't cutting it any longer without the 64-bit functionality. Basically, X-Plane will shut down functions or plug-ins in an effort to keep itself running. You may want to try lowering the resolution of your textures in X-Plane. Try setting it to "low" in the X-Plane resolution settings menu. If this does not work, re-name your Custom Scenery folder to 'Custom Scenery_old', and create a new, empty folder titled 'Custom Scenery'. Just for our information, can you please also list the system specs for the machine this is running on?

After further investigation it appears you purchased this product elsewhere than X-Aviation.com. This section of the forums is for customers who have purchased from X-Aviation, so please utilize the support systems available from your original place of purchase. More than welcome to hang around X-Pilot and enjoy the rest of the forums, however!

Beautiful!

I have just tried this in both X-Plane 9 and 10. I flew from Reno to Sacramento, with many FPL changes along the way following your instructions as well. I cannot duplicate ANY of what you are seeing. Everything worked flawless on this side, just as it has for JGregory. Anything else we can try that gives the same behavior every time with a specific process?

Hi, there, Can you please specify whether this is XP 10 or 9? Can you please upload the log.txt file in your main X-Plane folder?

As this topic has found a resolution, it is now closed.

Just remember to put it back if you wish to fly X-Aviation products. It has nothing to do with slow support at all. This issue extends beyond anything "simple." An active topic about this with explanations can be found here:

That's an assumption on your part, Marc. It's not fact. Trust us when we say that we've invested much time (almost too much) in porting to Linux. It's NOT as easy as you are assuming, even if you've programmed your own works for X-Plane. Gizmo is a whole other beast in it's dependencies and compiling needs. Investment is dependent on how much money we must pay someone to do the port...it's not a cheap investment in comparison to the ROI. It's simple business when you look at the numbers, and suffice to say...I'm sad about it. I DO like Linux, but I too must face this reality. Understood, Marc. It was figurative speech to be sure (coming from Ben, that is). Hi, Paraffin, We understand that and see it wholeheartedly. It is not something that can be fixed at this moment, and it's not something we enjoy having our customers endure. Had it been an easy fix we would have solved this a long, long time ago. That said, we are very confident with our use of Gizmo and its future. While I can't let all of the cats out of the bag I can assure you that all of this has been methodically planned out as best we can while we get to the end goal. A goal that we are quite sure will revolutionize many aspects of X-Plane and how we interact with it as users. X-Plane is a growing market, and these are parts of the growing pains. It's unfortunate, no doubt, but we are trudging on with confidence. It's hard to have faith in all of this for you guys on the outside, I'm sure, but it's all we can ask for from our customers at this time. We'll ultimately get to a very happy place...that I'm sure of! Happy flying!

Hi, Jim, I can see where your frustration is stemming from. I can assure you Philipp meant no harm. Sometimes the language barrier gets in the way and things don't always come off well over text. Philipp is a very "happy" guy in person, so I know his intent was nothing but good in his response to you. I suppose this should have been better explained. X-Plane.org and X-Aviation don't run the same plug-ins. We DO run the same aircraft systems and core product, but the activation processes are slightly different and a couple of sounds on Windows are coded in a different way to better tailor to compatibility with ALL X-Aviation aircraft. This basically ensures that all XA customers have a smooth experience for anything they buy from us. So, in short, yes, the aircraft itself is the same, but some very minor subtle changes are there between the two store versions to accomodate for the sound slot issue and activation processes.

If you're truly interested in this there are a number of examples about the forums as to how development and example uses have shown Gizmo's capabilities BEYOND aircraft use. It will be even more apparent once these uses hit the market. This is nothing new. As already stated, SASL products cause a problem...the PBY is a SASL product. That's entirely your decision! Not true once the products that will make it very evident of Gizmo's intended capabilities hit the market. We'll be sure to make this very apparent.

Hi, Jim, Firstly, these forums are for X-Aviation customers of the CRJ. From what I can tell you did not purchase from our website with regards to this aircraft. That said, I'll assist in this instance: The issue is that you are utilizing a version of the CRJ purchased from a venue other than X-Aviation, and which is a different plug-in in some areas to do with sound. The X-Aviation version works around this. What is happening is your CRJ is conflicting with Gizmo with regards to OpenAL sound. The screeching is then experienced from this clashing while the plug-ins fight for sound slots. Considering your loyalty to X-Aviation in the past please contact me using the following form: http://www.x-aviation.com/catalog/product_info.php?products_id=68 I'll be willing to work something out for you regarding this matter.

Hi, Jim, The only time I am aware of this happening is with the presence of other plugins fighting one another. Can you please upload the log.txt file located in your main X-Plane directory?