Jump to content

FSUIPC4 version 4.115 & Leveld 767


Recommended Posts

Hi

I'm using FSUIPC4 version 4.115 on Windows Vista 32, and for control I use a joystick Saitek X52 and trackIR

yesterday I purschase the new leveld 767 for FSX (sp1) and notice that I cannot use Vnav A/P. In other words the altitude don't stabilyze. The plane goes up and down, and to fly I have tu use all the time the trim weel

But when I remove my registered version of FSUIPC (that I use to calibrate the X52) all works fine on the plane.

Something is not comunicating good with simconnect. or there is some kind of conflit going on.

Many people using this plane, are reporting this and other's strange things.

Please, take a look at that. Thanks

Link to comment
Share on other sites

Something is not comunicating good with simconnect. or there is some kind of conflit going on.

What does the FSUIPC4.LOG file (in the FSX Modules folder) show? If SimConnect is playing up t may be installed incorrectly, so possibly a SimConnect log would be useful too. Please see the FSX Help announcement above.

Many people using this plane, are reporting this and other's strange things.

And what do LevelD say about it?

Regards

Pete

Link to comment
Share on other sites

Something is not comunicating good with simconnect. or there is some kind of conflit going on.

What does the FSUIPC4.LOG file (in the FSX Modules folder) show? If SimConnect is playing up t may be installed incorrectly, so possibly a SimConnect log would be useful too. Please see the FSX Help announcement above.

Many people using this plane, are reporting this and other's strange things.

And what do LevelD say about it?

Regards

Pete

FSUIPC.LOG

...

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX on Windows Vista (SimConnect SP1 May07)

Module base=61000000

DebugStatus=15

156 System time = 19:22:26

156 FLT UNC path = "C:\Users\Jorge\Documents\Flight Simulator X Files"

156 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X"

998 LogOptions=00000001

998 SimConnect_Open succeeded: waiting to check version okay

8159 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0)

8159 Initialising SimConnect data requests now

8159 FSUIPC Menu entry added

8205 C:\Users\Jorge\Documents\Flight Simulator X Files\Startup.FLT

8205 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\B737_800\Boeing737-800.AIR

34414 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\LVLD_B763\B767-300.AIR

76612 System time = 19:23:43, FSX time = 19:22:35 (18:22Z)

76737 Aircraft="Level D Simulations B767-300ER - British Airways"

77829 Advanced Weather Interface Enabled

973165 System time = 19:38:39, FSX time = 19:34:38 (18:34Z)

973165 *** FSUIPC log file being closed

Memory managed: 473 Allocs, 473 Freed

all seems ok.

Link to comment
Share on other sites

all seems ok.

Yes, that's fine. SimConnect doesn't look to be playing up.

Are you calibrating the Throttles via FSUIPC? I seem to remember in the FS2004 versions of some add-on aircraft (e.g. FeelThere ERJ145) you had to select the "exclude THROTTLEn_SET" option on the 4 throttles page when using that for calibration.

Otherwise I can't imagine how there'd be any conflict. If you don't calibrate through FSUIPC is there still a problem? If so, you could further see if is still the same if you close FSX and add "NoAxisIntercepts=Yes" to the [General] section of FSUIPC4.INI before reloading? As it says in the FSUIPC4 Advanced User's guide:

NoAxisIntercepts is only relevant to registered FSUIPC4 installations, can be set to ‘Yes’ to prevent FSUIPC4 intercepting and forwarding axis controls. This will prevent the use of the Joystick Calibration facilities for FS-assigned joystick axes (though you could still use the FSUIPC4 axis assignments directed to FSUIPC4’s calibrations).

These two facilities was added only to get around the problem the initial release of SimConnect has with some third party security programs, where the firewall or privacy hooks inserted by those programs (whether enabled or not) appear to slow down SimConnect’s ability to send data to FSX. Delays in axis operations of up to 30 seconds have been reported!

When, hopefully, these problems with SimConnect are fixed—whether by an FSX update or merely information on avoidance action—these options will be redundant and will probably be removed, and normal axis interception resumed.

Mind you, if you had delay problems with axes you'd surely have noticed these before you added the LevelD 767?

I'm really not able to go any further with this without knowing what the LevelD aircraft is doing. I don't suppose it is even using FSUIPC these days, is it? Is there any answer on the Level D support forum, which I assume they have (still locked to others by the look of it?). Or do they do support by private email now?

Regards

Pete

Link to comment
Share on other sites

Are you calibrating the Throttles via FSUIPC? I seem to remember in the FS2004 versions of some add-on aircraft (e.g. FeelThere ERJ145) you had to select the "exclude THROTTLEn_SET" option on the 4 throttles page when using that for calibration.

Yes. And the exclude THROTTLEn_SET is active. The problem is the trim, not the trottles

Otherwise I can't imagine how there'd be any conflict. If you don't calibrate through FSUIPC is there still a problem?

If I calibrate through FSUIPC the problem appears.

If I simply remove FSUIPC from de modules folder, the problem goes away.

And Yes, "NoAxisIntercepts=Yes"" solves the problem too. :?

With the axis controled by FSUIPC directly.

EHEHEH

IT solved the problem !! Nice very nice. Is in times like this that I'm glad that I payed for the software!

Thanks. Now all seems to work fine.

PS: Send a MSG to Leved developers. Controlling the axis directly with FSUIPC and "NoAxisIntercepts=Yes" is the key :idea:

Link to comment
Share on other sites

And Yes, "NoAxisIntercepts=Yes"" solves the problem too. :?

With the axis controled by FSUIPC directly.

EHEHEH

