Perfect??.. No, but I do have a sample that I am continuing to work on and tweak. Over this weekend I’ll try post some screenshots and or a quick video.
No instructions were with mine as well. I just figured it out through trial and error. lol
Okay another issue. Some of the controls work while others don’t. I turn the heading and altimeter dials and they work and change the pfd values. But none of the soft buttons like CDI on the bottom work. And the Nav dials don’t work. The buttons all have a click sound but they don’t do anything. I am using the latest mobiflight 8.0 or about that. It’s in the community folder. Should I try 7.10 or am I missing a setting or did I install something improperly? Anyway to see if the event is going through? Thanks!
Edit: I had the MSFS2020-module folder in the community folder. I corrected that and put the contained folder there and now there is no response from the pfd. Do I have to do something else?
Edit 2: There is an install script in the MSFS2020-module. Does it have to be executed?
This isn’t a helpful post, but I just really wanted to take a minute to say thank you to everyone who contributed to this solution. I have a touchscreen running as my MFD with the Knobster all working great thanks to you folks. This feels so close now to being a fully functional hands-on IFR trainer and I love the flexibility of the Air Manager based setup. Kinda regret buying the real sim gear G1000 for the PFD now as it’s a bit redundant.
Here’s to more G1000 improvements - Xplane still hands down wins on pure accuracy, but we’re getting so close to parity here it’s untrue.
1 Like
A couple of things:
-
When you installed Air Manager, did you also download and install the beta service plugin that goes with it?
-
The aforementioned AM service plugin is a bit unstable at the moment (beta, so expected). If it stops responding, it’s because the service crashed. You can fix this by running the plugin installer again, or by going into your Windows services panels and cycling it there. Personally, I find the reinstall much quicker.
I think reinstalling the plugin worked. But I am noticing some inconsistency with the knobster. After using it a bit for altitude and heading, I notice that every so often, a value is skipped or goes backwards. Then it could jump forward. I’ll have to try without the knobster but I think it will be okay without it.
Edit: I started the panel again and the knobster value jumping seems to have gone away. I’ll have to try a few more times. Not sure what happened.
Both my Winmaxit monitors seem okay but I need longer cables for them. Also I’m not sure if I should just leave the two monitors at the bottom of my main monitor or buy mounts that can suspend them to the left and right of my monitor. As you can see my desk is a mess now and I put one monitor away. If I suspended the monitors in air, I would get rid of the android tablet on the left and the extra mounts that are hanging out. But I am not sure how it would react to touch inputs with such a mount suspending the monitors in air. What do you think?
So here is one option for panning, The Chevrons will pan the map in any of the four directions…
Another option is to move the icons out to the edge of the Map area. The trouble with that scheme is accounting for scaling. Its just lots of math that can be off by 2-3 pixels in some cases. Centering on the map area is easier. The Icons are only visible when in panning mode.
Also Note these Icons are FAR too Opaque! The new set is more transparent
1 Like
I would recommend getting a nice heavy VESA arm for your main monitor and moving it up and out of the way somewhat. It will clear up desk space under if for one, and will allow you to raise and lower it easily for non-sim use.
I wouldn’t put the Wimaxit monitors on arms. You want those as steady as possible. If there’s any wobble, you’ll find yourself double tapping buttons accidentally. I’m currently having that issue with my second monitor as it’s mounted on top of my Logitech AP panel. The frame isn’t very steady compared to the yoke (cheap plastic). Often I touch a ‘button’, which causes the monitor to wobble, causing a double press. I would imagine arm mounting them would do the same.
Earlier I checked out Yves Levesque’s G1000 bezel at the link below. He has the joystick enabled in his and it works. It could give you some ideas perhaps.
PS: Still using your bezel. I don’t like the knob turn acceleration he has in his. Causes me to overshoot settings all the time. He’s got some interesting code in there though that may be of interest to you.
This is THE EXACT reason I did not mount my Portable Touch monitor on an Arm. My 21 inch HP touch screen is on an arm Mount and has enough mass, and the mount is firm enough that Touching it does not affect it. However I had my second Knobster attached to ithje touchscreen for about 2 days and relocated it as every push moved the display, bad bad idea that was 
1 Like
I will take a look at his implementation. I do have a Knobster imp I was playing with but found it did not work as well as panning the screen with touch. That being said it well be a personal preference thing…
I did post the above protoype on another board and the Pureists lost their ■■■■ whining that this breaks how inauthentic the mode is and is should be stricken from the web… People taking cockpit building WAY TOO SERIOUSLY.
It was a good laff tho
I was thinking to introduce a global acceleration user setting so people could tweak it to suit their wishes… Most of the Acceleration values are the same so it might work OK…
I like your panning solution. It seems well thought out.
Yes they do! lol I don’t. I value functionality, as long as things remain at least somewhat true to life. Sometimes, short of owning a physical bezel, you have to make some compromises. Although Yves’ implementation of the joystick may be something you’d want to model yours off of. I like his implementation for use, but looks bad IMHO. I think it needs work graphically. I’m pretty sure something like that would satisfy even the purists on the other forum.
This would most definitely work. I don’t like the acceleration. I count clicks so I don’t need to keep my eyes on the numbers for tuning my radio. When I need to tune to a frequency, I look at my standby, and I know how many clicks of the detent I need for each knob to get to my target frequency. Acceleration just throws that right out the window. Perhaps it would be useful for the heading, but even then, I’d prefer not have it at all. As long as the option is there to not use acceleration, I’m happy.
BTW, noticed in your latest lua script on GitHub (finally got a chance to try it tonight), the baro setting has a bug.
When set to either the G1000 or Kohlsman setting, nothing happens. When I have it set to “both”, it increments the baro by 2 per click instead of 1.
I commented out the line for Kohlsman_INC and Kohlsman_DEC under the “both” section in the script and only left the G1000 Mobiflight commands. It seems to adjust both the G1000 and Kohlsman anyway, and correctly increments by 1 per detent as it should vs 2.
Thought I’d let you know.
I find that I have to make the g1000 display windows a little bit larger to fit in the bezels at the default size. Do you guys use fancy zones for this? Also how do you get rid of the “title bar” at the top of the g1000 displays because they are windows. Thanks.
I’m thinking of just using the included cover stands and putting the Winmaxit displays in front of the main monitor. I ordered some longer cables because the included ones are too short. The Sabrent 10 port USB hub seems to power them okay. Thanks for the recommendation.
Yes Exactly. So here is what I have Touch Screen Wise:
I have 2 touch screens
My First Screen is an HP L2206tm 21 inch 1080P running Scaling at 100%
My Second Portable Monitor is a 15" 4K monitor, running scale to 200% (effectively 1080P in desktop some respects) but FS2020 still sees it at its native resolution.
My HP G1000 MFD Bezel is set to 1223 X 792 pixels which yields a physical image of approximately 300mm X 190 mm on the HP display. That means when I pop it out and drag it over to the HP it does not need to be resized to fit into the Bezel. It’s a legacy holdover from before I understood Fancyzones value. At that Size I think it is close to the physical size of a real G1000.
On the 4K Display , the PFD Bezel is 1371 X 890 Pixels yielding a 245mm X 160mm onscreen image. It is physically smaller but it is very close to my my keyboard and it is very comfortable to use. Even the softkeys are a good size though they are tighter than on the HP. When the PFD screen image is popped out and dragged over to the 4K display it is MUCH smaller than the Bezel and Fancy zones resizes the image to the zone it is being dropped into.
On my computer this yields a pretty decent framerate drop but I still get 30FPS in most cases, with no lag or stutters. I have not done any recent benckmarks with no popouts. I run High-Ultra graphic and see a mix of GPU and CPU bound with Pwr being my graphics limiter. I could Overclock the graphics quite a bit and have seen 50+ FPS in the past but recent updates have caused FS stability issues (crashes CTD) so I don’t bother.
Anyways back to your question re FancyZones. It really comes down to your preference for the physical image size of the Bezel and would suggest you decide that first. Then once you do, you can setup fancyzones to fit that window and get rid of 90% that setup positioning frustration you used to have. I have never benchmarked the framrates to see what the impact of scaling the popped out images is, but if you have a sufficiently powerful PC and graphics it may not make too much difference.
Thanks for the info. Do you also know how to get rid of the top title bar from the windows?
I find that if I size the G1000 bezels the full 1080 height of the monitor, my pop out windows fit in it perfectly without the need to resize. This may be a function of what resolution your main monitor is though. Mine is 1440.
As for the title bar, I have mine hidden behind the bezel. If you enable “Always on top” in the settings as per the image and place / size the window properly, the actualy MFD/PFD screen will fill the gap in the bezel fully and the window title bar will be hidden by the top of the bezel.
If your sizing isn’t right, Fancy Zones will fix that for you easily though. I don’t have to use it with my G1000, but I do for the GNS530/430 and my AP and transponder windows on my C172 Classic.
Hmm strange. My main monitor is 1440p as well but it comes out a bit small when I move it to the 1080p Winmaxit. Do you have scaling on anywhere? There seems to be some voodoo involved.
1 Like
No scaling anywhere. Below is the size at which I run my bezels in AM and my pop out windows fit perfectly.
But who knows why it’s like that for you. The only consistent thing about MSFS is how inconsistent the experience is from user to user. lol
But Fancy Zones will fix that for you. It’s a bit of work to get it set up initially, but like Phil said in his last post, once you have it configured, it takes 90% of the work out of future setups since it’s a matter of just undocking the instrument windows, holding SHIFT, and dragging them where you want them.