gypsyczar

DISREGARD! I was looking in the sim for actual control wheel movement. Not there but elevator and rudder do move on the Sys page. Only one way to find out......

Must be a miss on my part. I have tried everything to get these axis assigned through AAO. Tried all of the options, Axis, Event, and Variable using two different.controllers. The axis movement indicators in AAO move when the stick is moved but there is no control movement in the sim. Both of the axis assignments are removed in the MSFS controls assignment and FSUIPC has been shut down to avoid and duplicate assignments. I have uninstalled and reinstalled the 737 with no effect. I noticed in one of the Lorby responses that he was using a variable for the Elevator and Aileron assignments. If so which one did you use?

Thank you sir! You supplied the missing link. It was the Tiller and rudder incompatibility. Change tiller to steering set and all works like a champ! Now if I can just figure out RPN. You don't happen to know of a RPN for poets tutorial do you?

That's what I'm using. The ONLY way I can make it work is to also assign the rudder axis using the standard MSFS primary flight controls udder axis assignment. Without that assignment no rudder function at all. Oh well. I'll just remove the assignment from AAO and use iot the old fashioned way. Our is not to reason why......

I am trying to assign the MaddogX rudder axis using AAO. I've tried all of the commands and events with RUDDER in the name but no joy in making the big flap on the back of the aircraft move in the sim, The rudder indicator moves just fine in the AAO axis assignments page but the rudder pedals do not animate nor work in the A/C. If I assign the rudder axis in the MSFS primary flight controls assignment page all works fine. I am mapping the rudder axis through the Thrustmaster TCA rudder slider that works fine on all of the other aircraft that I have. There are no MSFS conflicting rudder assignments. So , looks like it must be a Maddog issue. Has anyone else seen this quaint feature and function and perhaps have a solution?

Hello all, I've only got 40 years in IT and as of yet have not found a more frustrating piece of software than AAO and streamdeck. I have followed the documentation and trobleshooting guide and have not gotten AAo and Streamdeck to synch up so that The fenix can be controlled by Streamdeck. I am using the Fenix streamdeck information from Flightsim.to. It worked when I first added streamdeck but no joy now. XTouch connects with no problems yet no luck with streamdeck. I'm running Win 11 if that makes a difference I have changed my webAPI to 7070 per the troubleshooting doc since the stock is used by another driver. I have opened a range of ports 6500-7500 in the firewall .Would it be possible for someone to post a foolproof instruction to get AAO and Streamdeck working together.? A complete reinstall is no problem. It looks like a webapi problem to me, but i can't find it Thanks, I must be an word not allowed

Thank you, might give it a try

Hey, just where do I find the Stram Deck "set port and apply" button. I've got the same problem as the OP. Everything is sorted except selecting the "Set port and apply" Button

I've looked and can't find an answer. Does AAO and its plugins work on a separate Machine from msfs"

Thanks. I did and it works as explained

I have purchased the software through JustFlight. They provided no key, or serial number to activate the product. I downloaded the last update and now the product is in demo mode and stops working after 20 minutes. How can I fix this?

OK I admit to being a FS inards word not allowed. But all I want to do is program reverse thrust for the Maddog using a Thrustmaster Hots throttle. The AAO documentation does not address this as far as I can see. Just stock Thrusmaster gives a reverse thrust bot but not where I want it. The Thrustmaster has a detenf where one must pull up and then reverse thrust is activated using the throttle motion allowed beyond the detent. Any help would be greatly appreciated.

Thanks. Admiin rights did it!

I have installed the Maddog rebooted with no errors in p3d v52 and have activated fs2crew in the load manager. With the maddog open in P3D the autofeather on/off toggle does not launch the Fs2crew window. I have looked at the maddog panel.cfg file and do not see any changes related to Fs2crew. Anyone have any ideas?

All is well now I seemed to fix it by turning fs3crew off in the LM saving and loading the AC in p3d then turning fs2crew on in the lm, saving and loading in P3d

