I'm having problems with some of the systems on the Vulcan, is it just me not operating things properly? I'm using P3dv5 hf2 and the latest version of the Vulcan I can download.
Centre of Gravity
No matter what setting I put the centre of gravity pumps onto it goes forward to nose heavy, the longer I fly the further forward it goes until into the red, I can't work out how to get it to stay neutral. I submitted a ticket on this one over a week ago but haven't had a response. Ticket number #43105 - now getting good help from support, thanks.
Remote mode - the manual says this should steer the Vulcan to the default gps route. I have a route showing on the GPS, but remote mode doesn't seem to do anything. - now sorted, thank you
Localizer and Glide Path.
I can pick up an ILS localizer and glide path to follow manually, but the manual says the autopilot should be able to fly a glide path with the top autopilot selector set to G.P. and the bottom set to Approach, and Track and Glide selected. I can't get this to work, have I got the settings wrong? - Localizer track is being picked up now, thank you, glide path an altitude hold at lower levels still problematic
Pulling out the knob and rotating the beam compass doesn't rotate the needles, so it can't be used for following a course.
Dive /Climb settings- the fault was with the user!
edited to update as getting good support (and one issue down to user malfunction).
@Wiggi001 That's your opinion and no problem with that. It's been checked here again and we can't reproduce the issues using the latest build (from Nov 19), the FDE seems fine.
But if it doesn't work as you'd wish and that will mean you won't be using the aircraft then please contact the support team who will be happy to issue you with a refund. This Archer has been very well received since release and has become a favourite add-on for many users. However we'd not want anyone sat on an aircraft they can't use so please feel free to do as I suggest above and claim your refund.
Done to death beforehand on the old forum and over at Avsim. We had plenty of real-world Arrow pilots involved, both initially and then joining in for the initial SP. One (and only one) was adamant that there should be a strong nose-up pitching on flap extension, the rest were insistent on a fairly stable / nose down tendency. The POH doesn't help, mentioning pitching but not stating which way, but it does say that it can be easily held by hand rather than needing trimming out.
I seem to recall discussions on PPrune as well as among our testers where the same aircraft was accused of pitching either up or down, dependant on who you listened to. It's been a long time since I worked on these files, but I think that what was settled upon was a very slight upwards pitching on flap extension but that the drag created (and resultant slowing of the aircraft) would pull the nose back down.
It's a really difficult situation, there is no 'black and white' definitive answer to your question, only about ten pilots / owners who would each give their own fairly in-depth description and what we ended up with was what you have.
Sorry, I see the problem now -- I purchased the PA-28R Arrow III & Turbo Arrow III/IV Bundle, for which they are only showing:
COMPATIBILITY FSX/FSX:SE/P3D v1-v4
CURRENT VERSION 2.01
On the other hand, they are showing the PA-28R Turbo Arrow III/IV title as:
COMPATIBILITY FSX/FSX:SE/P3D v1-v5
CURRENT VERSION 2.03
So far their download file has not been updated for the bundle.
Hi, I am new here,having installed the Robin DR400 yesterday. Installing worked fine and I can load the Robin into P3d v4. I even see the Cockpit view and here the engine. But when I try to move the window to adapt it for my three screens, the P3d crashes after a few seconds. It just needs a move of the window for a millimeter (Cursor on the horizontal bar and pulling) to trigger the crash. moving and adapting windows is usually no problem with other addons.
Thanks in advance
I've got this running in P3Dv4.5
The parkingbrake leaver is to the right when brakes are on (I don't know if this is correct or not).
Undercarriage lever is down when undercarriage down
Engine start buttons don't seem to stick
A white mark would be useful, tool tips does say which is selected (1,2 or off), but I imagine some don't like that being on for immersion reasons.
Doesn't seem to be a hole in the wing on the p3d model
I remember having this problem before. I think it was something to do with locking the two fuel cocks (with the middle mouse click) after turning to number 2 tanks. I was using a mouse with a fancy middle button and I could never start the engines (this was back when I was using FSX:SE with the Lancaster). I borrowed a really cheap standard mouse and the middle click on that would activate the cocks. It's hard to know if that will be the problem for you as there doesn't seem to be any sound or visual indicator that the cocks are locked, which would be helpful.
I've just tried 3 different mice in p3dv4 (including the one I used to have problems with) and they all seem to work (pressing manual start and then trying to start up), but can't say whether that is due to p3d or something else as I have a different system entirely now.
I remember a post on the old forum having similar issues with the middle click of the cocks [http://forum.justflight.com/forum_posts.asp?TID=32497&title=ah-lancaster-cold-start-12-port-wont-start](link url)
If your props are turning, but the engines aren't catching it might be that.
7-10 - I haven't tried to use the autopilot or fuel system or guns.
Hope that's of some help.
@tedban If they don't work or it doesn't work to your satisfaction yep you'll be able to get a refund. Might be worth contacting our support team to see if they can help you out to begin with though.
You'll also need to let them know the exact product you're referring to, 1_11. Flight sim software doesn't really narrow it down very much.
Support can be contacted here: https://support.justflight.com/en/support/home
@tucanto said in DC F15 Eagle:
Thanks for your reply , (interesting detail) but I do not have the inclination to go in to all the technicalities,
I just thought I would mention it, it's no big deal I just apply the brakes occasionally.
Delta558 is correct - aircraft such as the F-15 have such a high thrust-to-weight ratio that they'll easily taxi under even heavy loadouts when under idle thrust. Just the nature of the beast. Some airplanes have internal controls to limit thrust when taxiing but I'm not aware of one for the F-15, so toe-brake dabbing is required I'm afraid.
I recently purchased the Tristar for V5 and I have some questions when following the tutorial flight:
On page 131 (section configuring the autopilot) it says:
"Switch on the flight director by right-clicking on either of the two FD switches.
Both switches will move to the centre ON position and the yellow flight director
command bars will appear on the attitude direction indicator."
Right clicking does nothing. Left click switches the FD switch to on, but not both at the same time. Also the yellow FDF command bars do not come in. See positions 4 and 5 in Tristar1.jpg.
Also on page 131 it says:
Click on the NAV switch to engage navigation hold mode. When we engage the autopilot
after take-off the aircraft will turn to intercept the first leg of our route.
Clicking the NAV switch does not show a green "NAV" but just an orange spot, see position 1 in Tristar1.jpg.
On page 132 it says:
We will initially climb to 10,000ft so rotate the ALTITUDE SELECT knob until 10000 is
shown in the window and press the ARM switch.
Pressing the Arm switch does nothing, see position 2 in Tristar1.jpg.
Also on page 132 it says:
Finally, rotate the IAS knob until 220 is shown in the speed window..
I cannot rotate the IAS knob, just nothing happens. See position 3 in Tristar1.jpg.
Also, the Aviation Master switch is "Inop", see Tristar2.jpg.
Anyone can help, or should I go to support for that? I did not use the Tristar in V4, so I am not sure if what I observed are really bugs or if I'm just doing something wrong. If appropriate, I can also do a video.
I have resolved the issue. Previously I installed an earlier version (not v5 compatible) and forced the installer to the Prepar3d v4 directory. Then running the 2.02 installer without uninstalling resulted in the error.
To solve the problem I installed the earlier version first and then I ran the 2.02 installer. Now it asks for the P3D version and installs in the proper directory. Problem solved.