Gabe-the-Pilot
-
Posts
11 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Gabe-the-Pilot
-
-
13 minutes ago, Pete Dowson said:
Okay. That actually works the same as if you assign in P3d.
1. Where, in the Assignment tab or in the Calibration tab, or both?
Both..... all appears to work as with other axes
13 minutes ago, Pete Dowson said:2. Does this apply to both Direct FSUIPC assignment AND FS control assignment, or only the latter?
Only the former. Rudders work if I assign via your FS Direct option.... but ONLY if I also Reset the calibration made earlier on the Calibrate Axes page.
13 minutes ago, Pete Dowson said
3. Which FS rudder control do you assign to: "Axis rudder set" or "Rudder set"?
Axis Rudder set..... as with other axes
13 minutes ago, Pete Dowson said:4. Does this apply to all aircraft -- default included -- or only add-on aircraft?
All.
13 minutes ago, Pete Dowson said:5. Check your rudder trim: an extreme setting for that will nullify rudder inputs in P3D. You can zero it by assigning a button or key to "Rudder Trim Set" with a parameter of 0.
No. I do have Buttons Set for all other trims along with Centre and they all work well, even in aircraft that aren't meant to have them ... always handy ! But yes, checked in do228 which has bith - even if the needles move the wrong way.... gotta love Carenado.
13 minutes ago, Pete Dowson said:6. Try also just assigning the rudder in P3D -- not as a possible solution necessarily, just to check.
Yes this works ... as I would expect, given No. 2 answer, above.
But I will probably end up having to use this as a solution, as at least I should be able to set a Deadzone and Sensitivity - but of course: no slope / linearity, nor the ability to easily save different values for each aircraft ... 8-(
So hopefully this 'anomaly' can be sorted. As I said earlier, the toe brakes works 'perfick', so I don't get it.
Thnx again.
-
Hi.
Will get back. Need to double check some of these points.
Thnx.
-
15 minutes ago, Pete Dowson said:
You mean assigning in P3D?
FSUIPC's calibration is available no matter where you assign.
I've no idea. You give no details for me to even guess.
Well there are 3 options are there not for assigning an axis.
The first is assign as a fsuipc axis.
The second is assign as a direct fs axis
The third is something about offset .... ?
Normally I use Fsuipc axis and then go the calibration page and calibrate.
Ok.... so, as I said above, I cannot get the Saitek rudder axes to work if I try to use the first option Fsuipc calibration.
I can only get them to work at all, in any aircraft addon, in P3D v4.3 on Windows 10 Pro latest build.... (phew !)..... IF I USE THE SECOND OPTION.
Of course I disable all controller axes in P3D itself, or that would cause a conflict, as per the manual and a million Avsim posts.
Also, if I assign via the second option, it will not work unless I unassign (via the Reset button on the calibration page) the previous calibration.
It all appears to work in the Fsuipc interface, as the numbers behave correctly, but there is no subsequent rudder actuation at all, in the sim.
So.... hope that explains the problem more clearly. I am not at my PC currently, or I would make a video and stick it on Youtube.... in fact I may do just that later.
Thnx
-
Meant to add.... toe brakes work fine ! Assign in usual manner, set a big deadzone and slope no probs.
What is it with the rudder axes ? Bemused !
-
Hi all.
Is this now simply an issue I have to deal with ?
Basically, I can only use Direct FS axis with all my aircraft in P3D v4.3.
Clearly this means no sensitivity or slope adjustment, which I badly need as thry are so overly sensitive.
Am I missing something or is there a workaround ?
Thnx for any help.
-
Just will not locate the correct paths for creating the required database !
Please sort this out.
Xannot find the right P3D v4 paths - no mention of P3D in the interface. Why ?
Purchased from Just Flight on the basis that it would be P3D friendly - it is not !
-
UPDATE
Okay it transpires that the AFCAD software I was using has a problem with apron lights with not enough space between them.
As I had modified another persons BGL file that had been made with a different AFCAD program - there was a conflict.
Now I have deleted all the apron lights and redone them using my choice of AFCAD software...it is fine.
So, the chances are...a sudden OME is probably due to a scenery problem rather than a system problem. Mine came on suddenly - I'd never had one before!
So I suggest testing to make sure that the problem happens everywhere regardless of where you load a flight from and that you haven't installed new scenery or modified any AFCADS before you start thinking you need to worry about pagefiles and /3GB fixes etc. -seriously, it probably isn't anything to do with that (at least in XP - I can't speak for Vista and never will...8-) )
-
Hi,
Well it transpires that the bgl per se was not the problem.
I have reloaded a fresh version of it and it is working fine - it appears that one or more other files are interfering with it...I am now in the process of eliminating the offending item - once found it will be dealt with in an...appropriate fashion....I will spend some time deciding what 'approriate' will amount to......I may put the file in the same folder as a Jason Donovan mp3 file....and just leave it there to rot until Xmas....ho ho ho !..... :evil: :twisted: :lol:
-
Hi,
Sorry - yes.
I am not going to say which program it was as it would be doing an enormous - and undeserved - mis-service to it.
Suffice it to say, it was a bgl that started out as someone else's that I subsequently modified. At some point it went wrong - clearly.
It was simply a AFCAD file that had parking positions and so on - not a landclass bgl. So it was the main airport AFCAD file.
Hope that helps.
Maybe a good test to see if is a BGL file, is to uncheck your addon scenery folder or any that you have recently installed/modified - just common sense really, in a bid to narrow down and possibly eliminate it as a cause.
I felt a little foolish after spending hours looking at other causes of OOM errors - when I did a Search for all files modified in the past 24 hours...guess which BGL file popped up? Yes - the filthy rotten perpetrator...! Having created a new one with the same program and reactivated it - it is now fine.
-
Okay,
I've just started having OOM problems with XP - knew this was rare.
Turns out I have a "dodgy" bgl file that I created using a scenery design application. Whenever I flew near or left from this airport, I'd get the Out of Memory message and then crash. As soon as I disabled this particular scenery folder in the library...no problems any more.
Don't know what caused it - don't want to - I'll simply create a new one.
You have been pre-warned and pre-armed !
Cheers
Saitek Rudder Pedals Issue - not able to calibrate
in FSUIPC Support Pete Dowson Modules
Posted
Well thnx for your efforts.
I cannot uninstall the drivers unfortunately as I value the multi mode function too much.
Everything is perfect on my system except the rudder pedals.
It will go down in my huge tome that includes many musings on the wierdisms of flight sim setups.
Good news is I configured the rudder pedals in P3D itself... just for the rudder pedal axes and with a little tweaking got a reasonably good sensitivity / deadzone compromise that seems to work OK on all my addons.
I had to set the rudder pedals to Do Nothing in FSUIPC though, for each addon... and reload the aircraft a couple of times... but all is now good and I have made a backup of the relevant file !
Thnx again Pete. Case closed I guess !
🤣 Now I can watch Strictly without fretting.