Jump to content
The simFlight Network Forums

Artem Crum

Members
  • Posts

    71
  • Joined

  • Last visited

Posts posted by Artem Crum

  1. Hello Pete,

     

    I've stumbled upon strange situation.

     

    This simple command crashes the P3Dv2 to desktop. No other Lua scripts are running simultaneously, the only script executed is a file with this one and only string (script is executed by 'Lua testscript' command assigned to joystick button):

    ipc.display('Test')
    
    Windows Error log:

    Fault bucket 73316406496, type 1
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: Prepar3D.exe
    P2: 2.2.10437.0
    P3: 533d6c08
    P4: FSUIPC4.dll
    P5: 4.9.3.4
    P6: 537f5a02
    P7: c0000005
    P8: 00013586
    
    =========================================================
    
    Fault bucket 73349789338, type 1
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
     
    Problem signature:
    P1: Prepar3D.exe
    P2: 2.2.10437.0
    P3: 533d6c08
    P4: FSUIPC4.dll
    P5: 4.9.2.8
    P6: 52d1eec2
    P7: c0000005
    P8: 00012b3e
    P9: 
    P10: 
    
    FSUIPC4 versions tested: 4.9284.934a
  2. No-no, if it allows only fixed choices and nothing more, then it probably doesn't worth it. And I'm actually not ready to describe what I need exactly. I know about the "ask" function, and will check what it can do for my purposes.

    Right now I'm working on scripted failures engine and don't want to mess with dedicated GUI for it, so I need some space to display current systems status (will try to use Lua display for that purpose) and some instruments for user interaction to set things up (like setting max speeds for different flaps positions for current aircraft, switching some failure modules on/off and so on). This could be done with XML-gauge, but it will require to edit panel.cfg for each aircraft and I don't like that, so I'm looking for an easier and yet universal solution.

  3. There is a program you may know - AivlaSoft EFB. I believe they do it through the SimConnect, but they've managed to create ATC-like window with their own content - which could be a great feature for the future versions of FSUIPC, allowing scripts and other addons like Radar Contact to communicate with user in more natural way. Any chances?

    Here is the screen:

    fsxintegration.jpg

    As for Lua Display window position, I can just save it's position on script exit, allowing user to chose it's place for himself... so, not a big deal right now.

    p. s.

    Multiple Lua displays will be cool too! And with control over fonts, colors and so on... (yeah, our wishes are endless!)

  4. I'll probably add it as an optional parameter to the ipc.setdisplay function, making the position and size optional too. Maybe read the name with the ipc.getdisplay function too, so nice cooperative programs can save and restore it.

    That would be great, thanks.

    Another question on the same topic - is there a way to get current display's resolution? I. e. I want to place Lua Display window in a lower left corner.

  5. Hello Pete,

    Is there any way to create and control multiline message window inside FSX via Lua script?

    I know, I can create two types of messages - the green scrolling line by sending data to special offsets and the "LUA display" box by using ipc.display() function. But can I create something like internal ATC window or at least Radar Contact's message box?

  6. Hello again,

    I know it's not directly related to FSUIPC, but it's related to FSX internals.

    I need some way to detect, if it is FS-Recorder replay is going on right now or not. It's all about Lua-scripted failures engine I'm creating. Right now it cannot distinguish "real" flight from FSR's replay, so all the damage/wear counters keep increasing while in replay, which is bad.

    I've asked the same question on FSR support forum, but it doesn't looks like I'll get any answer there.

    Any ideas?

  7. I'm sorry. My "previous" is 4.756, "latest" is 4.824.

    Several users reported the similar problem after updating from 4.80 to 4.82. Script stucks randomly (i.e. after opening FSUIPC settings) which was never happened on 4.80 and earlier versions.

    UPDATE: got the confirmation that 4.80 works fine and doesn't stuck the script on aircraft change, but 4.82 - does.

  8. Hello Pete,

    Here is the example script (test.lua) which is not working as expected:


    local i = 0

    function test ()
    i = i + 1
    ipc.log(i)
    end

    event.timer(100, 'test')
    [/CODE]

    1. Load any flight

    2. Start script by "Lua Test" joystick button assignment in FSUIPC

    3. Check fsuipc4.log for constantly increasing numbers

    4. Change current aircraft to any other

    5. Script STOPS working after new plane is loaded (no more numbers in log)

    On previous versions of FSUIPC script continues to work after plane change. On latest version I have to restart script manually each time I change aircraft while in flight.

  9. Hello everyone!

    I'm working on a simple failures engine based on Lua scripting (modular and configurable as LINDA). Main logic is operational already, but I have a problem simulationg some failures.

    FSX has it's own failures settings and it does allow to fail one flap separately, and it works fine. I'm trying to do the same thing with my script, but I cannot find any posibility to un-pair flaps to control them separately. Is there any way to achieve this?

  10. So if all the devices are handled that way, wouldn't it be best for users to stop FSUIPC scanning them all the time?

    Not sure what do you mean. But you should note that most of LINDA users also have several joystick assignments made within FSUIPC and ALL the axes assigned through default FSX input or/and FSUIPC calibration/assignment fascility.

    Another idea! Derek, try to remove any assigments done in LINDA for NGX and Default FSX aircrafts. May be this is some kind of flood problem when some button sends to many presses/releases in a short period of time.

  11. Pete,

    - LINDA GUI (linda.exe) - is the only part of the system which is dealing with HID-devices directly.

    - Lua scripts in LINDA are only using COM-port interactions.

    - actions.lua script is just a collection of Lua functions which are called only when some button is pressed. There is also a little part of it which is executed by timer, but it's not really big to cause any problems.

    So, if error is still there without linda.exe running, then this is Lua scripting problem. And the only idea I have, is some kind of memory limitation for Lua scripts in FSUIPC.

  12. Hello Pete,

    All your previous updates made by my request are now used in LINDA with intense.

    I know, I'm getting greedy, but.. I have another one "question". :grin:

    At the moment event.param + LuaValue accept only the numeric values. FSUIPC GUI allows to enter strings in the parameter field but, doesn't save them and doesn't send. Can this be changed to allow sending a string value to the Lua script?

    With regards

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.