[5.12 and display problem]

Thanks Pete.

[5.12 and display problem]

Just after installing 5.12 my display window was 'moved' to the upper left corner and the rest is black??

 

[Saitek Cessna Trim Wheel...again]

Normally it is empty, but right now I moved the Trim Wheel a lot further than before and suddenly it kicked in and I was able to assign it. 

Weird though, but maybe The Trim Wheel needs more movement than joysticks?

Thanks for the help.

 

Michael

 

[Saitek Cessna Trim Wheel...again]

36 minutes ago, Thomas Richter said:

Hi,

what type of controller is it in Windows, does it use a axis (slider) for the trim wheel (from your first post I would guess)?

Are you using other controllers as well, listed in FSUIPC?

What Controller number (Joy#) do see when you move the trim wheel in FSUIPC?

Thomas

Yes in Windows the Trim Wheel use an axis.

This is my controllers:

[JoyNames]
AutoAssignLetters=No
0=Mad Catz Pro Flight Cessna Trim Wheel
0.GUID={82413B00-8D72-11E6-8001-444553540000}
1=Saitek Pro Gamer Command Unit
1.GUID={07E4ABD0-7E7C-11E6-8009-444553540000}
3=Saitek Cyborg X
3.GUID={07E45DB0-7E7C-11E6-8001-444553540000}

Nothing happens when I move the Trim Wheel in FSUIPC.

 

Michael

 

[Saitek Cessna Trim Wheel...again]

Hi Thomas

Yes, it is listed in the FSUIPC file:

0=Mad Catz Pro Flight Cessna Trim Wheel
0.GUID={82413B00-8D72-11E6-8001-444553540000}

 

Michael

 

 

 

[Saitek Cessna Trim Wheel...again]

My new Saitek Cessna Trim Wheel is not recognized in Axis assignments by FSUIPC.

I have P3D v3.4 running on Windows 10 and I can use the Trim Wheel in Windows Device settings.

If i enable controllers in P3D, then I am able to assign the Trim Wheel, but not in FSUIPC.

Michael

[Reading Attitude State?]

Ok, this works if I use the Offset to read the state and then the control 66373 to set.

 

 

Thanks Pete  :)

[Reading Attitude State?]

Logging L:Vars doesn't log controls, so i guess you aren't logging L:Vars. What did you do?

 

 

 

Well that works fine, with the FS control 66373 and offset 2F68 changing accordingly, as logged here where I clicked the button twice:

 

   114162 *** EVENT: Cntrl= 66373 (0x00010345), Param= 1 (0x00000001) ATTITUDE_CAGE_BUTTON

   114193 Monitor IPC:2F68 (U32) = 1

   114193 SimRead: 2F68="ATTITUDE CAGE"

            INT32: 1 (0x00000001)

   119731 *** EVENT: Cntrl= 66373 (0x00010345), Param= 1 (0x00000001) ATTITUDE_CAGE_BUTTON

   119762 Monitor IPC:2F68 (U32) = 0

   119762 SimRead: 2F68="ATTITUDE CAGE"

            INT32: 0 (0x00000000)

 

Regards

Pete

Well, I used Tracker tool in the LINDA application, which logs both L:Var and Controls.

Your example from the DC-3 is exactly like the script I wrote using the Offset 2F68.

Value 0 for Off and 1 for On, but it does not work in the F1 Islander.

Maybe I should write the script first for the DC-3 to test it?

Thanks

Michael

[Reading Attitude State?]

I tried to log the L:Var, but nothing came up except the FSX control.

 

The default DC-3 has a Cage button, bottom right under the Horizon indicator.

 

 

 

Michael

[Reading Attitude State?]

I use FSX Acceleration and this is for the Flight1 BN-2 Islander.

 

An item on the Shutdown checklist is to Cage the Attitude indicator.

 

I want this Shutdown checkliste to run automatically in a LINDA module, but I have no way of reading the state of the Attitude indicator.

 

 

Michael

[Reading Attitude State?]

Does anyone know if its possible to read the Attitude state (Caged or Uncaged) ?

 

