Home

GoFlight-Lua Scripter
What's the current version?
 

THERE IS NO RELEASE DATE FOR GFLS

 Progress Reports

Program Features    -    Frequently Asked Questions    -    Registration

The GoFlight-Lua Scripter (GFLS) is currently under development.
Any screenshots depicted are subject to change.

For question/comments and/or suggestions, contact us at gfls@anadrac.com

Minimum System Requirements
 GFLS doesn't really have a minimum requirement,
except for the operating system must be USB capable.

I'm just posting the requirements for FS2004.

Windows XP-SP3
450MHz Processor
128MB RAM

Designed on WinVista-SP2-32
Tested on WinXP-SP3-32 & Win7-SP1-64

This download button is for my testing purposes ONLY.
The software won't work for you, so don't even bother to download it.

PROGRESS REPORTS

22JAN2012
        I've been receiving requests for GFLS.  I'm still developing the software. I'm currently having difficulty with saving the configuration and getting it to recognize when modules are added or removed.

9DEC
        I just received my 4 port KVM today to accommodate my XP, Vista & Win7 machines. Now I just have to wait to pick up my "new" 2yr old Apple machine!!!

30NOV
        I picked up my new computer, Win7-64bit 3.1GHz Quad Core computer so testing on 64 bit systems can begin.

28NOV
        I've completed trimming and streamlining the Install and Uninstall files although I think I still need to work a little more on them.  I've also converted all my variables, subroutines and functions to conform with Hungarian Notations. Whew!  I've also been tweaking the Registration system.

22NOV
        I've been getting some confusing results from my Error Handler since my last tweak of it. So I've spent the last 2 hours designing a new Error Handler. I've introduced a "Path Tracker" which keeps track of the order in which subroutines are called, so now I should be able to figure out which subroutine called my problem child.

18NOV
        OK!!! As long as I'm not trying to get my software to detect the inputs from the modules, Everything is heading in the right direction.
                - A few more tweaks to the code generator
                - Update the offset database
                - Link the control numbers to offsets

16NOV
        So, I think I'm going to abandon the idea of using the modules for inputs.  The program is stable if I'm not expecting inputs from the modules. When I try to select a button on the MCPPRO, the API sends a release signal also, so keeping a button selected is not working.

14NOV
        Well, I think I'm stuck. Having a problem with variable data types not available in VB6.

9NOV
        I received the first three modules yesterday so I'm back working on the GF-Lua Scripter. I took a break to pursue other hobbies. I was running at full steam at the beginning and was burning myself out. But I have about three weeks before I need to return the modules so I'm back on track, not quite at full steam.

4OCT
        Received an e-mail from Tony at GoFlight and he's considering sending me the units I don't have. I'm very thankful!!!

3OCT
        Been taking a break... family visits & stuff. So how can I temporarily get my hands on modules I don't have for testing?

23SEP
        Now that I've had the chance to tinker with the SDK, I'm writing new code to allow the user to press a button, throw a switch or rotate a dial to select which function goes with what control. I have yet to incorporate the LGT2 button assignments... but thanks to "Porchpup" I have them.

9SEP
        I need your help. I need button responses from the following modules...

                GF-LGT2
                GF-MESM

8SEP
        I keep setting myself back because I find better ways of doing things. But I am making progress!

7SEP
        Double "Kudos" to Gene. He gave me the code to read strings from FSUIPC!!!!!

6SEP
        Many thanks to Gene Buckle for "talking me into" moving to VB6!!!

5SEP
        I've been tinkering with getting my on-screen modules to display the values coming from FS via FSUIPC.  I started with the Gryo Heading and IAS. You can take a peek at a screen shot HERE.

3SEP
        Many more thanks to Pete Dowson and Paul Henty. Ignorance is NOT bliss!!! They helped me sort out my Data type problems.  However, My SIR-ADM application is launching and I'm already getting error reports and support requests.  I may have to take a little break from this project.

2SEP
        I've been hung up on trying to get my software interfacing with FSUIPC so you can see your results before writing any scripts. I'm having trouble with data types, formats and general stuff I don't understand.

