Chain_1
-
Posts
148 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Chain_1
-
-
After today's update, the pitch ladder and flight path indicator displace to the side of the HUD at around 90 degrees of bank in either direction when in DRIFT C/O. NORM is working normally. Track attached.
-
I assume that it would be expanded, but I'd like to know for certain, as well. The mountains in the northeast provided some great scenery, plus Bagram, J-Bad, Kabul, and the Mez are there. And I want to provide cover to FOB Shank because it got mortared all the time.
- 1
-
Use Rt Ctrl + \ to open the menu for comm 2. Also input the correct frequency: 131.00 in this case.
- 1
-
I noticed it in the last update or two as well. You're starting the toss right at the edge of the envelope and drifting in and out of it, based on what people are saying in another thread. If you wait a few potatoes after the max toss cue, or use a lower toss angle, you'll see it doesn't happen.
-
2 hours ago, Temetre said:
Btw what are these sytems on F16 and F18?
The Mk 1 Eyeball.
- 1
-
On 4/23/2023 at 9:48 AM, lethal205 said:
...so I wouldn't keep your hopes up for future updates.
Especially considering that ED is actually working on the DTC, according to the roadmap.
-
To make it easier on yourself use 3000' at 10 mi (1 deg = 100 ft/mi) since math kills lift. If you look into the 60:1 rule, there's a bunch of things you can mentally figure pretty easily if you round a bit, i.e. 1 NM = 6000' instead of 6076'. It's all close enough. Technique only.
- 1
- 2
-
Check out the community keybinds mod, it has slower options for you to bind.
- 1
-
Use the landing light for takeoff/landing, and the taxi light for taxiing.
- 1
-
razo+r is correct, you were looking too low with the radar. A fighter's radar isn't an all seeing eye, for want of a better term, it can only see in a cone. It won't detect anything outside that cone. This tool (https://tawdcs.org/radar-f15/) was made using the F-15's radar, but the principles are the same. Use it to practice locking contacts, and that will help your understanding of the system.
-
1 hour ago, imacken said:
However, I will say that the unknown IFF square does not appear ever as mentioned by @Chain_1 above.
Has this bug been reported?
I was looking around yesterday and it looks like it's not a bug.
-
I just tried it in MT and ST and the NCTR worked as advertised in the training mission. The unknown IFF return did not show in either though. Have you tried a repair?
-
In the meantime you can also use this: https://www.digitalcombatsimulator.com/en/files/3312680/ You set up your programs under the special options tab so you don't have to mess with the CMDS pages every time.
- 1
-
2 hours ago, AvroLanc said:
No, this is not the solution.
Yes it will make the bricks more visible, but it doesn’t address the bug. The GMT and SEA modes are both displaying terrain mapping incorrectly in MT.
They should not display ANY terrain unless the INTL (interleaved) option is selected, and then only on alternate sweeps. Compare this with the correct behaviour in Single thread.
Brick visibility was the OP's issue, but you are correct in that the terrain was not displayed by default in GMT/Sea pre-patch.
-
Just tried your replay in MT and both worked as advertised. The issue was needing to turn down the map gain under the data page (like in the Viper, if you have that). The GMT bricks blended in with the terrain until I turned it down.
-
You also should make the Mav SOI and TMS up on the same object you're looking at through the TGP so that it's locked, then hit BSGT
- 1
-
Negative. The F-15C does it perfectly because it is a lo-fi aircraft. You'll have to manually spin the HSI in the A-10. That said, the waypoints can cycle automatically in the HUD/on the TAD.
-
It's an intro level vid, but it's up now.
-
Double check your control axes for any binds. I have the HUD/JHMCS brightness bound to some controller axes, and if i move those controls after a hot start that will cause the HUD or JHMCS to instantly turn off and then back on while the game matches the physical axis position, and it looks like what you described.
-
2 hours ago, _SteelFalcon_ said:
that's not true, you only have to boresight the pylon. DCS has it working correctly afaik
Looks like I misremembered. I was thinking of stepping through the missiles, the boresighting works as you say. I just tried it.
-
1 hour ago, Shrike88 said:
Is there a known issue with the TER’s vs a single mount that’s know of ? Seems not all are calibrating when using the TER
If memory serves, this is an ongoing issue. You should only have to boresight each rack, but currently you have to do each individual missile.
-
31 minutes ago, darkman222 said:
That does not make sense. If the IFF transponder is damaged or just off by mistake is enough to get you shot down by a coalition aircraft?
Not enough by itself, there would be procedures in the SPINS/ROE that would address such a situation and hopefully prevent friendly fire.
-
On 1/30/2023 at 3:39 AM, buceador said:
A female friend of mine who has recently got into DCS was astonished that are no female pilot models available for any of the aircraft!
20.0% of USAF pilots are femaleEven the Russian Federation has its ‘angels of death’, female pilots!
ED?Hope she sees this, bro.
- 1
-
There are certain conditions which will disconnect the autopilot. What were your flight parameters at the time? If you put the gear down or set the air refuel switch to open, for example, it would disengage. I couldn't get it to disconnect just by going to the F10 map.
Drift C/O and wind
in Bugs and Problems
Posted
First track was from an air start so I can't check the alignment, but to help troubleshoot I tried a cold start with both a stored heading and normal alignment and the behavior persisted. I ran a full repair, and the behavior still persists regardless of alignment or type of start. That said, I didn't do myself any favors in the last track by doing a roll in normal mode first to show it was working properly. Here's a track where I only use DRIFT C/O. First I roll right and go a bit more and less than 90 degrees of bank, then I go left and do the same. You can see the pitch ladder and flight path vector rapidly move to the top and bottom of the hud as I go to either side of 90 degrees both ways. To be clear, the ladder is oriented correctly, i.e. perpendicular to the ground. It did not used to behave this way. However, if you all are seeing the ladder remain caged as it does at all other angles of bank, I guess I have a different problem.
hudladderDRIFTCO.trk
Here's some pics to show what exactly I'm seeing.