Cameron
X-Aviation-
Posts
9,813 -
Joined
-
Days Won
414
Content Type
Profiles
Forums
Latest X-Plane & Community News
Events
Downloads
Store
Everything posted by Cameron
-
You can do so here: https://www.x-aviation.com/catalog/account_newsletters.php
-
It's simple, Matthew. There are a lot of projects because it's a team environment. Goran strictly does 3D modeling. When he gets done with his part, he passes it along to the next person. It goes from UV/Texturing, to programming, to animating...there are various people involved. As such, Goran makes the best use of his time by creating a new model in the mean time since his job is "finished."
-
Hi, Jens, Yes, this is exactly what I was speaking of. A little clarification: The rheostat in the Falco will not adjust the brightness of the Garmin. This will only work for products like the Reality XP Garmin. For the default Garmin shipped with the Falco, SeaMax, and generics used on the C400, any brightness levels are saved just the same. Again, you'll need to make adjustments to these prior to loading a new aircraft, or by restarting sim. This is an X-Plane problem, and not something to do with our products. It goes for any aircraft using the same numbered light as the previous you had opened. If you wish, you can report your findings to Laminar and discuss it further.
-
Hi, Jens, I'm not sure if Laminar considers it a bug. There are a number of lights available to use in X-Plane, however, almost everyone uses the same numbered light value for their instruments or gauges. As such, the setting flows over to whatever you load next. I'm pretty sure we had looked into this in the past (hence the reason I know what's happening), as we noticed this prior to release of another product. However, I don't believe there was a work around programmable at the time. I may have to revisit it, but the simple answer is what's been said...X-Plane saves the last light values unless the sim is exited. If you're talking about the Falco and not the Falcon, then you should be able to just up the lights from the rheostat if the lights are dimmed down too much (or off for that matter).
-
Hi, Jens, For aircraft that use 3D lights, X-Plane remembers the last light setting from the previous aircraft.
-
Hi, Riccardo, Please see the following: http://forums.x-pilot.com/index.php?topic=751.0
-
Hi, Riccardo, There's not much to say here other than it will be an FMS that utilizes the AIRAC data and simulates functions as per the CRJ-200 spec. It's nothing different than you would expect from those like PMDG in the FS world.
-
On a properly calibrated monitor, the above image is borderline "terrible." Just to be sure I've cross verified this on my Mac's as well. What you have to remember, Jack, is that X-Plane brings in textures much darker than they are when exported from any program used to edit or save them. The result of the above image from within sim would be far from ideal. Additionally, because of the wide range of gamma out there, as well as how X-Plane portrays things, screenshots will often times come out BRIGHTER than they appear in sim. X-Plane does NOT export gamma settings to screenshots. As someone who develops an aircraft, I'm surprised you don't see this, Jack. Perhaps when you get into aircraft that have solid colors (red, blue, etc), you'll begin to see this some. Lastly, the image you edited (that Eric originally provided) is NOT what is our final output seen in sim. It's what we showed you PRE-PROCESSED, to compare with other pre-processed vendors. Again, we want Norcal to be the best it can be. We've been around the block on color corrections so many times that we're sure of our decision for what has been made final. It is leaps and bounds above any other package we've other released, and we stand by that comment. For those that choose to purchase, we're confident you'll feel the same. Thanks, all!
-
Garrett, Please refer back to my last post. Non-enhanced sceneries have some washed out areas, but the Norcal package has been in production for nearly a years time, and has had a tremendous amount of color correction done. Tennessee (which you mentioned) would fall into the Non-Enhanced category as mentioned in my previous statement posted above. Norcal comes from different sources than traditional packages we've done, and we've gone that extra mile to enhance not only the imagery, but the roads and night lighting as well. As such, Norcal is the first "Enhanced" package available, and should definitely not be compared to any previous packages we've ever published. It's honestly an entirely different animal when compared to previous packages and time spent working on it. We don't use satellite photos for RealScenery. I'm sorry, but having been one of the few to fly over the Enhanced imagery and Norcal, I don't agree with your statements. It is our desire to ensure we do Norcal right, and if it really were a problem we would definitely fix it! We want Norcal to set a new bar, but of the various people I have asked, in addition to others posted here, you're in a minority at this point. If we were talking about one of our previous packages I may agree in some areas. This time...I don't.
-
No smooth option in FS X. The same can be easily achieved in X-Plane, but extra polys in the wrong places can cost you, and using them on knobs when you can get them to look relatively good already is not where they should be spent.
-
Hi, Guys, Nothing to show at this time. Working as hard as we can. Thanks for checking in.
-
Hi, Jack, I can't say I agree any bit with what you are saying. Non-enhanced sceneries have some washed out areas, but the Norcal package has been in production for nearly a years time, and has had a tremendous amount of color correction done. It's stunning and beautiful in sim. X-Plane's atmosphere can add brightness dependent on your gamma settings and time of day/visibility, but that's about it.
-
A few quotes from Heinz: "This plane will not be cheap to produce as a licensed product." (licensed meaning by Boeing) "Like every other virtual plane the realism is limited to what can be done in a simulation so 100% realism to the real plane is not possible. There are also limitations to what is allowed to be released .....that is some things will remain classified by Boeing. In short the project will evolve through updates after release as more information becomes available." Do I even have to say anything? I question a lot of the authenticity here...
-
For the Javelin: There is a 1.3 update available. Since you're not a customer of X-Aviation, Javier will have to get with you on that. For the CRJ: The questions you have asked have been asked countless times. Please read through the forum and do some searches here: http://forums.x-pilot.com/index.php?board=42.0 For a list of FAQ, please read here: http://forums.x-pilot.com/index.php?topic=543.0
-
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?