31AUG
        Only six more modules left to write mouse move routines for... Then I gotta check that each option is working properly... then I can get into making this thing produce Lua script files!!! Maybe in Sep, I'll have the basics done!

30AUG
        With the new variable structure, things are more streamlined and uniform, I have a couple modules converted to the new structure... progressing.  I copied over my Product Code routines from another program and plugged them in. I also have the "encoder" working. I revamped my Product Code Generator. Well, back to making those changes,

28AUG
        I've decided to focus more on the customizable modules first, GF-166, GF-45, GF-46, GF-P8, GF-RP48, GF-T8 but not necessarily in that order.

        I've hit a snag... The variable structure I setup for keeping track of offset assignments doesn't permit me to distinguish between Displays and LEDs. I didn't realize it until I tried to program the GF166 which has both where they could serve different purposes. Back to the drawing board and a re-write.

27AUG
        I took a day off to regain my sanity.  I've just finished the loading and saving of the module configuration, including function assignments. Whew!  Now, back to Mouse Move events.

        Taking a different approach on assigning functions to controls. Instead of using Control Numbers, I'm going with Offsets. It's working much better. I had to change my config file format which resulted in how it's loaded and saved. So far it's working, but there's still a glitch that I haven't tracked down yet.

        I compiled an executable... Silly me for thinking it would work on another machine! Can't find the problem until I implement the Error Handling routine. I guess that's my next task.

        Switching Tab controls... the good one doesn't work on other systems

        It's almost midnight and I have a basic Error Handling routine working which, allowed me to find my errors and get a compiled package working on my XP system.

25AUG
        Making progress by leaps and bounds... It's so much easier if I just concentrate on the bare basics of what function turns on this LED. Without thinking about how to keep track of which control operates what function, it's all coming together nicely.

24AUG
        I setup the status bar with indicators for FSUIPC and the FltSim In addition to which module is selected and which is being hovered over. I got rid of the moving tooltip showing which modules the user had the mouse over, it kept getting in the way.  I've complete the "snapping" routine to snap one module to another. It only works when you snap one module UNDER the other. I'm thinking about doing a top snap too. 

        I started creating a "Constants" list for modules. That's going to be a pain switching between Joy#s and Unit#s.  Got valuable info from "KAPTEJNLN" on the GF-MCPPRO. If only I could get my hands on one.

        I'm going nuts... I've been happy with the idea that each joystick input and provide 32 button inputs... Leave it to the MCPPRO to have 100 button inputs! So how do I re-code to account for that?

23AUG
        I've just completed re-creating all the modules for display purposes. I didn't like the photos I had. Click HERE to see them.  I've also complete the code to load and save modules arrangements. I think I've also decided on a interface. Below are screenshots.

20AUG
        I'm getting frustrated with how to arrange the GUI. I keep changing things and screwing up the code.

TO DO LIST

  • Update the list of memory offsets.¹

  • Create a "database" of all inputs a module is capable of. ² (in progress)

  • Determine "essential" functions to start with.

  • Sort out functions pertaining to buttons, switches and displays. ²

  • Design "Preview Lua Code" tab.

  • Implement Error Handling routines.

  • Finish writing the Offset Converter and make it a Offset Database Manager. ¹

  • Link Offsets with Controls (Zinny)

  • Implement online version checking.

  • Program registry entries

  • Figure out how to convert Byte strings from FSUIPC!!!

  • Finish MouseMove events for large module displays (in progress)

    • GF166

    • GF45

    • GF46

    • GFATC

    • GFEFIS

    • GFLGT

    • GFLGT2

    • GFMCP

    • GFMCPPRO

    • GFMESM

    • GFP8

    • GFRP48

    • GFSECM

    • GFT8

    • GFTPM

    • GFTQ6

    • GFWP6

  • Build FlightSim Controls database file

  • Redesign modules displays

  • Make a Snap to module routine

 

Top Priority | Second Priority | Third Priority