Hello Dino,
I think that the problem is that I cannot get the weight below 40.600 lbs. Since I use v3.1 I cannot use tacpac and if I set the weights of fuel and stores to 0 in the fuel and payload menu and press OK nothing happens; the tanks are still full and the stores are still there. Even with all the fuel gone (dumped) the weight still seems too high. Can you please tell me how to get it down? I do see the copyright message for the STOVL gauge.
Thanks for your help,
Stickshaker
@Stickshaker
That is indeed quite strange. The F-35 should work perfectly fine in P3Dv3.1 (even without Tacpack). If you have the green copyright message the STOVL code is loaded.
I am assuming the STOVL system works and you can perform short take-offs.
Then, readings (obviously for the F-35) should be as in the screenshot (taken during hovering in P3DV3.1 - note that configurator will report the correct weight, and the gross weight is shown in both the FUEL and FCS pages):
Basic weight 32500 lbs
Fuel -> as required... in the example, I have dumped fuel down to 3492 lbs
Stores 3893 lbs (default)
Total weight: 39975 lbs -> HOVER ENABLED (control+H or control on the FCS page)
Note that if you have 0 fuel, the STOVL system should power down (as well as the engine of course)
Make sure the installation is correct and there is no conflicting software. I am very positive the F-35 works.
Hello Dino,
No, I cannot engage STOVL mode either. That is to say: the doors open but the exhaust keeps pointing backwards, as is also shown in the MFD, and the word 'hover' is red, even if I do not select hover but STOVL mode. Even after having dumped nearly all fuel I still cannot get into STOVL mode. And, as I said, I cannot change the fuel and payload in the P3D menu, not even with the engine turned off. When I change values and press OK the old values remain.
I think I installed correctly (as administrator). Is there something I could do wrong there?
You mention conflicting software. What software is known to conflict? I do not think I have any unusual software in use, but one never knows.
Thanks fior your help. Perhaps is helps to note that I installed the Tacpac edition of the MilViz F-86F and there one of the pup-up windows (shf 2; aircraft configuration) appears as a black box, so without content. Does this perhaps point to a common problem with a Tacpac aircraft installed in v3.1 without Tacpac, and could this have something to do with the F-35B problem?
The only conflicting software I know of are AccuSim modules - which do conflict with STOVL functionality (I have not verified this directly - this comes from user reports).
I have several installed aicrafts in P3Dv3.1 and I see no conflict. Tacpack code should not be the culprit here as the code is simply ignored if Tacpack is not installed.
If the nozzle does not rotate, there is something not working in the STOVL module - may be you have denied authorization upon aicraft first run...
Do you see similar malfunctions in -A and -C models?
I have several Accusim airplanes in my P3Dv3.1 and I never had any conflict with the VTOL mode.
Perhaps you were thinking about the AccuFeel module, from the same company ? In that case yes, it's better to deactivate some effects of the module for that plane (there are aircraft-specific settings in the AccuFeel window), to prevent unecessary shaking or sounds. I'm thinking about stall effects and wind volume for example.
Dino, I cannot remember what I did during the first install, but when I re-installed the package a few days ago I was not asked to authorize. Is there a way I can still authorize the module even if I did not do so during the first run? So far I do not see malfunctions in the other models; they seem to fly OK.
Daube, thanks for your suggestion. In my case it cannot be the problem since I do not have AccuFeel installed in P3D (I simply forgot).
Dino, I can now change the payload and fuel, I simply did it wrong earlier. But I still cannot get into STOVL or hover mode.
I just gave it a try in P3D v3.1.
When i loaded the plane, i got the green ribon on top of the screen about the copyright for the VTOL module.
Then I enabled the SVTOL mode with the black button on the left of the main panel: the engine turned to around 60 degres for short take off.
=> The Hover mode was in red.
Then I noticed my fuel tanks were full, so I went to "fuel and payload" menu and set all the left/right tanks to zero. Coming back to the cockpit, I could see on the fuel panel that the center tanks were still full, but the side tanks (including tips) were empty.
=> Hover was still red.
Then I pressed the "dump" function on the fuel panel. The top center fuel tanks began to empty. The Hover writing turned to blue only when the bottom fuel tanks were reached. Then I could click on the "hover" writing on the center panel, and the engine went down to 90 degrees.
Thanks for testing, Daube. I did exactly as you did but the result remains the same as before. The exhaust won't rotate (and the arrows indicating the position of the exhaust on the MFD keep pointing aft) and the word 'hover' remains red, whatever I do. I even re-downloaded the plane. No joy.
I am at a loss what to do.... I cannot imagine what makes your install different from mine.
Dino, are there any files I can send to you so that you can look whether something is wrong with them? Or should I check whether I miss files? I have FSUPC installed.
At the LM P3D forum I was told that P3D v3.1 does not ask whether to trust gauge files when you first run a plane.
Last edited by Stickshaker; February 27th, 2016 at 10:46.
One question: when you activate the dump fuel, do you see the purple fuel levels go down on the right part of the panel ?
Also, did you check your realism settings to ensure unlimited fuel wasn't enabled ?
Yes, I can see the tanks emptying when dumping fuel. And I have unlimited fuel unchecked.
Is it possible that it is some problem with Windows 10? I recently upgraded to it.
Can you post a screenshot of the cockpit view when you have dumped the fuel ?
I'm going to do that as well, to show the differences.
Here are my screenshots: I started the plane on the runway, and I activated the fuel dump until almost all of the tanks were empty.
This is how it looked like just before I reached the very last two fuel tanks. I'm still above the maximum weight, so HOVER is still red.
Then, just two seconds later, I reach the limit, HOVER turns to blue:
I deactivate the fuel dump a bit too late, but at least I can now select the hover mode (not clicked yet in my screen):
Hello Daube,
I only now saw your posts. I installed the plane in FSX and the STOL and hover modes work perfectly! I see exactly the same as in your screenshots. I do not understand why your plane works perfectly in P3D v3.1 and mine does not.
Thank you for all your efforts in making the screenshots etc.! Do you have any suggestions as to what to do next? I can’t think of anything except sending files (i.e. the hover module) to Dino. Perhaps he can to see if anything is wrong with them.
When a plane with "special" gauges doesn't work in P3D, the most common reason is the lack of SimConnect installation.
Did you reinstall simconnect from the "redist" folder inside P3D after your upgrade to Win10 ?
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.
Personally, I'm convinced there's nothing wrong in the F35 package, nor that it depends on the F35 package version.Originally Posted by Daube
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...
Members who have read this thread: 0
Posting Permissions
Bookmarks