WHOGX5
-
Posts
741 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by WHOGX5
-
-
On 7/25/2023 at 5:10 AM, Nealius said:
On the SEAD side the long pod used to be effective against SA-2, causing an immediate dropped lock after launch when head-on the threat and on the extremis of the SA-2's WEZ. However now (update just prior to today's update), the long pod is wholly ineffective against the SA-2 in the same scenario, with missiles continuing to track 2~3nm outside the WEZ. Will need to test again with today's update.
IMO jammers are pretty much useless in DCS except for A-A combat. Even an SA-5 will launch at close to max range even if you're barrage jamming. This wasn't the case before where ECM would usually half the engagement range, so something has indeed changed.
-
2
-
-
Its also difficult for milsim communities who work with real life airspaces, because the tanker turns in DCS are so incredibly wide that it doesn't fit in any tanker track in the world. You need such an enourmous amount of airspace reserved for a single tanker in its current state.
-
4
-
-
This is really needed, as it's almost impossible to see the lights in daytime with a normal FOV. Also, because of the extremely bright backlighting for the Fore / Aft column it's very hard to see at night as well.
-
2
-
-
When using NVG's, the recorder behind the HUD blurs the HUD symbology, even though it shouldn't.
-
2
-
-
On 7/20/2023 at 2:08 PM, Braunn said:
Weasel pilot Dan Hampton praise the HTS pod in his book. They did do some changes to it to make it better but cant remember what it was. I can only assume they made it less work needed (as per OPs question) to operate effectively.
Yeah, I've read that book. He mentioned helping out with the development of the HTS R7 variant, but exactly what that upgrade entailed is left out, apart from being generally better than it's predecessor. I don't even know if the R7 variant is accurate for the DCS F-16C.
ED should however have access to the necessary documentation as they've modelled the HTS pod and HAS page in-game. All I can say is that I find it extremely improbable that you can't mark SAMs in the F-16CM-50, and I wish ED could bring some clarity upon this topic.
-
4
-
-
10 hours ago, Tango3B said:
Okay, got your intent there but let‘s talk about NCTR in this context. ED hardcoded NCTR to only work at/or below 25nm. This really is quite unfortunate. Why exactly is that? NCTR prints can, under the right conditions, be obtained from far greater ranges. Can we please agree on the fact that this has to be coded in a much more dynamic way? We really need to get rid of this static radar behavior. Being fully aware of the fact that NCTR always was and still is kind of a hot topic I want to point to Razbams form of implementation which really shows the beauty of what can be done. I really hope we will see some of this coming over to the F-16 in the future, too. Thank you.
All ED's DCS modules are deterministically hardcoded. It doesn't matter if it's detection range, NCTR range, MAV acquisition range, etc, etc. Everything is very simplified with arbitrary hard limits to them. Hopefully ED will pay some of the 3rd parties to copy their technologies, like Razbam's A-A and A-G radar modelling, or Heatblurs RWR modelling for the new F-4E, which is leaps and bounds beyond all ED modules.
-
8
-
-
I don't have any evidence backing what I'm about to ask, hence I'm not marking this as a bug, but I still think it is and hopefully someone can provide a factual response to this question.
Shouldn't you be able to store detected emitters on the HAD as markpoints? It's very strange that you can create markpoints using every single sensor in the DCS F-16C, except the HAD. If I send a detected emitter over LINK 16 to my wingman, the emitter will be displayed on his HSD with the correct emitter type and even a threat circle indicating the engagement range of the emitter. In my own aircraft however, the best I can hope for is to not lose track of it on the HAD and have it turn green, only to completely fade away moments later. I can not get it to display on my own HSD with a threat circle, and I cannot slew the ground radar to the emitter in order to refine the coordinates. The workflow currently has to be:
1. Bug emitter on HAD.
2. Make TGP SOI.
3. TMS Up to get a point track.
4. Create a markpoint and set as active steerpoint.
5. Switch to GM radar and cursor zero.
It's an unnecessarily convoluted process and I can't imagine that's what pilots have to do in real life. If this workflow was correct, it'd also mean that you can't mark the emitter if there are clouds in the way, as you won't be able to get a point track with the TGP. It feels like you absolutely must be able to create markpoints using the HAD in real life, because I don't see how you could be effective in the SEAD/DEAD role otherwise.
-
3
-
-
On 7/15/2023 at 6:14 AM, Nealius said:
Not sure if this is on Block 50s but it is a thing on Vipers. Someone will have to fact-check which Blocks/software. IIRC the threat circles are saved as steerpoints (numbered in the 70s I think?), so with HSD as SOI we can TMS-up on the centerpoint of the threat circle to select that as current STPT, making for easer DEAD engagements.
All of this is correct, but we still don't have all the steerpoint functionality the real F-16 does. At the moment threat circles are not stored as steerpoints, but rather they just magically exist in the aircraft, meaning they cannot be selected for targeting. And they used to be stored somewhere in the mentioned steerpoint range, but the M4 tape has 700 steerpoints rather than 100-127 in the older tapes, and I have no idea what those new steerpoints are, but my guess would be that a lot of steerpoint ranges have changed.
-
2 hours ago, _SteelFalcon_ said:
so it is intended that all DL info is lost once the radar detects a contact that was previously provided with DL and already marked as either friendly or hostile? seems weird
AFAIK, the way it's supposed to work is that if there is a mismatch in ID between L16 and your onboard sensors, the contact will flash between the two different identification types, like between unknown and hostile for example. You always need to classify a contact yourself using onboard sensors and like others have mentioned, the only thing that gets correlated from L16 for your own identificaiton process is IFF response.
-
1
-
-
3 hours ago, NineLine said:
The correct as-is tag came from your OP which you dropped out of parameters, when dropped correctly we are not seeing the bomblets going long. We do not have all the settings available for the CBUs right now so you need to drop within those parameters for now or you will have issues.
But the issue is that the NOSE fuze setting shouldn't care about any of the parameters, hence there shouldn't be a "out of parameters" drop. It just releases and activates, disregarding any burst altitude setting. Even if we get the ability to set burst altitude in the future, it will still constitute bugged behaviour if you need to drop it above the burst altitude with NOSE fuzing selected.
-
4
-
1
-
-
9 hours ago, skywalker22 said:
In the DCS F-16C we still cannot set burst altitude nor spin RPM for the CBU-87, unlike in real life where they are adjustable. "Fixed open height" is simply the altitude ED has chosen for the CBU-87 to burst at in DCS.
3 hours ago, NineLine said:Please supply a track where you release above 1500 feet and it opens right away. Working fine here.
The point is that the CBU-87 does not use the burst altitude settings with NOSE fuze set, it should dispense the bomblets immediately after release irregardless of burst altitude setting. It even says so in the DCS F-16 manual, so I don't know why this is marked as "correct-as-is"?
-
5
-
1
-
-
On 7/7/2023 at 11:26 PM, Nascar said:
How do you cycle the HCMS RWR threat? If it is showing a friendly, how can I get it to show the bandit for steering cues?
You cannot cycle it. The RWR decides on its own what the most high priority threat is, and that is what will be displayed in the JHMCS RWR circle. You can however choose whether you want to prioritize ground based or air based emitters by pressing the ALTITUDE button on the THREAT WARNING AUX panel. I would however imagine that the RWR in real life does not prioritize friendly emitters when there are hostiles around.
-
2
-
-
I think the most important thing for a DCS Korea module would be to include low detail areas of the Shandong and Liaodong peninsulas in China, the area around Vladivostok in Russia, and the Fukuoka and Yamaguchi prefectures in Japan. That would open up so many possibilities and it would allow us to stage conflicts including any combination of South Korea, North Korea, China, Japan, Russia and USA. My mouth is watering just thinking about it...
-
2
-
-
1 hour ago, Mik75 said:
Exactly.
I had no clue what was going on... Pretty sure it also comes from flying too many planes in DCS.
Remember that you can always see which mode is current'y active in the bottom left of the HUD. Makes it easier to recognize if you're actually in the mode that you think you're in.
-
2
-
-
3 hours ago, Viciam1 said:
Okay thanks. When u say vicinity....i just type in the mgrs and drop the bomb when I get ccrp drop que...
Also
U know the reaper its not giving elevation. This is a big issue coz if I want to use tgp its not possible.
Is there a way around this.
You could use the ground radar to lock on to the target STPT location. Just cursor zero and TMS Up. That way you should get accurate elevation data on the correct coordinates.
-
On 3/19/2023 at 8:13 PM, imacken said:
So, as the TM says there should be a square for negative IFF response, and Wags's video from a few months ago shows a yellow square for a negative IFF, has the behaviour changed recently? Just curious.
It's true that you get a yellow square for negative IFF responses. However, in DCS we currently only have Mode 4 which doesn't respond unless the interrogation pulse matches a certain key, meaning you'll never see a negative response. Once we get Mode 1, 2 and 3 transponders however, you will start seeing negative IFF responses as they always respond to an interrogation pulse.
-
9 hours ago, llOPPOTATOll said:
technically speaking, the block 50 in dcs should be able to use NAVFLIR even with the WAC hud. The CCIP block 40s cant use TFR either, because it was removed from the CCIP software
Where have you gotten this idea from that the CCIP upgrade removed TFR capability? That is simply not true and there's plenty of documentation to prove that. You can see many F-16's around the world still use TFR and the whole idea behind the CCIP software was to increase commonality between all F-16's, not decrease it. I mean, you can even see the TFR page in the DCS F-16C, it's just INOP at the moment.
But you're completely right that the Block 50 can use the NAVFLIR and TFR with the WAC HUD. The only issue is that ED has said that they won't be implementing the NAVFLIR for the Block 50, as it was not really used by USAF block 50s. Block 50/52's that were exported abroad however have been using NAVFLIR on the WAC HUD.
-
1
-
-
On 5/23/2023 at 8:01 PM, BIGNEWY said:
Hi,
not at all, current work is listed in the roadmap
Is there any progress being made on resolving bugs? I'd love new features (especially DTC capability) but at the moment pretty much every system in the F-16C is bugged in some way which is really annoying and it feels like fixes are few and far between. I'd be really happy to see some progress on that front as well.
-
8
-
1
-
-
24 minutes ago, MAXsenna said:
I'd really love a downgraded older version.
But that's me!
Sent from my MAR-LX1A using Tapatalk
Agreed! Honestly, I'd be ecstatic if ED just added a 2007 era Block 40, which would be minimal work as it has the exact same software as the Block 50, only with the addition of the WAR HUD and the LANTIRN navigation pod with FLIR repeating on the HUD and terrain following radar. Of course, I would also love some PW engines and a pre-CCIP Block 40/42 like the ones used in Desert Storm...
-
1
-
-
14 hours ago, twistking said:
Hello,
i'm still struggling to refuel in the Viper, but slowly getting there (ithinkhope).I do however sometimes encounter an issue that i did not experience with other aircraft:
Sometimes the boom operator just refuses to do his/her thing: I'm aligned perfectly (judging from the light indicators on the tanker), but just nothing happens. I also do not get a radio call to abort or something. My two theories on what might have happened are that either i have touched the boom while creeping into proper formation which broke the AI procedure, or that i was approaching from too low to trigger/initialize the boom operator going active (when approaching with correct altitude, there is that moment where the boom goes active and "lifts" above your canopy).
I know it's not a lot of information, but i'm sure someone has also encountered that and might give some tips on how to avoid that situation.Bonus question: Often i find myself looking at the HUD, especially the velocity indicator. I assume that it would be better to focus only on the tanker. Can i just disable the HUD, or do you think that having the HUD on is helpful during certain phases?
As no-one has given you an answer about how the DCS boom tanker actually works when it comes to connecting, I will do so now. There are two factors at play:
Factor #1 is your position relative to the tanker. The reason this is important is because in DCS the tanker will keep the boom extended half way before you connect. He will not extend the boom to connect to you but he will retract it, so you have to come to him. This means that even if both position lights are green and centered, if you're refueling port is in the further away half of the green and center area, you will not get a connect. The way to solve this is to make sure you keep moving forward so you know that the tanker can reach you with the boom without extending it more than half way. My preferred way of doing it is to simply keep the Up/Down lights green and centered, while you just go one notch closer than center on the Fore/Aft light to be sure that he can reach you. As soon as you get a connect, you can move back to a fully centered position.
Factor #2 is your speed relative to the tanker. The boom operator will move the boom quite slowly, so if you have a even just a few knots of speed relative to the tanker it'll probably be enough for the boom never to catch up to you. So once you know you're in a good position, based on the info for Factor #1, then you need to slow down and maintain a similar speed to the tanker for enough time so that the boom operator can move in for the connect.
And like others have mentioned, it's always useful to look at the replay where you can see exactly what's happening at any given time.
EDIT: And about the HUD, for the love of god, don't look at it. Just look at the tanker fuselage to be able to judge relative movement and look at the position lights to judge which relative movements you need to make. There's no reason to turn off the HUD, but you shouldn't look at it either. Every millisecond you spend looking at the HUD will delay any corrections you make when you eventually see yourself moving out of position. If you start slowing down for example, you should be able to react to that by adding more thrust before the position lights show you moving out of position.
-
1
-
2
-
-
13 hours ago, SickSidewinder9 said:
Shouldn't there be a ram air turbine somewhere for when we lose all power? Is that a custom thing for countries that didn't want to deal with hydrazine? I thought the hydrazine just restarted the engine, and the RAT is for when that wasn't an option/didn't work. Right now, without engine, we have nothing.
If I'm off, tell me where and wrong and lock the topic and let it die.The F-16C uses an EPU to generate emergency power. Unfortunately it's not implemented properly in the DCS F-16C so you will lose most important systems if your engine dies, making the EPU practially pointless. This has been reported years ago but there is still no fix in sight.
-
1
-
-
Follow up to the video above:
-
1
-
-
2 hours ago, SFJackBauer said:
Sup everyone.
Sorry for the blackout. Things in life happened and I ended up taking a break from DCS for a while. The break then got longer, then longer, and then longer until now. I did not had headspace to think about this, but I should have at least left some message here.
In any case, this is done in a completely voluntary basis. I added p-louis way back as a contributor to the repository since he volunteered to implement the Hornet and the Apache, and I can see he has done a lot in that regard. I will try to dedicate time to support what has been done and improve in any way that could be done, but the primary module I fly is the F-16 so that is where I spent more time developing.
Now I want to address some topics:
- Error about TCP connection on port 43001
The DTC software works this way: It has a bidirectional connection to DCS, to send and to receive data. To receive data, the DCS lua script opens a UDP port 43000, which the DTC software reads. This port is only read when doing waypoint capture from DCS. On the other hand, to send data, the DCS lua script opens a TCP port 43001, and the DTC software tries to connect to this port when doing the upload to jet. If the DCS lua script does not create the port, the DTC software will error when trying connect to it.
Therefore the most common reason for this error is just an improper installation of the LUA script in the Saved Games folder. If you follow the install instructions it should work. This is the same way other mods that needs to read/send data to DCS work.
- Virus warnings
Virus detection is a complex subject and the antivirus tools uses a series of heuristics to flag an executable as malicious. For example, the fact it needs to connect to the lua script may be a factor to flag it. Also there is no installer and Windows tends to flag executables downloaded from the internet as suspicious. Its a fact people use liberally other mods (from DCS and other games) without checking its source code and the reason they do not get flagged is just because an installer is used... and thats fine because security is also a function of the perceived trust and the empirical evidence of the software actually doing something weird. To be honest, the safest way if you are paranoid is to never download any executable from the internet at all, but who lives like that? In any case the DTC code is open and anyone can always inspect it and/or compile on your own machine if you are willing to go to that length. Or... not use it at all.
With that said, I will investigate adding an installer if this just means making it less bothersome for people who actually wants to use it. I've inspected the latest version of the code and there is nothing implemented beyond the purpose of the software.
- Discord
I am considering opening a Discord server dedicated to this mod, so people can discuss it, suggest features and support each other. Is it something worthwhile? I would like feedback on this.
Cheers.
Glad to see that you're back! I just want you to know how invaluable this software really is. In my community DCS DTC is mandatory and we use it every single session, doing all of our planning in CombatFlite. Any further developments are welcome, especially to the F-16C!
And if you created a discord, I'd join in a heartbeat. I have both feature requests and at least one bug report that I can think of off the top of my head. It'd be good to have a discord server to discuss these things in a more organized manner than a single forum thread.
-
6 hours ago, eatthis said:
yeh its a rocketship in that midrange speed bracket! the tomcat isnt exactly sluggish but damn the viper is great there, that aoa limiter makes low speed a bit of a dead end though, apparantly that was a noted thing in bfm for real, clever/good pilots would try to force the viper slow and then drive the nose of their jets around knowing the viper simply cant
Yeah, it is absolutely essential to stay fast in the F-16. Most aircraft in DCS prefer lower speeds than the F-16, so the only thing you have to do is to not get baited into lowering your speed and stay fast. If the opponent starts slowing down and is turning inside of you, take it out of plane into the vertical and use your energy advantage to defeat him. Like you said, the AOA limiter in the F-16 prevents you from outmanouvering practically all aircraft at low speeds and it will also take you ages to accelerate up to a higher speed again so it's best just not to slow down in the first place.
8 hours ago, Temetre said:Thank you for the tips! Im currently working trying to learn F-16 dogfighting, again, and Ill try to put that band to good use.
Currently im just going over basic dogfighting theory. Ive played a bunch of flight sims, mostly WW2 before DCS, but usually flew by feel. Can beat the AI with F-16, but im working into the how and wanna try multiplayer later.
Btw, the behaviour ive been talking about? I think that was more like a semi-stall that i was experiencing. Actually had a double check looking at the AoA indicator, but I was like >20 degrees off. Weird thing is, the FBW system made it feel like im still in control of the aircraft, that threw me off. Doesnt happen like that in the F-18, and the Hornet has a pretty useful alpha-indicator on the hud.
Just a weirdly unintuitive thing I havent experienced in this way in any other aircraft. Definitely gotta work harder to keep my F-16 at a the right angle.
Yeah, because of the AOA limiter you'll basically never enter a real stall in an F-16 unless you do some really specific maneouvers or run some crazy assymetric loadout. Usually when you get slow it just gets kind of sluggish before the FLCS starts slowly letting the nose down. In an F/A-18C, for example, you have so much AOA available that you can practically point the nose anywhere you want at low speeds. The F-16 is so limited in AOA that even if you're well above the stall speed you still can't really move the nose anywhere but down towards the ground.
-
3
-
FCR In CRM mode, TWS "bumping to a 60* fov by cursor. not functioning
in Bugs and Problems
Posted
AFAIK, it's because RWS is used both to search for and to engage contacts, while TWS is only used to engage contacts. This means that with RWS you're constantly changing which volumes of airspace you're searching through, hence bump range and bump azimuth makes that process much more efficient.
However, TWS is only used when you've already found whatever you're engaging. The distance from the target group where you switch from RWS to TWS in an engagement is predetermined in the mission briefing. Becuase of this, TWS settings like range or azimuth are simply loaded from the DTC and not meant to be changed while flying. The removal of bump azimuth means that you can move your cursor freely without worrying about accidentaly changing any azimuth settings.