Roland
-
Posts
80 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Roland
-
-
Hi Pete,
yes that seems to be difficult.
Anyway, this FSUIPC works perfect and now there is a real big potential in it.
-
Arrrgh, I'd better read the manual twice :-)
Your right, now it works perfekt. This is really great!!
On my wishlist :-)
As a future update it could be possible to choose if we want to save settings for a exact Model or group of Models. That would prevent editing the ini-file.
Thx Pete
-
Hi Pete,
this version works great, except editing the aircraft name in FSUIPC.ini to make it work for i.e. all Bell does not work.
This works perfekt:
[axes]
1=0Y,256,D,2,0,0,0
2=0Z,256,D,4,0,0,0
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,6464,16383,66079,0
6=1Y,D,-16384,-4787,66080,0
7=1Z,256,D,6,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
0=0X,256,D,1,38,0,0
[Axes.Boeing 737-400]
0=0X,256,D,1,38,0,0
1=0Y,256,D,2,0,0,0
2=0Z,256,D,4,0,0,0
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,6464,16383,66079,0
6=1Y,D,-16384,-4787,66080,0
7=1Z,256,D,22,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
[Axes.Bell 206B JetRanger]
0=0X,256,D,33,38,0,0
1=0Z,256,D,4,0,0,0
2=1X,256,D,1,0,0,0
3=1Y,256,D,2,0,0,0
4=1Z,256,D,5,0,0,0
5=2X,256,D,7,0,0,0
6=2Y,256,D,8,0,0,0
7=2Z,256,D,3,0,0,0
This do not:
[axes]
1=0Y,256,D,2,0,0,0
2=0Z,256,D,4,0,0,0
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,6464,16383,66079,0
6=1Y,D,-16384,-4787,66080,0
7=1Z,256,D,6,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
0=0X,256,D,1,38,0,0
[Axes.Boeing]
0=0X,256,D,1,38,0,0
1=0Y,256,D,2,0,0,0
2=0Z,256,D,4,0,0,0
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,6464,16383,66079,0
6=1Y,D,-16384,-4787,66080,0
7=1Z,256,D,22,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
[Axes.Bell]
0=0X,256,D,33,38,0,0
1=0Z,256,D,4,0,0,0
2=1X,256,D,1,0,0,0
3=1Y,256,D,2,0,0,0
4=1Z,256,D,5,0,0,0
5=2X,256,D,7,0,0,0
6=2Y,256,D,8,0,0,0
7=2Z,256,D,3,0,0,0
-
Great Pete,
so I'm standing by for further updates :-)
-
Hi Pete,
first of all, we have to thank you for this great tool!
For me, it would be the best to make a copy of all defaults, cause this is the base of all alterations. I think most aircraft do need the same assignments and for example in a jet I would like the mixture set as spoiler.
And it would be great if we could edit the FSUIPC entries in that way, that special assignments work on a group of aircraft, i.e. all boeing or all bell.
AFAIK we could do this in the calibration section in this way.
-
Hi Pete,
OK lets go on with it.
First try, reassigned Controller 0 X-Axis (CH Yoke USB) to Pan Heading
Result:
[Axes]
1=0Y,256,D,2,0,0,0
2=0Z,256,D,4,0,0,0
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,6464,16383,66079,0
6=1Y,D,-16384,-4787,66080,0
7=1Z,256,D,6,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
0=0X,256,D,33,0,0,0
Thats OK I think
Next try, Joystick Z-Axis (MS SW FF Gameport) from Mixture to Spoiler
Result:
[Axes]
1=0Y,256,D,2,0,0,0
2=0Z,256,D,4,0,0,0
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,6464,16383,66079,0
6=1Y,D,-16384,-4787,66080,0
7=1Z,256,D,22,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
0=0X,256,D,33,0,0,0
Seems that normal assignments work well
Now setting back Yoke X to Aileron and second funktion to SlewSide and MSJoystick Z back to Mixture
Result:
[Axes]
1=0Y,256,D,2,0,0,0
2=0Z,256,D,4,0,0,0
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,6464,16383,66079,0
6=1Y,D,-16384,-4787,66080,0
7=1Z,256,D,6,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
0=0X,256,D,1,38,0,0
Perfect :-)
And now the first Aircraft-Specific Assigment.
Aircraft Standard-Boeing 737
Same as above, Yoke X to PanHeading (with makes no sense I know :-)
To do so, I klick on Rescan, move Yoke X, klick checkbox "aircraft specific" and change the entry in the first tab from Aileron to PanHeading.
The second entry "SlewSide" was left unchanged.
Result:
[Axes]
1=1Y,256
2=1Y,U,6464,16383,66079,0
3=1Y,D,-16384,-4787,66080,0
4=1Z,256,D,6,0,0,0
5=2X,256,D,7,0,0,0
6=2Y,256,F,8,0,0,0
7=2Z,256,D,3,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
0=1X,256,D,5,0,0,0
[Axes.Boeing 737-400]
0=0X,256,D,33,38,0,0
No more 0-Controller in the global axis section, all entrys from controller2 twice.
I just checkt the FS9-axis-assignments and found that FS9 reassigned the USB-Pedal (Controller2) when I start FS9. So I disable them again and
repeat the assignments of the last step. Befor this, I reset the FSUIPC.ini to the last working version.
But...
Same Result:
[axes]
1=1Y,256
2=1Y,U,6464,16383,66079,0
3=1Y,D,-16384,-4787,66080,0
4=1Z,256,D,6,0,0,0
5=2X,256,D,7,0,0,0
6=2Y,256,F,8,0,0,0
7=2Z,256,D,3,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
0=1X,256,D,5,0,0,0
[Axes.Boeing 737-400]
0=0X,256,D,33,38,0,0
Reset to working status and trying another axis. Now I try MSjoystick on gameport (Controller1) Z-Axis to Spoiler
Result:
[axes]
1=0Y,256,D,2,0,0,0
2=0Z,256,D,4,0,0,0
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,6464,16383,66079,0
6=1Y,D,-16384,-4787,66080,0
7=2Z,256,D,3,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
0=0X,256,D,1,38,0,0
[Axes.Boeing 737-400]
1=1Z,256,D,22,0,0,0
We lost 1Z in the normal section and dubbled 2Z
Again Reset and now assigning Controller2 (Pedals USB) Z to Pan Heading
Result:
[axes]
1=0Y,256,D,2,0,0,0
2=0Z,256,D,4,0,0,0
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,6464,16383,66079,0
6=1Y,D,-16384,-4787,66080,0
7=1Z,256,D,6,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
0=0X,256,D,1,38,0,0
[Axes.Boeing 737-400]
2=2Z,256,D,33,0,0,0
Looks OK I think. Very strange.
OK, stop trying at this point.
-
Hi Pete,
its a pleasure to go thru this pain :-)
Ok here we go.
First I deleted the whole Axis Section, open FSUIPC go to Axis Assignments and klick Reload all assignments.
After this, no assignments are shown.
Now I klick Rescan
Move the Yoke X-Axis
Picture1 after this step
Now I klick "Send direct to FSUIPC Calibration
and chose "Aileron" in the dropdown menue
Picture 2
To see this assigment in FSUIPC.ini I close with OK
The correkt entry in FSUIPC.ini
[Axes]
0=0X,256,D,1,0,0,0
To make it short :-) I do so for the other Axis
All axis not specified for an aircraft at this moment.
Yoke Y = Elevator
Yoke Z = Throttle
Pedal X = Left Brake
Pedal Y = Right Brake
Pedal Z = Rudder
Joystick X = Prop pitch
Joystick Y = Gear Up Gear down
Joystick Z = Mixture
FSUIPC.ini after this
[Axes]
0=0X,256,D,1,0,0,0
1=0Y,256,D,2,0,0,0
2=0Z,256,D,4,0,0,0
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,6464,16383,66079,0
6=1Y,D,-16384,-4787,66080,0
7=1Z,256,D,6,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,0,0,0
looks fine, I think.
Bevor I continue I wait for your "Go" :-)
-
Hi Pete,
we talked about in threat "CH Flightstick ...
I made some test today and have problems to assign axis aircraft-specific.
My Setup as FSUIPC recognice them:
Controller 0 = CH Flightsim Yoke USB
Controller 1 = MS Sidewinder FF Gameport (FF disabled)
Controller 2 = CH Simpedals USB
All Controllers are deleted in FS9 Axis assignment
They where send direct to FSUIPC Calibration.
This is the a part of my FSUIPC.ini before I made axis assignments to my Bell Jetranger.
[Axes]
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,1760,13312,66079,0
6=1Y,D,-12593,-6586,66080,0
7=1Z,256,D,6,0,0,0
8=2X,256,D,7,0,0,0
9=2Y,256,D,8,0,0,0
10=2Z,256,D,3,40,0,0
11=2Z,256,D,3,40,0,0
2=0Z,256,D,4,0,0,0
1=0Y,256,D,2,39,0,0
0=0X,256,D,1,38,0,0
As you can see, the Yoke (0) is assigned to Elevator, Aileron and Throttle,
Pedals (2) Rudder and Brakes
The Joystick X-Axes is assigned to Prop Pitch
and the Y-Axes is assigned to Gear (works fine, great feature!!)
Z-Axes works as Mixture.
OK now I load my Bell Jetranger and like to assigne the joystick axes X and Y to Aileron and Elevator, Z to Prop-Pitch (Rotor RPM)
The Yoke X should pan the View in 3D-Cockpit, Yoke Throttle works normal (as Pitch) and Yoke Y is not assigned.
Here are some Screens of my assignments:
And now the new FSUIPC.ini ( I cuted some entrys between the axes Section and the Aircraft-specific Section)
[Axes]
3=1X,256,D,5,0,0,0
4=1Y,256
5=1Y,U,1760,13312,66079,0
6=1Y,D,-12593,-6586,66080,0
7=2X,256,D,7,0,0,0
8=2Y,256,D,8,0,0,0
9=2Z,256,D,3,40,0,0
10=2Z,256,D,3,40,0,0
11=2Z,256,D,3,40,0,0
0=1X,256,D,5,0,0,0
...
[Axes.Bell 206B JetRanger]
0=0X,256,D,33,38,0,0
2=2X,256,D,7,0,0,0
The problem now is, FSUIPC shows the Axis 1X and 1Y with aircraft-specific-box checked but it changed the normal section.
In every test there are only 2 Axes saved aircraft specific and I never assigned any axes from the Ruderpedals (2) aircraft-specicfic)
Then I deleted the FSUIPC.ini and made some new assignments.
This time some strange things haben with the aircraft-entry
[Axes]
1=0Y,256,F,2,0,0,0
2=1X,256,D,1,0,0,0
3=2Z,256,D,3,0,0,0
4=2X,256,D,7,0,0,0
5=2Y,256,D,8,0,0,0
6=2Z,256,D,3,0,0,0
0=0X,256,D,1,0,0,0
[Axes.Bell 206B JetRanger]
1=1X,256,D,1,0,0,0
2=2X,256,D,7,0,0,0
0=0Z,256,D,4,0,0,0
1Y works as aileron, but isn't shown in FSUIPC.ini.
And it is not assigned in FS9!
This works until I restart the FS9.
Every other Axes is written to FSUIPC.ini when I assign it to a funktion.
Ehm... can you follow, its a bit confusing and difficult to explain :-)
-
Hi,
the Problem is that FSUIPC only see Controller1 and not CH Yoke or CH Flightstick.
Also FS9 assigns all axes and buttons new by default, when you change your controller.
There is no solution to your problem, when you change your controller everytime you use a different aircraft.
-
Hi Doug,
did you plug in both devices or did you use only one of them at a time?
In the first case, there is no problem to assign any funktion to your buttons cause you have device joystick1 and device joystick2.
With the new Version 3.6 of FSUIPC you can assign axes AND Buttons aircraft specific, unfortunally it seems to work not quite correct in this version, FSUIPC doesn't save this settings correct in fsuipc.ini.
I'm testing at the moment different axis for the bell206, where my joystick feeds the elevator and the aileron but with a fixed wing it serves propeller and the gear lever.
On the other hand, if you use both devices at the time you can use different FS9.cfg to assign your buttons and axis in any way.
To do so, read FSUIPC for Advanced Users.doc page 38, wich explains how to use different FS9.cfg and different FSIPC.ini files. You find this document in your modules-folder.
-
Hi,
had the same Problem, for me it was a Addon "Carrier2004", wich gives you the ArrastorCable Carriers.
Don't know how, but this one flattens a big Area in WA.
Maybe this was your Problem to.
One word to CTD's.
Take a look at Landclass-Files installed in Scenerys with Texture-Folder inside.
Some of the recomended Scenerys of the new EmmaFieldTour III do so.
Search for LC inside the BGL-Name.
Landclass (and Mesh) should be installed in a separate Folder with only one Sceneryfolder inside (no Texturefolder).
-
Hallo Andreas,
ich hab da was in der AFCAD-Hilfe gefunden.
Zum einen gibt es den Parameter atc_parking_types=GATE in der Aircraft.cfg. Der ist nicht bei allen Flugzeugen vorhanden, kann aber nachgetragen werden. (Schau dir mal die Default 747 an)
Dann kannst du natürlich mit AFCAD eine Menge machen. So lassen sich für eine Menge Fluglinien Gatepositionen festlegen.
Am einfachsten schaust du dir das mal auf der AFCAD-Seite an.
http://afcad.projectai.com/general/afcad_help2.php
Gruß und a3g
Roland (ebenfalls) Pohl
-
Moin,
kann es sein, dass der Luftdruck falsch eingestellt ist? Dann stimmen die Höhen nicht.
Einfach mal vor dem Start "B" drücken.
-
-
Got it, Pete :-)
thanks again, i love you (not really, my wife dosn't like that )
-
Hi Pete,
same happend to me?
Send my Mail on Sat. 26 of July to 'petedowson@btconnect.com'
My Mailadress 'Roland_Pohl@gmx.de'
-
dass austria pro noch mit fs2000 texturen arbeitet
So hatte ich zumindest den Eindruck, als ich die AustriaPro2002 das erste mal gesehen habe.
-
@ boerries: meinst du nicht evtl. den FS2000. AFAIK gibt es die "sich bewegenden Scheinwerfer" nicht im FS2002.
Allerdings hat die Austria Pro selbst (nicht die Add-packs) diese in Östereich hinzugefügt.
Die Dinger sind Bestandteil der Straßentextur und können nicht beseitigt werden, ohne die Straßen selbst zu beseitigen.
-
Hi,
looking good, but the national flag left from GB isn't correct, if it is the german flag. Colors shoud be Black Red Gold from topdown. In case of Belgium the bars must be vertikal.
-
@TEBRO
if you are so lucky to use this CH Yoke with three Levers, you can change the axis-settings in FS2002, in that way the formal Prop (or what is right of the throttle) lever is set to the Engine2-Throttle-Axis and the normal Throttle is set to Engine1-throttle-axis. Its a bit difficult to explain for me couse my english isn't very well.
With FSUIPC you can map this Setting already to an 4 Enginesetup.
Regards
-
Regarding if you should change all 4 VC entries. I would. Then, change VC 1 back to 1024 and see if the problem comes back. And on and so forth. However, if you can't tell the difference between how it looks in 512 and 1024... I would not even bother to go back to the higher resolution. Stick with 512. Your processor will thank you.
@EKO
The problem returns, when you change back VC1 to 1024.
The difference between 512 and 1024 isn't very much. The instruments are allready readable.
The VC-Panel in Twotter is a set of 4 1024x1024 Bitmaps, maybe thats a bit to much.
Thanks again for your hint.
-
Hello Eko,
confirm to Shaun.
With all Pixel-size for VC set to 512,512 all delays are gone, it switches normal between Fullscreen and Window.
Maybee there are too many VC-entries in Panel.cfg. I counted 4.
The wonderfull SIAI Marchetti SF260 has only 2 VC-Entries, one with 1024,1024 (Right Cockpit) and one with 128,128 (Far left of the cockpit)
Maybee there is no need to set all 4 Entries to 1024,1024?
-
And what about VA's?
I've done the paintjob for several Aircrafts of my Simclub. And it would be wonderfull to have a Paintkit.
But if not, no pro to alter the textures with Photopaint.
Anywhere, the most problem is to identify each part of the whole aircraft.
-
:D thats a kind of highspeedreaction i realy like.
Thanks, thats good support.
let the Twotter be a real good aircraft :-)
FSUIPC 4.0 - Addons menu not appearing
in FSUIPC Support Pete Dowson Modules
Posted
Hi,
same problem to me.
I assigned some aircraft specific axes and the menue entry was gone.
Solved this problem by deleting the FSUIPC4.ini.
BTW the aircraft specific assignment didn't work correct. I changed the aircraft but it saved with the aircraft I started the flight with.