Cameron

Hi, Guys, It's perfectly normal and not the cause of what's happening here.

Approaching Darrington in the C400 with RealScenery:

I've had some further discussion with Laminar on this issue, and we'd like some more diagnostics done. Here's what we'd like from those experiencing this issue: 1. When the FPS are down to a low level, please state what your FPS are in: 3D view, 2D view, Exterior view, and Forward No HUD view. 2. What is your CPU usage when your FPS are low? One important test in addition to the above: Turn your texture resolution down one level. Restart the simulator and see if the low FPS can be reproduced again. The point of this test is to help see if this is a resource exhaustion. Thanks!

For those experiencing this issue: The following is a questionnaire to try and help narrow this down. Please answer the following (please do not reply to this unless your high FPS drops down to 19): Before answering, please try the following procedure the next time you have low fps: 1. Open X-Plane and open the Corvalis 2. Go to the rendering settings menu 3. De-select the checkbox to keep X-Plane at full screen 4. Close the window and view your FPS. 5. Go back to rendering settings and select the checkbox again for full screen. ----------------------------------------------------------------------------------------------------- 1. When does the FPS drop usually occur? Upon load of aircraft, midway through a flight, or random? 2. What happens when you go to a different view? Do your FPS improve? 3. Does this always occur in the same view? If so, which one (Cockpit, exterior, 3D)? 4. Did you try the procedure in bold above this questionnaire? Did your FPS improve after? 5. What operating system are you on? 6. What video card do you have? 7. If on Windows, what video card driver version are you using (n/a if on Mac)? 8. Please list your system specs (CPU, RAM). Thanks for your time!

I can recognize and appreciate that it is not only you, Tom. I can also recognize that it's not the majority, and it's not every time the aircraft is loaded on every machine out there. I say I'm sorry, because I am. These kinds of things are frustrating, even more so when I or other developers including Laminar can't duplicate the issue you speak of. It loads in 9.5, does it not? It flies in 9.5, does it not? The aircraft is compatible just as is "claimed." No one is being deceiving here. FPS and compatibility are two different things. And again, I'm still unable to reproduce this. So I must ask, if I can't reproduce the same problem on multiple machines, is it really a problem with these two addons alone, or something on the various machines (like drivers)? So, Is it driver specific, or is it not? I can't place blame on anything at the moment. Yes, I will be interested. All the above said, I'm NOT saying I don't care. What I'm telling you is that without something I or any other developer can reproduce, it's going to be very hard to give an answer for this. It's time to get off of defensive mode, Tom. The attacking portion of "If you care," "If you want to be," or insinuating I don't give any form of sympathetic view on this is far from the truth. If you want to help with the tracking down of this that's plenty okay. However, the accusatory remarks need to stop now.

This isn't X-Aviation specific. It's hit and miss, I think, and applies to all aircraft you may have for X-Plane (a caution issue, I mean). I personally have never batch converted any aircraft I've had. Never really thought to or seen a need to. Is there something you feel you gain from doing so?

Hi, Tom, And while this may only happen with the two products for you, it doesn't happen to me, or any other developer associated to the project. I have already talked to Laminar about this, and with their busy schedule were willing to take a look. They too are unable to reproduce this and have said they feel it may be some form of a video driver issue. There are just too many possibilities. I'm sorry, Tom, but until any of us are going to be able to reproduce this, then it's going to be truly hard to say where or who the problem lies with and why. There's not much we can do right at this moment.

Hi, Tom, No, we don't. If it's OpenGL, it would be OpenGL from X-Plane itself and not the aircraft, as the plug-in contains no OpenGL. Unfortunately we're not able to reproduce this as some of you have.

This is really a pretty unavoidable issue...mainly due to the way things are linked up and how XP requires it. There should be no reason to ever update any of our aircraft without a patch anyhow. If there's nothing released by us, it's safe to assume "it works."