Here is the panel.cfg So what do I do now? ///////////////////////////////////////////// // Fly The Maddog X // // Panel Configuration file 64bit edition // ///////////////////////////////////////////// [Window Titles] window00=Views window01=FMS CM1 window02=PFD CM1 window03=ND CM1 Window04=Radio panel Window05=Ground/Crew Communication Window06=Speed chart Window07=EFB Window08=PMS window09=FMS CM2 window10=PFD CM2 window11=ND CM2 Window12=Flight Documents Window13= Window14= [Window00] size_mm=335,420 position=6 window_size=0.175,0.324 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10100 zorder=10 type=special gauge00=maddog!VIEWS_SELECT,0,0,335,420 [Window01] size_mm=407,584 position=0 window_size=0.212,0.541 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10101 zorder=1 gauge00=maddog!FMS1,0,0,407,584 [Window02] size_mm=400,318 position=3 window_size=0.208,0.294 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10102 zorder=1 gauge00=maddog!PFD1,0,0,400,318 [Window03] size_mm=400,318 position=6 window_size=0.208,0.294 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10103 zorder=1 gauge00=maddog!ND1,0,0,400,318 [Window04] size_mm=407,591 position=7 window_size=0.212,0.547 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10109 zorder=1 gauge00=maddog!RADIO, 0,0,407,591 [Window05] size_mm=640,480 position=4 window_size=0.333,0.380 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10111 zorder=3 alpha_blend=0.75 gauge00=maddog!GROUND_CREW_COMM,0,0,640,480 [Window06] size_mm=640,410 position=4 window_size=0.333,0.380 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10110 zorder=1 gauge00=maddog!SPEEDCHART,0,0,640,410 [Window07] size_mm=1024,800 position=4 window_size=0.500,0.694 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10107 zorder=1 gauge00=maddog!EFB, 0,32,1024,768 [Window08] size_mm=407,327 position=7 window_size=0.212,0.303 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10108 zorder=1 gauge00=maddog!PMS, 0,0,407,327 [Window09] size_mm=407,584 position=2 window_size=0.212,0.541 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10104 zorder=1 gauge00=maddog!FMS2,0,0,407,584 [Window10] size_mm=400,318 position=5 window_size=0.208,0.294 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10105 zorder=1 gauge00=maddog!PFD2,0,0,400,318 [Window11] size_mm=400,318 position=8 window_size=0.208,0.294 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10106 zorder=1 gauge00=maddog!ND2,0,0,400,318 [Window12] size_mm=763,1080 position=4 window_size=0.397,1.000 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=10112 zorder=2 gauge00=maddog!FLIGHT_DOCS,0,0,763,1080 [Window13] size_mm=726, 57 window_size= 0.3821, 0.0475 position=3 visible=0 ident=1000 zorder=100 gauge00=maddog!md_empty, 0,0,1,1 gauge01=maddog!md_empty, 1,0,1,1 gauge02=maddog!md_empty, 2,0,1,1 [Window14] size_mm=890, 285 window_size= 0.4684, 0.2375 position=4 visible=0 ident=1001 zorder=101 gauge00=maddog!md_empty, 3,0,1,1 [VIEWS] VIEW_FORWARD_WINDOWS= [Default View] X=0 Y=0 SIZE_X=8192 SIZE_Y=8192 Day=255,255,255 Night=233,192,107 Luminous=201,64,64 //-------------------------------------------------------- // VIRTUAL COCKPIT [VCockpit01] size_mm=1024,1024 pixel_size=1024,1024 texture=$screen1 background_color=0,0,0 visible=1 gauge00=maddog!VC_CM1_FMA, 0, 884, 678, 120 gauge01=maddog!VC_CM1_PFD, 0, 0, 570, 442 gauge02=maddog!VC_CM1_ND, 0, 442, 570, 442 gauge03=maddog!VC_NAV1, 570, 780, 390, 44 gauge04=maddog!VC_NAV2, 570, 824, 390, 44 gauge05=maddog!VC_EEDP, 570, 0, 374, 780 gauge06=TrueGlass!Core, 1, 0, 1, 1 [VCockpit02] size_mm=1024,1024 pixel_size=1024,1024 texture=$screen2 background_color=0,0,0 visible=1 gauge00=maddog!VC_CM2_FMA, 0, 884, 678, 120 gauge01=maddog!VC_CM2_PFD, 0, 0, 570, 442 gauge02=maddog!VC_CM2_ND, 0, 442, 570, 442 gauge03=maddog!VC_CM1_VSI, 748, 0, 242, 242 gauge04=maddog!VC_CM2_VSI, 748, 242, 242, 242 gauge05=maddog!VC_CM1_DME, 678, 882, 236, 54 gauge06=maddog!VC_CM2_DME, 678, 936, 236, 54 gauge07=maddog!VC_CM1_CHRONO, 570, 730, 122, 152 gauge08=maddog!VC_CM2_CHRONO, 692, 730, 122, 152 gauge09=maddog!VC_ESDP, 570, 0, 178, 730 gauge10=maddog!VC_FQTY, 748, 484, 260, 246 gauge11=maddog!VC_XPNDR, 814, 730, 188, 68 [VCockpit03] size_mm=1024,1024 pixel_size=1024,1024 texture=$screen3 background_color=0,0,0 visible=1 gauge00=maddog!VC_FGCP, 0, 980, 956, 44 gauge01=maddog!VC_FMS_L, 0, 0, 576, 488 gauge02=maddog!VC_FMS_R, 0, 488, 576, 488 gauge03=maddog!VC_EOAP_L, 590, 0, 434, 258 gauge04=maddog!VC_EOAP_R, 590, 258, 434, 258 gauge05=maddog!VC_LDG_ALT, 830, 560, 194, 140 //gauge06=maddog!VC_compass, 858, 732, 166, 106 [VCockpit04] size_mm=1024,1024 pixel_size=1024,1024 texture=$screen4 background_color=0,0,0 visible=1 gauge00=maddog!VC_VHF1, 0, 512, 512, 67 gauge01=maddog!VC_VHF2, 0, 579, 512, 67 gauge02=maddog!VC_VHF3, 0, 646, 512, 67 gauge03=maddog!VC_ADF, 0, 713, 472, 67 gauge04=maddog!VC_SPEED_CHART, 0, 0, 512, 330 gauge05=maddog!VC_PMS, 512, 780, 512, 244 gauge06=maddog!VC_FQTYAUX, 0, 780, 244, 244 gauge07=maddog!VC_PRINTER_PAPER, 815, 0, 209, 512 [VCockpit05] size_mm=1024,1024 pixel_size=1024,1024 texture=$screen5 background_color=0,0,0 visible=1 gauge00=maddog!VC_EFB, 0, 0,1024, 768 //-------------------------------------------------------- // TrueGlass [Vcockpit06] background_color=0,0,0 size_mm=1024 pixel_size=1024,1024 texture=$MD_TG1 texture00=TG_0, 0,0,1024,1024 [Vcockpit07] background_color=0,0,0 size_mm=2048 pixel_size=2048,2048 texture=$MD_TG2 texture00=TG_1, 0,0,2048,2048 [Vcockpit08] background_color=0,0,0 size_mm=1024 pixel_size=1024,1024 texture=$MD_TG3 texture00=TG_2, 0,0,1024,1024 [Vcockpit09] background_color=0,0,0 size_mm=2048 pixel_size=2048,2048 texture=$MD_TG4 texture00=TG_3, 0,0,2048,2048 [Vcockpit10] background_color=0,0,0 size_mm=1024 pixel_size=1024,1024 texture=$MD_TG5 texture00=TG_4, 0,0,1024,1024 [Vcockpit11] background_color=0,0,0 size_mm=2048 pixel_size=2048,2048 texture=$MD_TG6 texture00=TG_5, 0,0,2048,2048 [Vcockpit12] background_color=0,0,0 size_mm=1024 pixel_size=1024,1024 texture=$MD_FG1 texture00=TG_6, 0,0,1024,1024 [Vcockpit13] background_color=0,0,0 size_mm=1024 pixel_size=1024,1024 texture=$MD_FG2 texture00=TG_7, 0,0,1024,1024 [Vcockpit14] background_color=0,0,0 size_mm=1024 pixel_size=1024,1024 texture=$MD_FG3 texture00=TG_8, 0,0,1024,1024 [Vcockpit15] background_color=0,0,0 size_mm=1024 pixel_size=1024,1024 texture=$MD_FG4 texture00=TG_9, 0,0,1024,1024 [Vcockpit16] background_color=0,0,0 size_mm=1024 pixel_size=1024,1024 texture=$MD_FG5 texture00=TG_10, 0,0,1024,1024 [Vcockpit17] background_color=0,0,0 size_mm=1024 pixel_size=1024,1024 texture=$MD_FG6 texture00=TG_11, 0,0,1024,1024

