AngeloCosma
-
Posts
49 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by AngeloCosma
-
-
23 minutes ago, Pete Dowson said:
Look in the bottom right section of the "Information" options, the section entitled "Miscellaneous Text". The entry called "Information Text" should be enabled or messages from many add-on programs (not just FSUIPC's plug-in facility) won't be seen.
It's really only desirable to turn that off if you are redirecting them to another display, possible via WideFS.
I don't understand how you would expend much effort re-enabling an option in P3D (which is actually on by default). You must have expended effort turning it off!
Pete
Thank you for that, yup it was unticked! I didn't even think twice about it, I will reinstall the dll and test. Thank you.
-
On 1/18/2020 at 12:49 AM, Thomas Richter said:
Hi,
I don't think the button will be noisy, just the axis doesn't stay constant at the last value. But with a little dead-zone it will be constant at idle.
It would only effect some add-ons like PMDG, . . ., as those have to be assigned with direct to FS with no calibration in FSUIPC.
Thomas
You may have answered this question, can this above method work if the thrust axis' are sent to FS and NOT FSUIPC?
I am experiencing thrust reverser deployment in flight with the PMDG 737 NGXu low level near flare.
PMDG said FSUIPC would cause this as it doesn't know if the airplane is on ground or in flight.
What would be the best way to map the thrust axis' to achieve the saem desired outcome but with the protections from the FADEC and air-ground sensing system?
-
In the P3D display red text information, my only selections were SLEW and BRAKES. All other check boxes were un-ticked. I removed the dll it was too much hassle. The idea was good, it looks at what frequency is set in your COMM1 and tunes LiveATC.net to that freq and enables real world atc audio which I thought was neat. But not for this amount of effort. Thanks again for the help. I can also confirm that no text message was displayed, although I am not sure if it was suppressed due to my config mentioned above.
-
Well thank you very much John, turns out that that ipc.ask was the culprit. What was odd, was that there was nothing onscreen anywhere prompting user input. Quite frustrating, I have since removed that. Anyways, happy to be back in operation!
Cheers!
-
4 hours ago, John Dowson said:
Hi Angelo,
Pete just pointed out to me that you are running a lua plugin:
103562 LUA.0: beginning "C:\Games\Prepar3D v4\Modules\ipcReady.lua"
103562 LUA Asks: "Laap first start - Actual language is French - Do you want the English version ? (Y/N)"
This is waiting for a response from an ipc.ask request which looks like its blocking keyboard input. Try renaming that lua script to see if that solves your issue.
John
I will look into this.
-
4 hours ago, John Dowson said:
Your keypresses are not being recognised for some reason, but I don't think this is an issue with FSUIPC, and certainly nothing in the latest build. If you remove the FSUIPC5.dll (just rename it temporarily), does P3D see your keypresses?
John
Yes, If I remove the FSUIPC.dll from the modules folder, my key presses return to normal. The moment I re-add it, the problem surfaces.
-
13 hours ago, John Dowson said:
Hi Angelo,
I've just checked this with 5.155 and P3D key commands seem to be working as expected...
That is an old post from April 2019 and references FSUIPC 5.151. Not sure what the issue was there, but its certainly not relevant any more.
You could try activating logging for Buttons and key operations and Events (non axis controls) to see what FSUIPC is receiving/sending.
Cheers,
John
Here is the log as requested. During the sim session, I pressed "B" no result, "Y" no result, "Ctrl+Shift+F12" no result, "Alt+Enter" no result, and finally "Ctrl+C," even that did not work.
-
Hello Pete and Thomas,
I am unsure, but I recently updated my FSUIPC copy to the latest listed in the title. I am now noticing certain keyboard commands are no longer working in sim. I cannot zoom via +/-, “B” for altimeter doesn’t work, “Y” for slew does not work, and Alt+Enter does not work is what I have noticed so far. Even the GSX menu via Ctrl+Shift+F12 isn’t functioning, I have to open the menu via the menu bar drop down. I am able to control zoom and slew from a 3rd party instructor platform so I know it still functions in the sim. All my keyboard keys do work as I checked in notepad.
I googled around and it seems another user is experiencing the same issue. He fixed it by removing this version and going back down to prior build. Can you comment on this? I am sticking with 5.155 for now and am happy to test anything if need be.
https://www.avsim.com/forums/topic/553617-keyboard-commands-not-working/
EDIT: I can verify if I remove the FSUIPC.dll my key commands return to normal and all functionality is restored. I will await your reply. This is P3D v4.5.
-
6 minutes ago, Thomas Richter said:
Hi,
not the button but the throttle lever (axis) you use. To eliminate that you need to define a small dead-zone for idle position to ensure a little noisy axis in idle position overwrite the -1 value. Just a couple millimeter of axis movement as idle dead-zone will do.
Thomas
Ah so even if the button may be noisy, you feel the axis could be wiping the -1 based on seen axis location? This could be very true in my hardware. I will check and verify. Does it make a difference if I assign the axis in FSUIPC (Direct) vs (FS as normal axis)? I believe I use direct currently.
-
So I am suspect some of the buttons may be noisy. In Windows devices and printers they appear okay, but I do get phantom reverse on ground.
To eliminate variable, can I assign ONE button (on release) to command engines 1,2,3,4 to -1 parameter?
-
On 12/10/2019 at 1:07 AM, Thomas Richter said:
Hi,
as Reverse Idle in real means Reverser doors are open and eng is in idle, you do this in FS by setting the thrust value to -1 (minus one). That will open the Reverser but not increase thrust from Idle.
Thomas
So my success was short lived. I am getting unreliable consistence with the reverse idle on all engines. I run a 4 axis 4 engine setup. Each of the 4 button release commands a Throttle Set(x) -1 value.
Sometimes all 4 will idle, other times only 2, or even none. What is the behavior so random?
I also thought maybe it was a button polling rate issue. So I mapped the a SINGLE button (with no others programmed) to send a singular throttle set -1 (not engine specific) and no reverses idled at that point, strange.
If I fly a twin jet I get consistent operations, not sure why 4 engine configs causes this.
Any ideas?
-
15 hours ago, Thomas Richter said:
Hi,
as Reverse Idle in real means Reverser doors are open and eng is in idle, you do this in FS by setting the thrust value to -1 (minus one). That will open the Reverser but not increase thrust from Idle.
Thomas
I selected "Throttle Set" Parameter -1, and that did the trick. Thank you very much. This is resolved.
-
1 minute ago, Pete Dowson said:
Yes. Look through the assignment drop-down for button release.
Pete
Thank you.
-
6 hours ago, Thomas Richter said:
Hi,
as Reverse Idle in real means Reverser doors are open and eng is in idle, you do this in FS by setting the thrust value to -1 (minus one). That will open the Reverser but not increase thrust from Idle.
Thomas
This can be achieved via a button assignment? Specifically a control to be sent when the button is released?
-
I have my thrust levers to when hitting the detent button to command Thrust decr with control to repeat when held checked. I am wondering for control to send button released, is there an assignment for set thrust to Idle reverse? I know there is eng x cut. But this goes right to forward idle, I would like to go from full rev to idle rev if possible.
Thanks all.
-
Resolved.
Silly me, for whatever odd reason rudder axis was still set or got reset somehow in P3D axis assignments. All is well now thanks.
-
On 8/29/2017 at 0:20 PM, Thomas Richter said:
Hi,
there are not much information you give other than using P3Dv4 and FSUIPC.
Minimum needed information is always the versions are used, FS & FSUIPC. In case you have a problem with setting up axes you need to make sure Controls are switched OFF in FS to make sure there are not double assigned axes.
Please send your FSUIPC5.ini file and FSUIPC5.log file (after a short session), best as zip file.
Thomas
FS version is P3D v4.0
FSUIPC log pasted below.
********* FSUIPC5, Version 5.103 (26th June 2017) by Pete Dowson *********
1884688 System time = 30/08/2017 17:35:15, Simulator time = 17:33:28 (00:33Z)
1884688 FLT path = "C:\Users\Angelo\Documents\Prepar3D v4 Files\"
[Continuation log requested by user]
Running inside Prepar3D v4 on Windows 10
Module base=7FFA2E400000
3514485 LUA.4: #1 Reverse Thrust
3514516 LUA.4: #2 Reverse Thrust
3515203 LUA.4: #2 Forward Thrust
3517657 LUA.4: #2 Reverse Thrust
3517750 LUA.4: #2 Forward Thrust
3525219 LUA.4: #2 Reverse Thrust
3540813 LUA.4: #1 Forward Thrust
3540828 LUA.4: #2 Forward Thrust
3697625 Sim stopped: average frame rate for last 1813 secs = 46.0 fps
3697625 Max AI traffic was 49 aircraft (Deleted 0)
3700953 === Closing session: waiting for DLLStop to be called ...
3717422 === DLLStop called ...
3717422 === Closing external processes we started ...
3718422 === About to kill any Lua plug-ins still running ...
3718563 Lua threads being terminated:
3718563 0 = "C:\Lockheed Martin\Prepar3D v4\Modules\Throttle_Idle_1.lua"
3718719 LUA: "C:\Lockheed Martin\Prepar3D v4\Modules\Throttle_Idle_1.lua": killed
3718719 1 = "C:\Lockheed Martin\Prepar3D v4\Modules\Throttle_Idle_2.lua"
3718875 LUA: "C:\Lockheed Martin\Prepar3D v4\Modules\Throttle_Idle_2.lua": killed
3718875 2 = "C:\Lockheed Martin\Prepar3D v4\Modules\Throttle_Idle_3.lua"
3719016 LUA: "C:\Lockheed Martin\Prepar3D v4\Modules\Throttle_Idle_3.lua": killed
3719016 3 = "C:\Lockheed Martin\Prepar3D v4\Modules\Throttle_Idle_4.lua"
3719172 LUA: "C:\Lockheed Martin\Prepar3D v4\Modules\Throttle_Idle_4.lua": killed
3719172 4 = "C:\Lockheed Martin\Prepar3D v4\Modules\ThrottleManager.lua"
3719328 LUA: "C:\Lockheed Martin\Prepar3D v4\Modules\ThrottleManager.lua": killed
3719328 === Closing global Lua thread
3720328 === About to kill my timers ...
3720532 === Restoring window procs ...
3720532 === Unloading libraries ...
3720532 === stopping other threads ...
3720532 === ... Button scanning ...
3720625 === ... Axis scanning ...
3720719 === Releasing joystick devices ...
3720719 === Freeing macro memory
3720719 === Removing any offset overrides
3720719 === Clearing any displays left
3720719 === Calling SimConnect_Close ...
3722828 === SimConnect_Close done!
3722828 === AI slots deleted!
3722828 === Freeing button memory ...
3722828 === Closing my Windows ...
3722828 === Freeing FS libraries ...
3723828 === Closing devices ...
3723828 === Closing the Log ... Bye Bye! ...
3723828 System time = 30/08/2017 18:05:55, Simulator time = 18:03:41 (01:03Z)
3723828 *** FSUIPC log file being closed
Minimum frame rate was 19.3 fps, Maximum was 64.2 fps
Average frame rate for running time of 3538 secs = 45.8 fps
Maximum AI traffic for session was 49 aircraft
Memory managed: 1697 Allocs, 1696 Freed
********* FSUIPC Log file closed ***********
-------------------------- FSUIPC INI ------------------------------------
[General]
UpdatedByVersion=5103
History=CRVNYJGNCOABXZCYGMF0Z
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
InitDelayDevicesToo=No
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
FixControlAccel=No
FixMachSpeedBug=No
AutoScanDevices=Yes
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.0.28.21686
SimConnectUsed=4.0.0.0[WideServer]
WideFSenabled=Yes[Auto]
1=Lua Throttle_Idle_1
2=Lua Throttle_Idle_2
3=Lua Throttle_Idle_3
4=Lua Throttle_Idle_4
5=Lua ThrottleManager[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Throttle Quadrant
0.GUID={AAD310E0-5572-11E5-8003-444553540000}
4=Logitech G13 Joystick
4.GUID={DA58C850-CAE2-11E6-8002-444553540000}
5=CH FLIGHTSTICK PRO
5.GUID={C9AF7CD0-5FA2-11E5-8001-444553540000}
1=AGRONN B737 Yoke V2.1
1.GUID={BC50ED30-97AF-11E6-8001-444553540000}
2=Saitek Pro Flight Throttle Quadrant
2.GUID={AAD310E0-5572-11E5-8009-444553540000}
3=PFC MFD Rudder Pedals
3.GUID={AAD310E0-5572-11E5-8006-444553540000}[Axes]
PollInterval=10
RangeRepeatRate=10
0=0Y,256,D,9,0,0,0 -{ DIRECT: Throttle1 }-
1=0Z,256,D,11,0,0,0 -{ DIRECT: Throttle3 }-
2=2X,256,D,10,0,0,0 -{ DIRECT: Throttle2 }-
3=2Y,256,D,12,0,0,0 -{ DIRECT: Throttle4 }-
4=5X,256,D,36,0,0,0 -{ DIRECT: SteeringTiller }-[Buttons]
PollInterval=10
ButtonRepeat=20,10
1=P0,2,K57,8 -{Key press: 9}-
2=U0,2,K49,8 -{Key press: 1}-
3=P0,3,K48,8 -{Key press: 0}-
4=U0,3,K49,8 -{Key press: 1}-
5=P1,0,K79,9 -{Key press: shft+O}-
6=P0,1,K79,9 -{Key press: shft+O}-
7=R1,3,C65607,0 -{ELEV_TRIM_DN}-
9=R1,4,C65615,0 -{ELEV_TRIM_UP}-
11=P2,5,K71,8 -{Key press: G}-
20=P0,7,CL5:T,1 -{LuaToggle ThrottleManager}-
21=P0,8,CL5:T,3 -{LuaToggle ThrottleManager}-
22=P2,6,CL5:T,2 -{LuaToggle ThrottleManager}-
23=P2,7,CL5:S,4 -{LuaSet ThrottleManager (Flag 4)}-
24=P2,4,K71,8 -{Key press: G}-
25=P0,5,K112,11 -{Key press: ctl+shft+F1}-
26=P2,3,K76,11 -{Key press: ctl+shft+L}-
27=P0,4,K113,11 -{Key press: ctl+shft+F2}-
28=P2,1,K114,11 -{Key press: ctl+shft+F3}-
29=P2,0,K115,11 -{Key press: ctl+shft+F4}-[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No[GPSout]
GPSoutEnabled=No
Port=COM0
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=[GPSout2]
GPSoutEnabled=No
Port=<none set>
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=[Sounds]
Path=C:\Lockheed Martin\Prepar3D v4\Sound\
Device1=Primary Sound Driver
Device2=Speakers (Realtek High Definition Audio)
Device3=LG ULTRAWIDE (High Definition Audio Device)
Device4=Speakers (USB Audio Device)
Device5=Realtek Digital Output (Realtek High Definition Audio)[Profile.717]
1=TFDi Design 717 AirTran[Buttons.717]
0=P1,1,C74115,0 -{Custom control: <74115>}-
1=P1,2,C74119,0 -{Custom control: <74119>}-
2=P0,5,C74150,0 -{Custom control: <74150>}-
3=P0,4,C74150,0 -{Custom control: <74150>}-
4=P2,0,C74151,0 -{Custom control: <74151>}-
5=P2,1,C74151,0 -{Custom control: <74151>}-
6=R1,3,C74108,0 -{Custom control: <74108>}-
7=U1,3,C74110,0 -{Custom control: <74110>}-
8=R1,4,C74109,0 -{Custom control: <74109>}-
9=U1,4,C74111,0 -{Custom control: <74111>}-
10=R0,7,C65966,0 -{THROTTLE1_DECR}-
11=U0,7,C65967,0 -{THROTTLE1_CUT}-
12=R2,6,C65971,0 -{THROTTLE2_DECR}-
13=U2,6,C65972,0 -{THROTTLE2_CUT}-[Keys]
1=49,10,74056,0 -{ctl+1: Press=Custom control: <74056> }-
2=50,10,74060,0 -{ctl+2: Press=Custom control: <74060> }-
3=51,10,74061,0 -{ctl+3: Press=Custom control: <74061> }-
4=52,10,74062,0 -{ctl+4: Press=Custom control: <74062> }-
5=53,10,74063,0 -{ctl+5: Press=Custom control: <74063> }-
6=54,10,74064,0 -{ctl+6: Press=Custom control: <74064> }-
7=55,10,74065,0 -{ctl+7: Press=Custom control: <74065> }-
8=56,10,74058,0 -{ctl+8: Press=Custom control: <74058> }-
9=57,10,74059,0 -{ctl+9: Press=Custom control: <74059> }-[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Throttle2=-15864,-512,512,16255/40
Throttle3=-15864,-512,512,16383/40
Throttle4=-15994,-512,512,16383/40
Throttle1=-15864,-512,512,16255/40
SlopeThrottle1=2
SlopeThrottle2=2
Aileron=-16383,0,0,16383
SlopeAileron=2
Elevator=-15327,0,0,16052
SlopeElevator=2
SlopeThrottle3=2
SlopeThrottle4=1
Rudder=-16383,-565,591,16383
SlopeRudder=2
SteeringTiller=-13363,1024,1755,16383
SlopeSteeringTiller=2[LuaFiles]
1=Throttle_Idle_1
2=Throttle_Idle_2
3=Throttle_Idle_3
4=Throttle_Idle_4
5=ThrottleManager -
-
Hello Pete, I am noticing something amiss here and am asking for clarification. Back in v3 I had FSUIPC setup as follow.
Rudder Axis Direct Calibration (Yaw) Min Center Max Values set.
Second, I had another axis (my spare Joystick) as Tiller. This was also set direct and calibrated min center max. No assignments were conflicting and I made sure duplicates did not exist in P3D UI control settings.
This above achieved the desired effect. Below 35kts, the rudder would manipulate the nosewheel at a limited angle, and joystick would tiller the nosewheel to what would be expected.
Now in v4, the exact same setup does not yield the same effect. The rudder can command full hard turns just like the tiller can, I dont see any null effect on the steering when using my feet to make subtle adjustments while taxiing.
Any ideas?
-
4 minutes ago, Pete Dowson said:
Steering Set, unlike my built-in tiller, is only an FS control. For every change more than the Delta (as shown on the FSUIPC axis assignments tab) it has to send a message to FS's window. That message goes through to the simulation system and, if you calibrated in FSUIPC, gets trapped by FSUIPC for calibration. Then the calibrated value gets sent on.
The delay will be due to the large queue of messages awaiting attention, along with all of the others (and if you are using an add-on like PMDG planes, there are a lot!).
Check that your Delta has not been set low. 256 is the normal default -- don't set it less than that. 512 would give half the messages and still give enough resolution. The full range is something like 32768, so 512 still gives it 64 distinct positions.
The FSUIPC tiller would be more efficient.
Pete
Yes I agree but for some reason the FS Labs 320 provides specific instruction to NOT use the FSUIPC Tiller and to use Steering Set. I know I much prefer the tiller also, but I think the devs stance on it (Rudder not moving whilst turning) and the fact that the aircraft barely turns at all is why I have no choice but to use steering set.
-
That did the trick thank you! Can you think of any reason why the sim or fsuipc may be interpreting the signal from the joystick rather slowly?
Example I will move the joystick hard to the left stop, however the values will keep changing for almost a second or two before matching up with my physical hardware? Almost like a bit of lag, yes I have it calibrated in Windows, and the Slope is zero.
-
Got the latest 4.96. Checked with Piper Cub, still no motion in out on Joy Calib page, still shows steering tiller direct !
-
11 hours ago, Pete Dowson said:
Yes, "steering set" is an FS control, not an FSUIPC direct control, which uses the rudder still for direct compatibility across all versions of FS. Steering Set was new to FSX.
It works fine here, at least in P3D with FSUIPC 4.961. Are you sure your tiller input axis is working correctly? Do the numbers change in the assignment tab? Check with a default aircraft loaded in case something is preventing it.
(I see Thomas already got in and asked the last question).
Pete
I should of clarified, the IN OUT is moving in Axis Assignment, but in Joystick Calibration the calibration values don't move as I want to create a wide dead zone at neutral.
-
Hello Pete, FSL A320 requires that steering set be used in lieu of the steering tiller. My question is, I assign steering set as FS Normal Axis because it is not in the list for Direct FSUIPC Calibration.
I would like to calibrate steering set in fsuipc as another user did, but my IN and OUT values dont move when I move my axis, any idea why.
See this thread here for more detail.
Reverse Idle key command?
in FSUIPC Support Pete Dowson Modules
Posted
Send direct to FS as Axis "Axis throttle set" to Saitek lever 2, and control to send when button released as "Throttle Set" Param (-1) does not cause any change to the thrust position as the button is released.