danklaue

Ah yes: because one of those folders contains the instructions to hide the pilots when sitting in the pilot's seat. But you say you got LESS frames... that's strange. Well, at any rate, we're looking into this.

OK, that'll be reflected for the next release (lights, and test pattern). I've also now put a switch in place to turn off all the lights when the plane starts from cold and dark.

Haven't heard of this phenomenon before... but let's say just for argument's sake, would you be willing to remove some folders from your "custom avionics" folder temporarily, and see if that makes a difference? (You can actually simply create a subfolder in your "Custom Avionics" folder, and call it "unused", and temporarily place the following items in there, just to get them out of the calculation loop): -A_Popup -A_Popup_2D -A_TabSys -C_Popup -C_Popup_2D -C_TabSys -O_Popup -O_Popup_2D -O_TabSys I'm wondering whether these might be causing problems on some systems. Specifically, what I'm looking for is, if you notice slowdown over time, even with these folders removed. (They're the ones that give you the pop-up menus, so you'll be without those for the duration of the test).

Actually, for the newer planes, the scroll wheel plugin has the option to turn off scroll-for-zoom already. So, as a user of one of the newer planes (SuperManipulator-equipped), you could either shut off the scroll plugin altogether (via the "Plugins>Plugin Admin>Enable/Disable plugin" dialog) in order to ONLY zoom with scroll wheel, OR you could go to "Plugins>MouseScrollOptions" and click on "Disable Scroll Zoom" in order to JUST have access to the scroll wheel for manipulation of knobs... leaving you to zoom in with keyboard short cuts or joystick button assignments. (Not a bad option either). For now, we'll have to wait for Laminar to give us any sort of control over the right mouse button, before we can span it in to do anything like what the idea was above... however, we can already explore creating options to allow users to disable "scroll for zoom" via keyboard short cut, or when inside the 3D cockpit only.

For those who don't like the scroll wheel feature, you can always disable the plugin, and only use the click, click-hold, click-drag horizontally, click-drag vertically features. So what concrete steps would you suggest to avoid the "faceplant into the gauges" scenario? One thing I could think of doing, would be to ask Laminar to provide an option to disable mouse wheel zoom via dataref. Currently, that's not possible. I imagine, as Laminar spends some more time thinking through this, they'll also come up with some better ways to avoid common unpleasant scenarios, especially if it can be shown that the market (i.e., you) are expressing preferences/opinions about these things. (Not that Laminar has always listened when the market made requests, but... if we don't say ANYTHING, there's no way Laminar will get the sense that it is something important to end users.) Another idea would be, to request Laminar to tie the "Scroll for Zoom" functionality to the right mouse button... so that zoom, at least in the cockpit view, only occurs when the right mouse button is simultaneously pressed. Normally, right-click allows you to pan around the cockpit... so if you're in that mode already, of scanning around the cockpit, pointing the camera at a gauge of interest, it'd make sense to have the scroll wheel available for zooming. External view could remain as it currently is, as right-click panning often pushes the plane out of frame, unintentionally. Or a combination of these things. One could have a dataref that, when set to "0" disables all "scroll-to-zoom" functionality. When set to 1, you'd have "scroll to zoom only when right mouse button is pressed, inside the 3D cockpit view." When set to 2, you'd have "Scroll to zoom only in outside views; not in 3D cockpit view at all." When set to 3, you'd have "Don't scroll to zoom at all." That'd give authors some flexibility which they can pass on to their clients as well. I think I'll suggest this to Laminar, actually.

OK, here's what's happened: -There's a dataref in X-Plane, which is called "sim/time/hobbs_time". This Hobbs meter just kept moving forward, and all it was able to do was generate a semi-random number for the actual Hobbs meter. Not very useful. -Carenado and Alabeo created our own Hobbs dataref, and set the logic to start the Hobbs meter whenever the engine of the plane was running, and saving the value to disk, for next time the plane was loaded. -X-Hobbs did something very similar. In both cases, the trick was, to have a little text file inside the plane's folder that would register the new Hobbs value attained during that flight, and continuing the count, as it were, next time that plane was loaded. -Then Laminar did something similar in v10.40: they added the Hobbs value to the "***_prefs.txt" file (the asterisks represent the name of your plane). Here, stuff like the chosen livery, the camera snap points, and also now the Hobbs meter value were stored. -As soon as Laminar came out with this, it became superfluous for Carenado/Alabeo planes to use this. Newer planes simply use X-Plane's internal Hobbs meter. -An interesting note: Carenado and Alabeo have used stored camera snap points way before X-plane did this... and from the way the Algorithm looks, Laminar's implementation is almost identical. So again, we've been trailblazing features that end up finding their way into X-Plane itself... both with camera snap points, and with Hobbs meter functionality... next up seems like we'll soon see universal SuperManipulator á la Carenado in X-plane... but probably not before XPv11. Some older Carenado and Alabeo planes might still have the old custom implementation, due to the fact that it's difficult to go back into the source files and change the animated components without the risk of damaging other aspects of the plane, due to changes in the authoring tools.