That fixed mine too.

Looks like we have a bug.......... I would think that the new Maddog beta has either changed or overwritten something that the fs2crew installer needs.

I installed the latest maddog beta (2.0b783} this morning. i reinstalled fs2crew and made sure it was enabled in the load manager. I assigned a hotkey to Autofeather on/off. Loading up P3dV5 and the md83 pressing the assigned autofeather key I get no Fs2crew display. Anything to do with the change log line saying that the panel config would not be overridden if it had been edited. FYI i have not edited the panel config file. This is also posted in the Maddog forum

Resolved. Did an uninstall and reinstall of NGXu and Fs2Crew,

For some strange reason the main panel has decided not to appear when called. The green bar is there showing my input but no main panel. This may be related to the P3DV5 NGXu udate but I can't be sure of the timing. Below are the panel config entries for Fs2Crew. Any ideas? //FS2Crew windows [Window15] size_mm=1069, 51 window_size= 0.5567, 0.0425 window_pos=0.00,0.05 visible=0 ident=1000 zorder=100 sizeable=1 gauge00=FS2CrewNGXu!FS2Crew_MainPanel, 0,0,1069,51 gauge01=FS2CrewNGXu!FS2Crew_Audio, 20,20,5,5 gauge02=FS2CrewNGXu!FS2Crew_VoiceMain, 10,10,5,5 [Window16] size_mm=402, 639 window_size= 0.2093, 0.5325 position=3 visible=0 ident=1001 zorder=105 sizeable=1 gauge00=FS2CrewNGXu!FS2Crew_SecondaryPanel, 0,0,402,639 //FS2Crew windows end

Just a small thing but, as many times as I have tried, I have only managed to get the Pm to start the engines once in all my tries no matter how nicely I ask, Are there any specific conditions required to make this work?

My eyes say thank you!

Is there any way to increase the size of the onscreen control FS2Crew widget in 4k for the Dash8? Works just fine for all of your other products. Too small for old eyes even with glasses.

Found the answer. Must reinstall the Dash8. With all due respect. Unless there is some absolute technical reason why Fs2Crew must run in the main P3D folder you should probably modify your software to use the Addon.xml method like the rest of the P3D software universe. Makes a P3d upgrade much less of a problem.