IT solved the problem !! Nice very nice. Is in times like this that I'm glad that I payed for the software!

Just so I understand a little of this, you have "NoAxisIntercepts=Yes" set as well, still? If so, if that is omitted, even though you are calibrating axes directly, does the problem still exist?

Thanks. Now all seems to work fine.

PS: Send a MSG to Leved developers. Controlling the axis directly with FSUIPC is the key :idea:

I'd like to understand why, though. I wonder what is special about their implementation which would cause such problems.

Regards

Pete

Link to comment
Share on other sites

I have NoAxisIntercepts=Yes SET and calibrating axes directly

If you put NoAxisIntercepts=NO and calibrating axes directly, the plane won't opperate normaly in A/P

in conclusion, if the NoAxisIntercepts is with the flag NO, you cannot use the plane with A/P, FMC, etc.And this is with calibrating axes directly or calibrating with FSX

Link to comment
Share on other sites

I

in conclusion, if the NoAxisIntercepts is with the flag NO

Which it is by default with a registered FSUIPC. It just means all axes pass through FSUIPC before they get to FS, just as happened with FS2000 through to FS2004.

If LevelD doesn't like this it must mean they are capturing the same controls but at some intermediate priority between the one FSUIPC captures them at and re-transmits them at. Which would be a bit weird if you ask me.

I'm afraid to sort this out properly, the appropriate developer in Level D will need to contact me and discuss SimConnect details.

Regards

Pete

Link to comment
Share on other sites

Hi,

FYI, from one of the developers in the Level-D FSX Forum (only for licenced members):

"The 767 for FSX has been reprogrammed to take advantage of the new SimConnect features. FSUIPC is now only used for the advanced fuel logic (fuel dump, scavenger pumps, apu fuel flow). It is likely that this logic will be also converted to SimConnect in our future products. In the meantime, if you want to desinstall FSUIPC you will only loose what is mentionned above."

Link to comment
Share on other sites

  • 2 weeks later...

Pete,

I am having the same problem with the LDS except it is with FS2004 and 3.75 Registered. I have tried adding the NoAxisIntercepts=Yes and this had no effect. Is there a different setting for 2004 that may work? Additionally I tried the Feelthere fix of checking the elevator controls and this also did not work. I removed the FSUIPC.dll and the AP trimmed just as it is supposed to. I will give deleting the INI file a shot and see if that works.

Link to comment
Share on other sites

Hey, Pete. Hope your holiday was good...

From the Level-D forum, it seems the tag "NoAxisIntercepts=Yes" corrects the AFDS instability. Unfortunately each time FSX closes, FSUIPC rewrites the FSUIPC4.ini and the line "NoAxisIntercepts=Yes" is deleted. That means that for now Level-D 767 for FSX users who are having the problem have to change the line before every flight (before starting FSX).

Daryl

Level-D Simulations

Link to comment
Share on other sites

I am having the same problem with the LDS except it is with FS2004 and 3.75 Registered. I have tried adding the NoAxisIntercepts=Yes and this had no effect.

FSUIPC3 does intercept axes as such. There is no comparison with FSX.

Hasn't the FS2004 version of the LDS aircraft been available for a long time? I am not aware of any problems with FSUIPC and the Feelthere software, other that you may need to check the THROTTLES option centre bottom on the 4 throttles calibration page, if you use it.

Regards

Pete

Link to comment
Share on other sites

Unfortunately each time FSX closes, FSUIPC rewrites the FSUIPC4.ini and the line "NoAxisIntercepts=Yes" is deleted.

Really? How strangeI'll look at that directly. If it does it is a bug.

Daryl

Level-D Simulations

Ah, a contact in Level-D. Good. Can you tell me, please, how it is that merely my intercepting axis values and re-transmitting them, even with no change, is upsetting your A/P? It must be something odd with SimConnect, as all my control operations are 100% using standard SimConnect facilities, but I need to understand it if I'm going to ask MS to fix it, and find a work-around in the interim (other than removing the whole set of intercepts).

Any relevant details would be very welcome please. Are all axes affected or only elevator, or elevator trim, or aileron or aileron trim, or what? Is it perhaps a priority problem where I trap them at one priority and re-transmit them at another, and you are trying to collect them in between?

If we are both trying to collect them at maximum maskable priority, maybe it is an ordering problem -- in fact, maybe FSUIPC won't get them if SimConnect sends them to you first (unlikely as aircraft will be loaded later than DLLs). I don't know how SimConnect resolves equal priorities -- it should treat them equally.

Regards

Pete

Link to comment
Share on other sites

Hi again Daryl,

Unfortunately each time FSX closes, FSUIPC rewrites the FSUIPC4.ini and the line "NoAxisIntercepts=Yes" is deleted. That means that for now Level-D 767 for FSX users who are having the problem have to change the line before every flight (before starting FSX).

I've checked into this and can in no wy reproduce the problem.

I think what may be confusing you is this:

On UNREGISTERED installations of FSUIPC, the Axes are, by default NOT intercepted. There's a parameter "AxisIntercepts=No" by default, which can be changed to "Yes" if needed, but as the program is not registered and the calibrations cannot be used, there is little point.

On REGISTERED installations, that parameter is replaced by "NoAxisIntercepts=No" by default, but that can certainly by manually changed to "Yes" (when FSX isn't running of course), and it certainly then stays that way.

The only thing I can think happened to give rise to your report is that someone with an unregistered FSUIPC4 added it "just in case" it was responsible for some problem he had, and, of course, it would have been replaced by the "AxisIntercepts=No" parameter instead.

Regards

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

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