Hi, there, The DRM is not causing the issue, but it IS letting us know that the aircraft has been altered. Your batch conversion may have messed some setting up that is toying around with the G1000 plugin. It is quite evident the acf file has been changed, whether you meant to or not. Safest and easiest bet here is to do a complete re-install (not of Gizmo) of the aircraft from the original zip. If you don't have this available to you you'll need to use the contact form on X-Aviation to request the new download. Please be sure to include your order number.

What exactly are you questioning? The oil pressure low? Are you saying that it is like this everytime you load the aircraft? Your log file also indicates you have done some form of editing to the acf file. Even if something simple, but something that you've edited and re-saved the aircraft file for. Can you shed some light on any changes you've made?

For those interested, it appears this issue is resolved. JensNDS successfully activated his product after installing this last step.

You need to cut it off for pasting right after .zip: http://connect.creativelabs.com/openal/Downloads/oalinst.zip

The problem is something to do with your Gizmo installation. Did you install the OpenAL package as the instructions say to do? Can you post your log.txt file located in your main X-Plane directory?

Hi, there, Yes, it can be installed on multiple computers. It's a great app!

Whatever works! Glad you're up and running.

Hi, there, Yes, it does. X-Plane changes the view to become the same as pressing ctrl+o for 3D mode, but at a fixed angle. As such, it is considered a 3D view. As stated, you'll need to either: 1. Press the right arrow key in 2D mode or 2. Utilize 3D mode (ctrl + o) and move the view to the center console.

Hello, You're using the 3D mode, which means you'd need to use the ReadyPad in the center console. If in 2D mode (w key) you can use the method I mentioned in my previous post.

gthomas, The problem is that you are trying to do this on the incorrect display. You'll need to use the right side display, and given your screen resolution, you'll need to first press the right arrow key. This will move your view to the right, and then you'll need to use the FPL key on that right side disply.

Part of the reason behind this is because X-Plane doesn't utilize registry values for it's install process. The updater doesn't either. I actually prefer it the way it is, as it's very easy to trash X-Plane and know you've truly trashed it if you want a fresh install.

Hi, Maxime, Your hardware is getting pretty old, so I'm not sure I can even be of too much assistance here, but, try this: 1. Open X-Plane and open the Corvalis 2. Go to the rendering settings menu 3. De-select the checkbox to keep X-Plane at full screen 4. Close the window and view your FPS. 6. Go back to rendering settings and select the checkbox again for full screen. This is usually chalked up to a video driver issue, but it's going to be relatively hard to provide support for a card that old. Hopefully the above will have some kind of positive effect for you, but if not it may be time for an upgrade someday soon in the future!

This was going to be my question as well. UAC issues in the program files folder. Ben Supnik has said many a time it's not suggested to install X-Plane in the program files folder.

Hi, there, That was the response we were hoping for. X-Plane will (by default) load every plug-in located in the resources/plugins folder. As you can imagine, this will cause a massive headache with various aircraft plugins doing their own things to the X-Plane systems, from fuel flow, to amps, to activation hiccups, etc. X-Plane will think all of these plugins should be active for whatever aircraft you have loaded, so to fix this Laminar added the plugins folder within the aircraft folder feature. Doing so makes X-Plane ONLY keep active whatever plugins are in the resources/plugins folder and the aircraft folder. So, for example, if you keep the MU-2 plug-in in its respective aircraft folder, and the Corvalis plug-in within its respective aircraft folder then X-Plane will ONLY load those plug-ins if the aircraft is open in sim. Glad you seem to be back up and running!

Daniel, Whether you purchase today or the day of the patch release, you're not going to be getting the version any sooner than anyone else. All updates will be provided in two methods once we are confident in the two. You will have the option to update in sim, or download a zip file and update the product yourself manually.

Jens, In the future this kind of tech support should go through X-Aviation's contact form: http://www.x-aviation.com/catalog/contact_us.php We make it a policy to not do activation tech support over the forums for security reasons, but I'll make an exception to this this one time rather than re-directing you to the contact form. We have a lot we are working on at the moment, and one of those things is a license management portal for customers. This will allow people like yourself to manage your licenses without contacting us, so just know we're working to improve things over time. In the interim, I've added provisions to your account and you should now be able to activate your Falco on the LAN.