Thank you Rudy for the quick and comprehensive reply! However that is exactly the procedure I have followed, just with a different KML file. After I press save to generate the LN3 file, I see that it has not actually created the file. I only tried on one file though, so maybe there was a problem with that one. I’ll try some of the others tonight.
Anyone else having throttle issues?
Got a saitek x52 pro and it seems to only have a small range, this happens in my G91 also. When I increase the throttle the engine only goes to idle and when I bring the throttle to idle the engine and plane go into reverse(yes I know this engine is not supposed to reverse). It used to work fine before SU7. The throttle works fine if I use the keyboard(F3 and F2). The x52 also works fine in all my other planes.
2 Likes
I’ve got an X52 and it works fine, mapped to Throttle axis and reverse axis ticked.
I have read other people say they needed to remap to Throttle1 after SU7
3 Likes
Hi all.
Considering well known embarassing problems/bugs introduced by Asobo with SU7 - and hopefully solved asap with hotfix they’re testing right now or with incoming SU8 - I’ve found a workaround to be easily able to move from front cockpit to rear cockpit and back, without the need to use the mouse and menu bar and without incurring in pilot overlapping effect.
This is a tricky procedure that - once done - in my case works 100% of times and it’s very practical since all hotas, so no need for mouse or hands on keyboard. It’s fine in VR but it should in 2D mode too.
Before describing the procedure, you need to map 2 different spring loaded switches - better 2 stick buttons - as indicated in the attached shots and here below:
Button 1 = TOGGLE INSTRUMENT VIEW 9
Button 2 = TOGGLE COCKPIT VIEW and also TOGGLE INSTRUMENT VIEW 1 (when mapping, you’ll have the warning that the button is already assigned, proceed and validate it anyway)
Then, here’s the procedure:
- Every time you enter in the TF cockpit during a new flght (or every time the aicraft is reloaded, so for example if you land somewhere and shutdown the engine until 0% rpm), with the mouse open the MENU BAR, select CAMERA icon, then PILOT, then click COPILOT. At this point the view changes to rear cockpit. Note: if you can’t click menu bar icons or selections, we know it’s a post-SU7 awful bug Asobo introduced, press Button 1 as defined above, or Ctrl-0.
- Once back, if aircraft has engine running, you should be able to see front pilot helmet and on the rear cockpit where you are no pilot-overlapping effect.
- To MOVE back TO FRONT COCKPIT: press Button 1 (and you should see front pilot disappear) then press Button 2 and you should find yourself back in front cockpit, no pilot overlapping.
- To MOVE TO REAR COCKPIT: press Button 2 and you should find yourself in rear cockpit, no pilot overlapping and - again - you should be able to see the front pilot helmet.
- See point 3 and so on…
Also, if you find yourselves not able to click VR windows (thank you Asobo!) just press Button 1 and you should be able to click normally again, no more need of hands on keyboard to find Ctrl-0 and/or lifting up your VR visor
To summarize:
- Don’t forget to do the one shot COPILOT selection at every flight session beginning or aircraft reloading.
- Button 2 to move to rear cockpit, Button 1 then Button 2 to move to front cockpit. No pilot overlapping.
- If you go to external view and then back, in my case I find myself in rear cockpit with pilot-overlapping, so - again - what I do is Button 1 (pilot disappears) then Button 2 and I’m in the front cockpit and all normal again.
This procedure, for my case at least, works always fine with the starfighter.
I hope to have been clear enough and also that this tricky but easy procedure could someway be useful to someone else, while we all keep waiting Asobo incoming official hotfix correcting (hopefuilly) all this or at least the impossibility to click the VR windows and (hopefully) many other embarassing bugs they intruduced with SU7.
Above all, fly and enjoy this magnificent TF-104G starfighter!
Button 1 assignment:
Button 2 assignments:
jk11467 by JanKees Blom, on Flickr
1 Like
Beautiful! Would love to have this?
Thanks for the reply. I’ve tried deleting the binding, binding the throttle to another axis(that didn’t work either). I just can’t figure it out. Throttle works perfect with all my other stick type planes(except my sim skunk works G92 and F104). Thanks again for the help. I’m so confused….
Just re-read your post. Going to try to re-map to throttle 1 when I get home from work. Thanks.
I also had problems with my throttle and the F104, very little movement and I also seemed to have reverse thrust when at idle.
Then I realised also that at idle thrust for some reason the parachute was being deployed.
I fixed it using Fsuipc7.
After calibrating the throttle axis with Fsuipc I have no more issues.
Probably this is not the only solution to your problem but if everything else fails you have this option as well.
1 Like
Hello,
for those that want use vACMIpartner to quickly construct .ln3 files from .kml files.
The example shown below uses an already made kml file from Google Earth.
Here a quick check list:
- cd to \Community\simskunkworks-aircraft-tf104g\Data\vACMIPartner
- run vACMIPartner.exe
- Open /close Pages ==> Open Data pages
- select LN3 waypoints tab
- click on Open .kml file on bottom bar
- on open file dialog choose a .kml file
i have selected from:
\Community\simskunkworks-aircraft-tf104g\Data\vACMIPartner\kmlFiles examples:
Delta4.xml, a round robin from LIPR
- click on Save as .ln3 icon on bottom bar
- on save file dialog i have selected.
\Community\simskunkworks-aircraft-tf104g\Data\phi-files\delta4.copy.ln3that’s all
from now on that file can be selected using the external configurator.
HINT:
checking "Export as .csv on right panel you may want have also an excel spreadsheet with legs data ,times,consumptions,etc…
hope this helps
1 Like
this aircraft is something. I don’t know if I ever will have the time to read the 500 pages POH that came with it but it is such an handful to fly around.
I cannot imagine the following link has not been shared yet, but I stumbled upon this movie by accident:
3 Likes
…and here the same exact livery: Lockheed TF-104 N991SF » Microsoft Flight Simulator
Enjoy!
Excellent video. Thanks for posting it.
It sure is. The airplane is not happy until it’s doing at least 400 knots when gear and flaps up.
jk11531 by JanKees Blom, on Flickr
6 Likes
Thanks, that’s very useful 
it also works to load .LN3 files which I have created through Little Navmap and my spreadsheet above, then save again with CSV
One thing I have noticed is that the CSV file has an extra waypoint inserted (ACC POINT) at the same lat-long as the first waypoint (which I guess is presumed to be a take-off), so if you have your first waypoint as an actual en-route point (to make the most of the 5/12 point limitation) it looks a bit odd…
Lockheed CF-104D Mk.1 of No. 417 Sqn (OTU). Last bare metal scheme for the Starfighter in Canadian service at home, circa early 1980s before Canada replaced the Zipper with the Bug…
Available now at Flightsim.to
I may do one or two more metal liveries and then it’s time for Camo paint.
9 Likes
hello,
is a placeholder acceleration point (does not changes wp sequence) to actually compute take-off data (time,fuel) in order to be more accurate, otherwise the first leg would be computed with “instant” acceleration to enroute speed.
/SSW
1 Like
Still can’t have the horizon and the NAV to work… Removed and reinstalled the full aircraft, to no avail. Followed the align procedure in the “hints” doc, but I can’t even see the orange light now… And the green light is on forever 
And still this CAUTION light I can’t shut down. Did I miss something?