That's all been fixed. Just re-download the plane.

I keep hearing vague reports of stuff amiss with the HSI, but as of yet (and it's been a while since this plane was published), there has been no serious attempt by anyone experiencing this problem, to narrow it down to a reproducible scenario that I can actually tackle and fix. As long as that doesn't happen, I don't consider there to be any serious lighting issues, unless we're dealing with isolated cases, where the problem may be related to something completely unrelated.

It's now available on all major resellers, and has been updated to v1.2. v1.2 Change Log -Improved sounds and visuals -ASI comes alive after 25 kts. -Inset map on PFD closes only when prompted -PFD "NRST" now hides frequency inputs without values, and pressing "ENT" works as it should -Direct-To now only removes waypoints after selected -Activating leg using ENT button in MFD now works. -"PAGE" menu added to Flight Plan page -Flight plans aren't automatically saved. -Added HSI dots in PFD -MFD splash screen now also gives way to MFD content when "ENT" is pressed. -Added "GND" Transponder mode. -improved electrical logic (PFD now turns on with Stby battery switch, battery voltage corrected)

The one way to quite easily discern whether a complex instrument was authored completely outside the scope of X-Plane's pre-fabricated, drag-and-drop instrument authoring paradigm is this: any time an instrument can be popped out as a 2D pop-up window, you're dealing with a completely custom-programmed instrument. (The only exception to this rule is the GNS430/530, which was authored by Philipp Muenzel for Laminar Research not too long ago.)

"Stock G1000?" There is no stock G1000. As I mentioned before in this very thread, there is practically nothing stock about this G1000. A few comments back, someone expressed the expectation of the G1000 having at least the functionality of the GNS530, to which I responded with an attempt to clarify that this initiative by Carenado represents a complete re-authoring of all the features that Laminar (only recently) put into their GNS530. And the stock G530 was authored not as a plugin, but as an integrated part of the sim... with Laminar's full support, full access to source code, etc. The X-Plane plugin SDK does not include a way to engage with the new GPS system (The one that runs as logic to the new GNS430 and 530). The SDK allows you to hook only into the old, legacy FMS/GPS data structure. Until Laminar provides an SDK for the new FMS/GPS system in X-Plane, this means, all the functions you are hoping to see in the G1000 had to be programmed from scratch... and the data for stuff like airports, nav databases, elevation, water ways, etc. have to be painstakingly extracted and derived from files that are found in the X-Plane installation (such as .dat files, .apt files, .dsf files, etc.) in order to display them on the G1000. Installing a "stock" GNS430 or 530 is a matter of dragging in a pre-fabricated instrument (which Laminar provides) from X-Plane into the panel... which would take only a few minutes to do. To make a plane with a G1000 means, to program the entire G1000 unit from the ground up; each function, each mode, each soft-key, each knob, each database access point, each checklist item, etc. using data that is not always readily available, but must be obtained by scrounging around the X-Plane installation or deriving data from permissible online sources (such as the vector-based water ways or Nav data). The G1000 represents several man-years of development.

So far, the feedback for v1.1 has been quite good. Very few problems. There are single cases of people who are having some troubles that we haven't yet got to the bottom of, but I suspect that it may be something really simple, such as folder names that have spaces or special characters in them... or conflicting plugins or something like that. Others simply seem to have expectations on this plane that aren't fulfilled (such as those already discussed in this thread). So despite a bit of a rocky start (which was somewhat to be expected), things seem to be looking up.

V1.1 is out. Change log: -Adjusted oil temp, ITT, oil press temperatures and green zones. -Adjusted MP arc. -G1000 electrical logic improved. -Autopilot FD button now highlights correctly, and does not require an initial power-cycle. -Duplicate waypoint popup now appears in flight plan, and sets correct waypoint. -Uses magnetic GPS course now. -BRG in NAV status box now display magnetic GPS course. -Push knob to sync NAV needles to direction of station. -Opening WPT page on MFD does not throw errors anymore. -Disabled softkeys that lead to non-existing features. -Displaying LOADING ... in NRST on PFD until airports are loaded. -Added wind direction and speed display. -BRG2 in PFD now shows Nav2 distance. -Added unfilled from to arrow for nav2 in CDI. -Pop-up window for "Loading" dialog. -Now detects if nav1/2 is VOR or ILS. -Tweaked MFD pop-up window right knob behaviour. Customers should download the package again from the link provided. Downloads and installations were increased. You should uninstall the aircraft (delete the old folder) before installing this new version.

The Nav database will be updated by Carenado. It's based on X-plane's .dat files. Waypoints should be editable already. PROC button? We're looking into that.

I understand the expectation that there needs to be at least as much functionality as in the built-in 530, but the reality is, that the GNS530 is a closed system, to which Laminar has not created any "handles" or any ability to alter what's already there. At BEST, you may be able to draw some layers over top of the existing GNS530 to approximate the functionality you're looking for. The G1000 represents a complete re-authoring from the ground up. This is how it often is, when you want to enhance something. An easy-to-understand example would be the sound engine. X-Plane offers a "default sound architecture", which has a certain limited set of capabilities, but you do not, as an author, have any control over the fade-out distance of sounds, or their stereo placement. If you want to gain any control over those features, you have to create an entire sound architecture from scratch, which also means, you'll have to replicate everything X-Plane already does, using your own code: doppler effects, pitch in relationship to engine RPM, sound intensity with distance, etc... before you can even start THINKING about altering such parameters... only once you have your own architecture, you can start building on that to generate the effects you're actually looking for. Same thing with the G1000. In order to gain any sort of control over and above what's provided by the GNS530, one has to re-author EVERYTHING from the ground up... but this also gives the flexibility to add or alter features, as time goes on. It has been an extremely long journey for Carenado to get to this point, and it is to be expected that there are still some things to iron out... particularly also because this is the first product released by Carenado that uses DRM. In fact, there are a lot of "firsts" coming together in this aircraft, and we are expecting some "teething" issues as a result. We appreciate your patience and understanding, and hope we can get all the kinks worked out within the next few days or weeks.

Here's a picture of a real one. The panel gets its registration number from the livery folder's name. If you create custom liveries, just rename the folder to what the registration number of the aircraft is, and the panel should reflect that.

Appreciate the enthusiasm. The SR22 is indeed a gorgeous plane. But I will not comment on the production order.

All in due time. Before biz jets, the G1000 needs to be brought forth.

I was actually not sure about the 4k video... when I published it, I noticed that playing it back on smaller devices, such as iPads, rendered the cursor of the SuperManipulator practically invisible. If your X-Plane screen resolution is smaller, of course, the SuperManipulator cursor will be better visible... but this 4k video does do a nicer job at displaying the quality of the panel. Oh, and I don't think I mentioned this in the video, but starting with this plane, the copilot only shows up when a payload weight threshold has been reached. And BTW, thanks for the support, LAdamson!

You're asking about GPS pop-up? The conversation above was about the autopilot pop-up, but below, there's also instructions on how to assign a keyboard shortcut to the GPS pop-up, if you wish. For the autopilot pop-up to be enabled, you go to the avionics.lua file; there's a line that looks like this: --local BKAP = subpanel {position = {38, 460, 550, 131 }; command = "xap/panels/2"; description = ""; noBackground = false, components = {BK_AP {position = { 0, 0,550,131 } }; }; }; Just remove the two minus signs from the front of the line and save the file. This now enables you to launch a pop-up autopilot window via keyboard shortcut. Which keyboard shortcut? Well, that's one you'll have to customize in X-Plane's "Settings>Joystick & Equipment>Keys" window. You will be looking for a CUSTOM command (so it's not one of the commands already listed by default at the right), so you'll have to click on the little square box above the text box at the top right of the window, which will open up a file browser. Browse to the following path: xap/panels/2 and bind your keyboard short cut to that. This should allow you to press the assigned keyboard shortcut to open the autopilot window. To assign a keyboard shortcut to the GPS as a pop-up, you can simply select the command from the list of X-Plane default commands: sim/GPS/g430n1_popup Oh, and for those of you who bought the plane already, you may find this video helpful in understanding the new SuperManipulators. (and for those of you who haven't bought it yet, I hope you find this video enticing.

You can quite easily enable a "hidden" pop-up autopilot, simply by commenting in the relevant line in the "avionics.lua" file, and assigning a keyboard shortcut to the corresponding SASL pop-up window.

Carenado has invested a ton of time and energy into creating the most flexible and intuitive manipulators for X-Plane possible. The PC12 has a new "super-manipulator", which allows for: -click, for discrete individual value changes (registers on mouse-up, in order to allow for the following other modes) -click-hold, similar to X-Plane's default. (Click and click-hold modes rely on where the user clicks: top/right of a knob yields increasing values, bottom/left yields decreasing values.) -click-drag vertically, for rapid increase or decrease of values. (independent of mouse starting position.) -click-drag horizontally, for fine-tuning of values. -scroll. This will be a standard in future Carenado planes, and the above-mentioned idea is also in its design phase, although no ETA has yet been established for that feature. This implementation allows users to simply manipulate knobs and handles in exactly the way they prefer, or experiment with different techniques.

And I am currently in Minneapolis airport, about to board my flight to Sao Paulo... On 3.5 hrs of sleep. I'll be on holidays for around 6 weeks, but I'll be keeping an eye on the forums nonetheless.

You must load the plane having sized your xplane window to the exact dimensions you intend on using the plane for. At load time, the panel configures its dimensions according to the xplane window's currentdimensions and, by extension, affects the availability of click spots.

On which plane(s)? The GNS430 click spot for swap is actually larger than the visual button. Not sure if parallax plays a role for you.