Didnt realized that, I use my clock or the mobile
nice catch
Hello,
issue fixed above around post 1195.
However even can be considered an issue take in mind that it has to be used in low level navigation using clock/heading method, it should be reset each leg end when you change your waypoint an most probably heading too.
Considering that you are going at about 7 NM per minute itâs unlikely you make 15x7 = 105 NM leg without reset the time and changing your waypoint. A good thecnique is to divide the route in shorter legs to better control navigation accuracy
Itâs been solved quickly after ![]()
Yeah I dont plan legs of more than 20nm then I ussually divide those segments into minutes depending on the speed for having a better reference if im on time or a bit fast/slow
And Hi, It could be so nice if you can share with me some of those routes, tbh donât know any routes in the us for some low level vfr flying, or the famous course rules
Hello,
news from SF260?
Best regards
External model done, textures on short final.
Internal model wip.
merry xmas and appy new year
/SSW
Hello,
since its christmas I have a âlittleâ wish:
a Orpheus reccon pod
I know MSFS dont want any weapons in the game, but a reccon pod would be cool to fly low level reccon missions.
I agree. I donât understand why at least the Orpheus pod and the SUU-21 have not been implemented. The versions with armament have been made available by other devs (Iâm thinking for example of Indiafoxtecho with his F-35) who also sell on the Marketplace, so I think itâs not impossible.
Maybe our friends of Indiafoxtecho have someone who loves them at MS, we have forbidden even a simple âGunsightâ because he had the word âgunâ inside.
So using a dirty trick we entered it as âeaster eggâ
![]()
The âeaster eggâ gunsight on this bid is kinda meh anyway, it isnât collimated properly unlike some other birds in the sim (the planes with modern HUDs and FlyingIronâs Hellcat for example)
hello,
recall we are talking of 50âs technology, it was not collimated at all.
SSW
While I also struggle to believe it was not collimated, the dev flew these IRL.
I donât mean a modern HUD but a reflector sight that was common in WW2 and even a few planes in WW1 planes had them:
or
The one we have in the F-104 doesnât act like that at all, itâs just painted in place. Look at FlyingIronâs Hellcat for an example of a basic WW2 reflector gunsight that acts like a proper collimated reflector gunsight.
So happy to see the 104 for MSFS, always my favorite military aircraft. I havenât had the aircraft (FRF Version) for long but do have three questions / observations;
- Iâm not into a lot of liveries and will likely never use anything other than RCAF, Is there a way to delete the unwanted liveries? I couldnât find the old style aircraft.cfg file that I would have edited in FSX.
- Is it possible to map one or both start buttons to a key combination so that I can map this to a controller button via FSUIPC? I like to use controls as much as possible when I fly and rather not use autostart. I did map the checklist and EPU.
- Iâve noticed that the cockpit quickviews donât return to the forward view after release of the POV as with the rest of my MSFS aircraft. If I look left the view will stay there until I reset to forward, this is contrary to the âsnapâ action of other aircraft.
Thanks
Mario, it seems Dino is not the only one to have these friends at MS. In the various F-14/15/16 of DC Design and its subsidiaries as well as in the Hawk of Just Flight the armaments are present and appear by changing the weight at the various attachment points or via tablet. And SSW too had the same possibility with your G-91. So something doesnât add up or -forgive me- itâs not told correctly (traduzione letterale di ânon la si racconta giustaâ
)âŠ
According to what you say we made and distributed two different versions (armed not-armed) of the G-91 for nothing ?
We are not so stupid, we were forced because MS refused the armed version to which we had to be accepted not only remove the weapons, gunsight and make inoperative weapon switches but also âsawâ the gun barrels protruding from the fuselage in the R3 version for the GAF.
We therefore decided not to produce more armed versions of our aircraft to avoid problems, as far i know MS policy is not changed and i donât know why aircraft you mentioned has been accepted.
But if, as you write yourself, you have produced and marketed two versions of the G-91, why not do it with the Starfighter as well? There would have been no problems with MS and you (SSW) would have satisfied many users, maybe even with a few more sales, right?
Hello,
when we released the first armed version of G-91 we were out of Marketplace (mp version was released 2 months later) and not aware of MS policy.
Making 2 versions means extra work and is error prone, moreover less than one hand fingers over thousands users asked for weapons so far.
MSFS 2020 was not made for weapons use, we agree with this policy.
We hope we donât have to come back to the subject.
/SSW
Surely MSFS 2020 was not made for weapons use, just like FSX and P3D werenâtâŠyet the weapons were there. But as you say letâs end the topic here, my question has been answered.
Buona serata e buon anno nuovo, Comandante.