Link 16 things you want in the next update
-
@NIL:
More steerpoint lines available. Having ten instead of four will make it easier for any MC to build mission SA. Would also like to see the engine data for the RDAF F-16 be updated with the PW220 instead of the PW200. This was updated on all RDAF F-16 1½ years ago.
That means more STPT than 99?
-
-
That means more STPT than 99?
No, steerpoint lines that you can put in when planning a mission. Marking a border, tanker track etc. Here seen as blue, green and yellow boxes.
-
@NIL:
No, steerpoint lines that you can put in when planning a mission. Marking a border, tanker track etc.
They go with STPT numbers.
-
But you only have four lines to build a complete SA with…
-
-
True…
-
-
…I thought there was a North arrow already in the display somewhere? I seem to recall having that pointed out to me…but yeah, I do like this one better - very easy to see!
…may the North be with you.
-
An option to randomize various switches’ states during a ramp start. Perhaps not all, but a few which could be in certain positions. That way one would have to pay more attention instead of just running down the start from muscle memory.
Perhaps it saves the button state after you exit a mission (a plane)? I can see that being more complicated to implement instead of just a randomizer.
-
…I thought there was a North arrow already in the display somewhere? I seem to recall having that pointed out to me…but yeah, I do like this one better - very easy to see!
…may the North be with you.
Hi, Stevie,
You got me curious, so I jumped into BMS IA for a moment. There was a north arrow on the TGP, but not on radar or HSD. I also noticed something interesting. The north arrow was pointing to 3 o’clock on the TGP. But, the little triangle on the HSD Bull icon,which I thought meant north, was pointing to 1-2 O’clock.
BTW, Luke, I’m your faaather. -
Yes - the triangle on the Bull icon points at the Bullseye, and the North arrow points North…I think…just to add to the confusion!
But now you know the way to cross check your spatial orientation wrt Bullseye.
-
Hi, Stevie,
You got me curious, so I jumped into BMS IA for a moment. There was a north arrow on the TGP, but not on radar or HSD. I also noticed something interesting. The north arrow was pointing to 3 o’clock on the TGP. But, the little triangle on the HSD Bull icon,which I thought meant north, was pointing to 1-2 O’clock.
BTW, Luke, I’m your faaather.Well, thats interesting! Also thougt, that both are showing north.
EDIT: I realized you spoke of the Bullseye indicator in the bottom left of the HSD. Thats correct, that one is directing to the Bullseye. But there is a northpointer in the HSD. Its on of the rings of the HSD, they are seperated into quadrants with 3 little lines and one little triangle on the outside of the ring. The little triangle shows north.
At the moment I also have another problem, my HSI always is off to the navdata in the HUD with 1-2 nm, in mY cockpit as well in 3D-cockpit, don’t have any clue, where that comes from. The problem is also certain to the TD box and the STPT Diamond in the AG modes… really annoying. Problem occurs with different alignments, from 1.5 to 8.0
-
Is one showing mag North and the other showing True North? Or NM vs SM?
…or slant range vs ground distance? I think the HUD always shows slant range. I think…
-
An option to randomize various switches’ states during a ramp start. Perhaps not all, but a few which could be in certain positions. That way one would have to pay more attention instead of just running down the start from muscle memory.
Perhaps it saves the button state after you exit a mission (a plane)? I can see that being more complicated to implement instead of just a randomizer.
Saving cockpit state is already existing. And a switch randomizer is easily implemented with existing run scripting as well
Gesendet von meinem SM-G930F mit Tapatalk
-
Saving cockpit state is already existing.
I can’t find information in the BMS-Manual and BMS-Technical-Manual regarding the cockpit state saves (I searched the documents for the keywords). Page 130 in BMS-Technical-Manual mentions the cockpit save states and some things which get saved. Does it also save the state of all the switches and not just the ones mentioned there? It also says that it saves some ICP settings. Would that be considered realistic? Can those things be programmed into the DTC?
a switch randomizer is easily implemented with existing run scripting as well
Can I do that already for every campaign mission? I thought those were for TEs.
What I wanted was something which would achieve the effect of someone shutting down the plane and the switches still being all over the place. Then when you do a new start, you “inherit” that plane and have to pay more attention to the switches at a ramp start (instead of them always being in almost perfect positions).
-
But to have everything in the right place is acutally more realistic. Crewchiefs will setup the cockpit prior the pilot entering the aircraft. So there might be a switch set to something different on the HUD Panel but thats more or less it, everything else has to be where it is according to the checklist the groundcrew is working with. Of course also the pilot hast to check certain switches before continuing with the startup and of course the groundcrew can oversee a switch set to a wrong settings at any given time, but I’m sure that won’t happen very often, as these guys are highly proffessional at their jobs.
-
I didn’t know about the crew-chiefs working on the plane beforehand. In that case it’s acceptable the way it is now.
-
Only can talk about RL procedures for Ground based systems. But beeing a tank officer for 15 years. Shutting down the Vehicle / Weapons system we would always follow the shutdown list to the point as we don’t have a ground crew that would recheck or prepare the system for the next start up for us
Gesendet von meinem SM-G930F mit Tapatalk
-
What I wanted was something which would achieve the effect of someone shutting down the plane and the switches still being all over the place. Then when you do a new start, you “inherit” that plane and have to pay more attention to the switches at a ramp start (instead of them always being in almost perfect positions).
But to have everything in the right place is acutally more realistic. Crewchiefs will setup the cockpit prior the pilot entering the aircraft.
The cockpit setup (reset) takes place after each flights, following pilot egress from the cockpit. Crew chief check prior the pilot entering the aircraft is mainly a 2nd check (switches could have been flipped during various maintenance in between by maintenance personnel for example).
Then the pilot do a 3rd and last check before startup.