F-35 Lightning II version 3.0 for Prepar3D v2.5

Hello Daube,

No I did not reinstall. Now there is an interface folder within the redist folder with several variants of simconnect, apparently: for ESP and several versions of FSX. Some have a simconnect.htm file in it, others not. Can you tell me which file I should install?
 
You should install that one: \redist\Interface\FSX-SP2-XPACK\retail\lib\simconnect.msi
This is an executable file :)
 
Hello Daube,
I double-clicked on the file and then I very briefly see a message to the effect that the program is configurating the computer (I think, the message is gone in an instant) and then nothing happens anymore. Does that mean that there is something wrong or that simconnect is already installed? After all, in FSX the gauge works OK. Should I look for something being installed in the P3D folder? May the fact that I am running P3D from an external disk and FSX from the internal harddisk have anything to do with it? Anyway, the STOVL gauge still does not work… I have the impression that only some accompanying visual effects work (the doors open) but not the gauge itself (the exhaoust rotating)….
 
Well the short install time is normal.
But the VTOL mode still not working is not. Honnestly, I'm out of ideas here :/
 
Hi Hans, I dont use this latest F35B, nor do I have P3D.
Just noticed this thread.

But if you call me (see PM) maybe I can diagnose the problem interactively while you try things.
Because (as far as I know) the STOVL function hasn't changed.

Cheers, Rob
 
Hi Guys,

I just got of the phone with Hans ("stickshaker") after 2 hours trying, and we finally found the culprit.
Which is quite disturbing !!

It appeared that the gauge VSTOLControlIPC_Function.xml (which controls all STOVL functionality) was NOT loaded.
Which explains everything Hans decribed, and why it wouldn't work (so nothing to do with weight or installed modules).
I could induce exactly the same problem by removing this gauge (and test it in FSX).

The problem is the filename length of the gauge; renaming it (and in the panel.cfg off course) to VSTOLControlIPC_Funct.xml (so just three letters shorter) solved all his problems; all works perfect now. !!
(and changing it back: same problem again. So it's repeatable !)

Now, the million$ question: why does only Hans have this problem, and others (as we know of now) not ???
His configuration: Windows10 (fully updated), with P3DV3.1 installed on an external harddrive, and FSX-Accel installed on the local C: drive.
Note that Hans also installed the F35 in FSX, and that worked perfect WITHOUT this name change of the gauge.

Any idea's ?????

Cheers,
Rob Barendregt
 
Could it be that the F-35 installed on my sim is not the latest version ?
It seems to me I had installed the latest one, not so long ago... but I could be wrong.
Anyways, I checked the xml gauge you mention and mine if named ....Function.xml.
And the panel.cfg refers to that very same name.
 
Daube said:
Could it be that the F-35 installed on my sim is not the latest version ?
It seems to me I had installed the latest one, not so long ago... but I could be wrong.
Anyways, I checked the xml gauge you mention and mine if named ....Function.xml.
And the panel.cfg refers to that very same name.
Click to expand...

Personally, I'm convinced there's nothing wrong in the F35 package, nor that it depends on the F35 package version.
I suspect it's a "bug" in Windows10 or P3DV3.1 or the USB external disk driver, which only becomes apparent in a configuration like Hans is using.

But that's only educated-guessing, untill we know what other people are using if they experiance the same problem .....
Or a very clever guy that knows / can isolate the origin of this problem ...

Rob
 
All - sorry for not having partecipated to the thread... it was a busy weekend.

I tend to agree with Rob - note that there is no difference whatsoever between the freeware or payware versions in terms of STOVL code - nor there is any change from v3.0 to v3.01 of the F-35 in that respect.
It seems indeed some odd behavior of Windows... we'll see if some guru can help with that.

Just for the sake of stats - Stickshaker is only user reporting this issue (out of about 200 copies sold so far).
 
Sounds a bit like the file path/name is too long issue in windows but then again if it was, you should have had issues renaming the file...
 
Roaming through the P3D forum there have been some very strange happenings due to either the language of the PC not being US English or the user name having special characters in it.... may be??

Jorge
 
Rob has been so kind to investigate the issue and has apparently found a solution - which is related to loading times. I'll let Rob comment on this once it is confirmed to work.

If it is confirmed to fix the bug, it will be included in the next update of the payware F-35 - that will also include other features which I'll disclose soon.
 
The problem that Hans ("stickshaker") was experiancing (and I can induce myself when using the package on FSX-Acceleration too), has to do with a "bug" (or whatever you want to name it) in FSX / P3D.
I.e.: when a gauge is loaded at aircraft/flight load, the gauge is already running whilst FSX / P3D doesn't accept Events issued by the gauge yet, during initialisation of the flight.
This "deaf" time highly depends on your PC speed, and how FSX / P3D loads (from harddisk, from the Windows cache, SSD, etc.)
Most of you probably have a faster PC then me, and run P3D from a local drive; unlike Hans who runs P3D from an external USB drive.
This explains why probably no-one has seen this problem before using this F35 package ......

I fixed the problem, and sent an update to Dino and Hans.
Just waiting for Hans to confirm that this indeed solves his problem, or if there is a "filename" problem as well (on top of this timing problem).

Rob
 
This will be a good reason to update the F-35 package... actually the number of reported bugs is quite small, but there are few points that need working.

Some things I have been working on:
- Solved minor texturing issue (not much visible in P2.5 - but mouch more evident in 3.0)
- ICAWS updated to include audio cues
- "no geometry" cockpit model for cockpit builders
- Minor improvements to handling (for better realism)
- Improvements to refuel system

Suggestions / requests welcome (although I can only promise to consider them!)
 
Hello, back from a short business trip. Rob, thanks so much for your efforts! I can now fly this beautiful plane and can wait for TacPac to appaer on V3.1 to enjoy all its features. I will test your solution tomorrow (need to get some things sorted out first) and report back. Dino and Daube, also thanks for your help!
 
No, not yet - I will work with VRS to get it solved.
As of today - the seeker seems to correctly identify the laser spot... but guidance fails in most cases.
 
I tested the file that Rob sent me, but it did not make the VSTOL gauge work. I re-installed the file but no luck (Rob, I adjusted the panel.cfg etc). For me, shortening the filename works fine. I do not know what to conclude from this as regards the loading time issue.
 
Stickshaker said:
I tested the file that Rob sent me, but it did not make the VSTOL gauge work. I re-installed the file but no luck (Rob, I adjusted the panel.cfg etc). For me, shortening the filename works fine. I do not know what to conclude from this as regards the loading time issue.
Click to expand...
Hi Hans,

Neither do I know what to conclude.
As we tried sunday, the evidence (on your PC) was clear that it has something to do with the filename, because we tried that consistently back-and-forth a few times.

And that's a problem that has nothing to do with the loading time problem.
I just found that by accident, when trying a few things for myself.

Anyway, you know how to solve it for now.
We just have to keep our eyes open if we ever hear of such a problem with another user.

Cheers, Rob
 
You must log in or register to reply here.
Back
Top