Jump to content
The simFlight Network Forums

guenseli

Moderators
  • Posts

    464
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by guenseli

  1. Hello Pete,

     

    Majestic Dash 8 has implemented a fix assignment that steering tiller is at the same axis as ailerons.

     

    However I find this really practical and tried it with NGX etc (meaning bigger planes with separate tillers) and I'm happy with it, because in that way, I could "simulate" the use of a separate tiller in a way instead of using rudder pedals.

     

     

    Now, as I have ailerons and steering tiller via FSUIPC at one axis, is there any possibility to disable ailerons as long as the aircraft is on ground?

     

     

    many thanks,

    Guenter

  2. Hello,

     

    here is a LUA script:

    -- Assignments valid for P40 and Spitfire
    
    
    
    -- rounds the integer
    function round(num)
    	num = tonumber(num)
    	if num == nil then return 0 end
        if num >= 0 then return math.floor(num+.5) 
        else return math.ceil(num-.5) end
    end
    
    function round2 (num, idp)
      num = tonumber(num)
      if num == nil then return 0 end
      local mult = 10^(idp or 0)
      return math.floor(num * mult + 0.5) / mult
    end
    
    
    
    acftname = ipc.readSTR("3D00", 35)
    
    ------------------------------------------------------------- Spitfire
    
    
    elseif string.find(acftname,"Spitfire",0,true)
    then
    
    	var = round(((ipcPARAM+16384)/32768*10)/2)
    	--ipc.display(var)
    	--ipc.sleep(50)
    	ipc.writeLvar("L:Eng1_RadiatorLeverPos", var)
    
    
    
    ------------------------------------------------------------- P40
    
    
    elseif string.find(acftname,"P-40",0,true)
    then
    
    	var = (ipcPARAM+16384)/32768*100
    	--ipc.display(var)
    	--ipc.sleep(50)
    	ipc.writeLvar("L:Eng1_RadiatorLeverPos", var)
    
    end
    

    Copy that code, insert it into Notepad (Editor) - NOT Word etc.!

    Save it into your Modules folder, name it as you like, e.g. Radiator.LUA

     

    Simply open FSUIPC and choose "send to FSX axis" and select "lua Radiator"

     

    that's it!

     

     

     

    EDIT: as you can see, that code is valid for P40 and Spitfire

  3. Hello Pete,

     

     

    I have Flight1's Soundstream (a tool to keep FSX sound active, even FSX window lost focus)

    My problem is, that I have some addons, where soundstream does definitely crash FSX. Best example is A2A's B17G

    Of course I asked Flight1 support and the addon dev's, but each says the other one have to fix it.

     

     

    Now, what I want to do is - when one of these addon planes is loaded - to disable (kill) soundstream.

    Problem is, I do not find it as task in task manager or anywhere else.

     

     

    My question is now:

    If soundstream.dll is started with dll.xml is there any way to kill that from inside FSX?

     

     

    many thanks,

    Guenter

  4. Hello Pete,

    I have this issue a long time now, but never cared about.

    Now, that I want to run some more programs, I bring this up, hopefully we find a solution.

    I'm on 4.90 of course and have Win8 Pro with full Admin rights etc.

    These are my lines in FSUIPC4.ini:

    [Programs]

    Run1=CLOSE,F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\AISmooth.exe

    Run2=CLOSE,F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\Linda.exe

    And that is the error I get every time:

    468 FSUIPC couldn't run: "F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\AISmooth.exe" [Error=193]

    468 FSUIPC couldn't run: "F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\Linda.exe" [Error=193]

    I have also tried it with and without quotation marks.

    Both programs run, if I copy the path's above into "Run" ...

    Other programs like Run3=CLOSE,D:\Aerosoft\Launcher\aeroSOFTLauncher.exe do work ...

    I tried of course also compatibility modes ...

    Many, many month ago this was all working, can't unfortunately say what has changed or if it's simply a WIN8 thing ...

    Any ideas?

    many thanks,

    Günter

  5. I don't know if you have also a german OS, but there it is "kritischer Abbruch".

    Roughly translated as "critical break" ...(?)

    EDIT:

    AH, my answer doesn't make sense.

    You need of course the name of the WAV: windows forground.wav

    But I have WIN8 (and you not, because I know you hate it :mrgreen: ), don't know if the names of the files are the same...

  6. I think I can't help you there ... such timers are the worst scenario you could have.

    Just try and error, but there are some addons with such timing sequences where I ahve to give up also ...

    But you can of course send such a timing signal also, e.g.

    L:EX500_LocalTime = 10000

    or whatever.

    I still wonder why paul still haven't discovered the LINDA LUA hunting abilities ... :rolleyes:

    Live could be so easy ...

  7. Just to be sure:

    You have tried it with "GAUGE_ANUM_MASTER_CAUTION" ... set it to zero or 1...?

    That's always a bit odd to give tips when I ahve no access to the addon itself.

    Such timings could be a real pity.

    I can only highly suggest LINDA to gather the LUA variables.

    With LINDA you have a list of all variables in the GUI, could click and test each single variable.

    And you have with the LINDA console a kind of live monitor to see what happens if you press a switch in the planes VC.

  8. Ah, that is why I said I'm no programer!

    The obvious does not catch my eye ...


    ipc.display("PARAM TEST START")
    ipc.sleep(2000)
    if ipcPARAM == 1 then
    ipc.display("PARAM 1")
    ipc.sleep(2000)
    elseif ipcPARAM == 2 then
    ipc.display("PARAM 2")
    ipc.sleep(2000)
    end
    ipc.display("PARAM TEST END")
    ipc.sleep(2000)
    [/CODE]

    this is working.

    LUA is [b]CASE SENSITIVE![/b]

    The correct command is [b]ipcPARAM[/b], not ipcparam.

    Same if you have Variables: [b]Var [/b]ist the same as [b]var[/b]

    :razz:

  9. Thanks Pete for your searching here.

    Unfortunately I have not much time this and the next days.

    But I have decided already to reinstall the complete thing, anything else would not be a good solution.

    Just have to find time for it; but I'll report back!

    Why you have so much problems with WIN8 I do not know.

    The hidden shut down is rubbish, yes.

    But your low frame rates I can't confirm. FS is not running better or smoother, but in no case it's running one frame bader.

    The rest of the system is running a bit better.

    My conclusion for WIN8 (maybe someone reads this):

    If you are happy with WIN7, stay there. The difference, especially for FSX is not that much.

    If you have a bit fun of trying out new things, then try it.

    There are still a few things I do not like on WIN8 (shut down, no start menue button, no desktop gagets [yes, I have used them; yes, I found Rainmeter now]). But there are also many features I like so much now that I wouldn't go back (FileHistory, Metro screen for fast information, explorer additions, fast boot and shutdown)

    Hope, I get my issue solved after a reinstall (but will take a few weeks)

    And I hope Pete is making his peace finally with win8 :mrgreen:

  10. Hello Pete,

    did you install Win8 clean, or as an upgrade from Win7? Maybe the registry is screwed up somewhat

    I installed it clean. But as I siaid I have experimented a bit and there was also a hybernation issue (which I had also in WIN7) where I have played much with (without solving it). Therefore I made some registry changings. Maybe this screwed it up.

    Have you disabled controllers completely in FS?

    First not as I do it for many years now by editing the stanrdard.xml and remove all entries for the joysticks (fastest way to unassign them all)

    But yes I have tried this also by unchecking them in the FS menue.

    What I finally wonder about:

    If the error happens, means the controllers have stopped working in FS and do not show up in FS and FSUIPC menues.

    Even when I do not stop FS, but just change to the device and printers window to look at the controllers properties they do show up and work there!?

    I will follow the link above and search around a bit, but I think, the cleanest solution would be a complete reinstall of the OS.

    I thought that would be necessary in only 66 days ...

  11. ok, seems that haven't worked with this debug.

    Here is a log again:


    ********* FSUIPC4, Version 4.853 by Pete Dowson *********
    Running inside Prepar3D on Windows 7
    ... Prepar3D has been renamed as "fsx"
    Module base=62F10000
    User Name="Günter Steiner"
    User Addr="yyyy"
    FSUIPC4 Key is provided
    WIDEFS7 not user registered, or expired
    78 System time = 13/09/2012 19:48:50
    78 FLT path = "C:\Users\Günter\Documents\Prepar3D Files\"
    93 Trying F:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\SimConnectP3D.dll
    93 Found it: trying to connect
    93 FS path = "F:\Program Files (x86)\Lockheed Martin\Prepar3D\"
    327 #### Initialising Dlrectinput Axis Scanning ...
    327 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0"
    327 Found correct joystick Id 0
    327 ... and a "GUID" value
    327 ... okay, Acquired device!
    327 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"
    327 Found correct joystick Id 1
    327 ... and a "GUID" value
    327 ... okay, Acquired device!
    327 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"
    327 Found correct joystick Id 2
    327 ... and a "GUID" value
    327 ... okay, Acquired device!
    327 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0402\Calibration\0"
    327 Found correct joystick Id 3
    327 ... and a "GUID" value
    327 ... okay, Acquired device!
    327 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0"
    327 "Joystick Id" value = 0, not wanted this time
    327 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\1"
    327 Found correct joystick Id 4
    327 ... and a "GUID" value
    327 ... okay, Acquired device!
    327 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0404\Calibration\0"
    327 Found correct joystick Id 5
    327 ... and a "GUID" value
    327 ... okay, Acquired device!
    327 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0762\Calibration\0"
    327 Found correct joystick Id 6
    327 ... and a "GUID" value
    327 ... okay, Acquired device!
    327 joyGetDevCaps for device 7 returned error 165 [000000A5]
    327 joyGetDevCaps for device 8 returned error 165 [000000A5]
    327 joyGetDevCaps for device 9 returned error 165 [000000A5]
    327 joyGetDevCaps for device 10 returned error 165 [000000A5]
    327 joyGetDevCaps for device 11 returned error 165 [000000A5]
    327 joyGetDevCaps for device 12 returned error 165 [000000A5]
    327 joyGetDevCaps for device 13 returned error 165 [000000A5]
    327 joyGetDevCaps for device 14 returned error 165 [000000A5]
    327 joyGetDevCaps for device 15 returned error 165 [000000A5]
    327 #### Completed Dlrectinput Axis Scanning
    327 LogOptions=20000000 02000011
    327 Wind smoothing fix is fully installed
    327 G3D.DLL fix attempt installed ok
    327 SimConnect_Open succeeded: waiting to check version okay
    327 Trying to use SimConnect Prepar3D
    359 VRI port 1 "com3" opened
    795 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    795 Running in "Lockheed Martin® Prepar3D®", Version: 1.4.4747.0 (SimConnect: 1.4.0.0)
    795 Initialising SimConnect data requests now
    795 FSUIPC Menu entry added
    811 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
    811 C:\Users\Günter\Documents\Prepar3D Files\EDDT_Standard.FLT
    811 F:\Program Files (x86)\Lockheed Martin\Prepar3D\SimObjects\Airplanes\Beech_Baron_58\Beech_Baron_58.AIR
    2028 VRI MCP2B ("MCP2 Boeing") detected on port com3
    68110 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    68812 System time = 13/09/2012 19:49:59, Simulator time = 19:48:53 (17:48Z)
    68812 Aircraft="Beech Baron 58 Paint1"
    69155 Starting everything now ...
    69171 LUA.0: beginning "F:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\ipcReady.lua"
    69171 LUA.0: ended "F:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\ipcReady.lua"
    69171 *** EVENT: Cntrl= 66851 (0x00010523), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_1
    69171 *** EVENT: Cntrl= 65701 (0x000100a5), Param= 26 (0x0000001a) VIEW_ZOOM_SET
    69171 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
    69186 LUA.1:

    69186 LUA.1: [INIT]LINDA:: Loading...
    69373 LUA.1: LINDA:: Aircraft: Beech Baron 58 Paint1
    69389 LUA.1: LINDA:: Aircraft module detected: FSX Default
    69420 LUA.0: LINDA:: AivlaSoft library loaded...
    69420 LUA.0: LINDA:: FSX standard library loaded...
    69436 LUA.0: LINDA:: IAO library loaded...
    69436 LUA.0: LINDA:: RealityXP library loaded...
    69451 LUA.0: LINDA:: A2A MAP library loaded...
    70309 Advanced Weather Interface Enabled
    74537 LUA.0: LINDA:: Loading a fallback joysticks config...
    74537 LUA.0: LINDA:: Loading FSX Default joysticks config...
    74553 LUA.0: LINDA:: Module: FSX Default Started...
    74553 LUA.0: LINDA:: Ready to go, Captain!
    74553 LUA.0: LINDA::
    84755 LUA.0: LINDA:: [S] FSUIPC logging bit set: 10
    95332 Sim stopped: average frame rate for last 27 secs = 25.1 fps
    110152 #### Initialising Dlrectinput Axis Scanning ...
    110152 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0"
    110152 Found correct joystick Id 0
    110152 ... and a "GUID" value
    110152 DirectInput8Create failed, return = 80040154
    110152 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"
    110152 Found correct joystick Id 1
    110152 ... and a "GUID" value
    110152 DirectInput8Create failed, return = 80040154
    110152 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"
    110152 Found correct joystick Id 2
    110152 ... and a "GUID" value
    110152 DirectInput8Create failed, return = 80040154
    110152 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0402\Calibration\0"
    110152 Found correct joystick Id 3
    110152 ... and a "GUID" value
    110152 DirectInput8Create failed, return = 80040154
    110152 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0"
    110152 "Joystick Id" value = 0, not wanted this time
    110152 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\1"
    110152 Found correct joystick Id 4
    110152 ... and a "GUID" value
    110152 DirectInput8Create failed, return = 80040154
    110152 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0404\Calibration\0"
    110152 Found correct joystick Id 5
    110152 ... and a "GUID" value
    110152 DirectInput8Create failed, return = 80040154
    110152 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0762\Calibration\0"
    110152 Found correct joystick Id 6
    110152 ... and a "GUID" value
    110152 DirectInput8Create failed, return = 80040154
    110152 joyGetDevCaps for device 7 returned error 165 [000000A5]
    110152 joyGetDevCaps for device 8 returned error 165 [000000A5]
    110152 joyGetDevCaps for device 9 returned error 165 [000000A5]
    110152 joyGetDevCaps for device 10 returned error 165 [000000A5]
    110152 joyGetDevCaps for device 11 returned error 165 [000000A5]
    110152 joyGetDevCaps for device 12 returned error 165 [000000A5]
    110152 joyGetDevCaps for device 13 returned error 165 [000000A5]
    110152 joyGetDevCaps for device 14 returned error 165 [000000A5]
    110152 joyGetDevCaps for device 15 returned error 165 [000000A5]
    110152 #### Completed Dlrectinput Axis Scanning
    123553 *** EVENT: Cntrl= 65732 (0x000100c4), Param= 0 (0x00000000) EXIT
    132367 System time = 13/09/2012 19:51:03, Simulator time = 19:49:41 (17:49Z)
    132367 *** FSUIPC log file being closed
    Average frame rate for running time of 47 secs = 25.1 fps
    G3D fix: Passes 23809, Null pointers 0, Bad pointers 0, Separate instances 0
    Memory managed: 37 Allocs, 37 Freed
    ********* FSUIPC Log file closed ***********
    [/CODE]

    I have had now a look into the normal FS controls and there my joysticks are disappeared!

    They do work in FS, also when I enter the FS controls menue and go back to FS.

    But entering FSUIPC then makes them stop working.

    So, the fault is maybe not FSUIPC (I never thoght this), the question is, why they do disappear in the FS controls menu?

    And why do they work one time and then the next start not?

    And I have made absolute no changes between: Starting FS, doesn't work, closing FS, do nothing, starting again: works!

    hmmmm...

×
×
  • 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.