I have tried using Offset 2F68, but it does not seem to do the job.

 

The only thing left is the Toggle control 66373, which does not have an off/on setting.

 

 

Thanks

Michael

[Frictionality and Bush airstrips?]

FSX Frictionality sounds interesting, but can it be used for bush airstrips?

After all wet grass has other surface characteristics than wet tarmac.

Michael

[Read value of FSX control?]

Pete,

 

The new Acceleration controls would be specific for Aircraft carrier and SAR aircrafts/helicopters.

They pop up in LINDA when I try mapping one of these aircrafts/helicopters. I might just make a list of these.

 

Just like we have FSX controls for various aircraft lights, then we also have Offset values to control them directly, which is way more powerful.

Thats what I am looking for in the Acceleration controls.

 

xcorez,

 

Thanks for the XML gauge workaround, which I will try out  :)

 

 

Michael

[Read value of FSX control?]

Actually I am using the application LINDA, which I think does the same job.

And no, the only action is that an FSX control is activated.

I really wish all aircraft designers would add Lvar to all buttons, levers and switches.

 

Well, if you add all the new Acceleration controls, it would be nice to have these Associated with an Offset value.

I am not really sure, if I can do this myself.

 

 

Michael

[Read value of FSX control?]

Hi Pete,

 

Unfortunately I do not have an Lvar option for this function, but I will create a 'normal' toggle using the FSX control.

 

Will the Offset document be updated as well?  ;-)

 

 

Michael

[Read value of FSX control?]

The 'Launch Bar' is from default FSX Acceleration and activated through the keyboard command Shift+U.

 

 

 

Michael

[Read value of FSX control?]

An example would be to test the status of the Launch Bar (FSX control 66879), if extended or retracted (Carrier Ops).

 

I have no Offset value for this control.

 

 

Michael

[Read value of FSX control?]

Hi Pete,

 

 

Is there any way to read the current value of a given FSX control, if this control does not have an offset value?

 

I assume that a command like this will just activate the control?:

 

if (ipc.control(XXXX)) == 0 then

...

 

 

Thanks

Michael

[And another G940 question]

In the axis assignment section FSUIPC recognises all the standard Windows joystick parts -- up to 8 axes and 4 POVs ("Points of View" controls, or Hats). If your second hat is not recognised as such by Windows it won't be recognised as such in FSUIPC. If you want it recognised, instead, as a set of buttons I'm afraid that is not supported in FSUIPC -- only button numbers 32-39 for the first POV are supported. Try the axis assignments instead. You can still do assignments to up to 10 of the values it sends by using the range assignments on the right-hand side.

 

Pete

Thanks, I will try the axis assignment.

[And another G940 question]

Hi Pete,

 

I have a Logitech G940 Flightstick and Throttle with two POV/HAT buttons on each.

 

My problem is simply that FSUIPC4 only recognizes one POV/HAT button on each device.

 

What can I do to change this?

 

[Weather from Opus?]

Can FSC9 download weather from Opus FSX ?

 

 

Michael

[FSC 9.3 and Alternate ?]

I have just installed FSC 9.3.

After creating a new flightplan with an alternate airport FSC does not save this airport to any file.

When this flightplan is re-opened the alternate airport is missing.

Michael

[Dreamscenery Indianapolis X ?]

Been some years since this airport was released and no update for the mid-terminal seems to be in sight.

Is this still the best scenery of Indianapolis airport for FSX ?

Despite its age it still looks good in screenshots.

Thanks

Michael

[FSC9 & Scansim EKCH]

Oops sorry forgot that,

1. FSX

2. FSUIPC4 4.70

3. FS Commander 9 Build 14.7.2011 and Database Manager version 9 Build 1.1.2011

4. Download version from Simmarket

5. Windows 7 64

I will reinstall FSX and report back if the problem still exists.

Thanks

Michael

[FSC9 & Scansim EKCH]

I have just bought and installed FSC9, but apparently FSC9 can not read the bgl-file of my EKCH scenery from Scansim, so the gates are not correct.

I can see that in Airport Information it is referring to the standard EKCH bgl-file.

Michael