Should I disable the GoFlight DLL/EXE in FSX.CFG?

Comments

• admin_pps

  February 2013 edited November -1

  Hi Rob,

  There is no need to disable any GoFlight software, in fact it is best to keep it enabled until I have full support for all their equipment e.g the GF166 in particular.

  Best wishes

  Steve
• robains

  February 2013 edited November -1

  Thanks Steve,

  Kept it enabled, working on setting up a GFConfig specific to Super 80 Professional -- getting FSX OOMs now   will keep working on it.
• robains

  February 2013 edited November -1

  Solve the OOMs in FSX, apparently something to do with Piper Cheyenne X aircraft I was working with ... nothing to do with your tool.

  I'm working on RealAir Turbine Duke right now ... your UI (User Interface) is a little difficult (especially the filter select/display) to work with but I'm making progress.

  Some Bugs:

  1.  In the Detective, the Import/Export buttons are not docking to correct window side so when I resize the window they move over into the events list.

  2.  Seems to only track GoFlight input events once then stops displaying them?  (i.e. when I press a button on my P8)

  3.  Doesn't see my two 166A (but I think you know this already)

  I'm working the following aircraft (in order)

  RealAir Turbine Duke

  RealAir Piston Duke

  Just Flight Bae-146

  Flight 1 Super 80 Pro

  Flight 1 Skyland 182T

   

   
• admin_pps

  February 2013 edited February 2013

  1) This is known, I'll add it to the list

  2) Not sure what you mean by this - stops displaying what exactly and in what part of the program? I don't know what a Goflight event is?

  3) 166A support has never been available - its not a bug, its planned support is way down the line.

  Best wishes

  Steve
• robains

  February 2013 edited November -1

  Hi Steve, some clarification.

  2) GoFlight's assignments -- i believe you call them Bespoke?  For example if I press button 1 on my P8, it will show up in the Detective event list window ... but if I press the same button again, it will not show ever again so long as Detective is open (I have to close and then re-open detective).  Any events I use in the VC via mouse will continue to show, just nothing that's triggered by my GoFlight modules.

  Cheers, Rob.

   
• admin_pps

  February 2013 edited November -1

  Rob,

  Does the VC recognise the event? Detective samples at 4 times a second, so it may miss things, where as during normal operations its 30 times a second. I can increase the sample rate, however I'm more concered that FSX never actions the event - can you confirm and also copy and paste the commands you are transmitting and the aircraft being used.

  Thx

  Steve
• robains

  February 2013 edited November -1

  Steve,

  Yes, VC recognizes the event but it doesn't show up in Detective.  If I click on another switch in the VC and then use the GoFlight switch (meaning I switch with my hand) it will show up in the Detective ... it's as if the detective will only show the GoFlight switch event once. 

  For example if I  press the button on the GoFlight T8 once, it'll show up in Detective, if I press the same button again (a couple of seconds later), it will not show in th Detective.  So in other words, repeat button presses (not rapid, 2 second intervals) will not show up in the Detective.

  Sadly I've ran into another problem, I've created Bespoke events and they show up in the T8 tab (back at your main interface tool, not in detective), however, the documentation says the bespoke event should now show up in GFConfig tool, but unfortunately it doesn't?

  Also, if I exit your Interface tool and come back in, and go to the T8 tab everything is reset - none of my changes are saved?  If I open Detective I see my events are still there so I guess my questions is how do I get the events to show up GFConfig and/or save via you Interface tool?

  I think I must be missing something very obvious?  

  Thanks, Rob.

  P.S.  The events are working when Test them in Detective .. they operate the appropriate switches in the VC. 
• admin_pps

  February 2013 edited November -1

  1) OK, I'll check the issue with Detective - I suspect it is just a sampling rate issue because the commands are being sent OK.

  2) Nothing done in this tool will be accessible in GFConfig, they are seperate products. If the manual indicates otherwise please tell me where and I will correct it.

  3) Your final problem is two known bugs, particularly with the T8 that I need to sort. 

  Best wishes

  Steve
• robains

  February 2013 edited November -1

  Page 9 in User Guide

  "You can now go into one of the GoFlight hardware tabs and under Button Event you will see this Bespoke Event listed and you can assign it to your button."

  I interpreted the above wrong ... thought is was referencing GFConfig.

  I still seem to be missing some fundamental concept issues ... how is your software bypassing assignments defined via GFConfig?  Should I be setting up a GFConfig that is essentially blank.cfg where NONE of the modules have any assignments (i.e. = No Selection)?

  Also, how are Configurations being saved across different Aircraft in your software?  There is no "Save" button?  Sorry, the UI is just really confusing for me. 

  If you need some help on the UI front, please let me know ... I'm a software engineer with 30+ years experience and very familiar with .NET framework.
• BigJacko

  February 2013 edited February 2013

  If I can butt in and maybe save Steve the job:

  1 - it doesn't bypass GFConfig, it simply wires up a GF unit's button-presses to the chosen input into the sim. If GFConfig is not 'hushed up, they will fight, or duplicate each other, or cancel each other out, depending on what each is set to.
  

  2 - yes, you'll need a 'blank' config to hush-up your GFConfig assignments and set them all to either nothing, or Project-Magenta blanks. This way, GFConfig will 'do' nothing (i.e. it will pass no codes to the sim when you mess with buttons, etc)
  
  3 - Steve's config files (saved in the Appdata/Local folder, under Pollypot) are XML files (albeit not very human-readable ones at the moment). They contain a block of data outlining the per-aircraft GF-unit settings (i.e. which GF unit is set to what Events or Bespoke Events, per plane), and a second block which contains the Bespoke Events (ie your little 'programs', defined in Detective) and these are also tied to a specific GF-Unit and aircraft (so will only show when that GF-unit and Aircraft is being dealt with).

  The action of changing something, causes the config-file to be updated instantly (I believe). Certainly upon quitting the Interface Tool, the current configuration is written out to the file (if all is well - or so goes the theory... I am seeing a few states where this isn't always the case, but that may well be an MCP-A-only issue).

  Hope this helps

  Neil
• admin_pps

  February 2013 edited November -1

  Don't duplicate or overlap configurations in GFConfig for each device. E.g. assign an action on a T8 in GFConfig and again in the interface tool. You can mix and match but don't overlap or you will get unexpected behaviour. For devices you are configuring with the tool, there should be no settings in GFConfig - leave those blank. As normal, devine a GFConfig for each aircraft you use and only configure the devices you won't be configuring with the Interface Tool (most likely 166A since no support exists yet).

  The settings are saved automatcially. There is a save button on the Settings tab if you want to manually save at any point.
• robains

  February 2013 edited November -1

  Neil,

  Thank you for the clarification ... much needed.  Yes, the XML files could use a little work ... it's going to be one VERY long Value when more aircarft are added and events.

  Steve,

  So for right now the T8 (values not saving) and the 166A's aren't fully supported.  So keep those T8 and 166A settings in GFConfig and the rest <no selection> (and/or Project Magenta).

  Does the Interface tool need to be running at the same time as FSX or will your Goflight Interface Module.dll make that redundent?

  Thanks, rob.

   
• admin_pps

  February 2013 edited November -1

  You will always need both running.