Fred00
-
Posts
337 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Fred00
-
-
Good discussion guys. However, the fact that the trim is too coarse/insensitive is only part of the problem. An even bigger problem is (like the track shows) that the plane can stay trimmed for a short while and then suddenly start rolling in either direction, and even change direction of roll all of a sudden with out any input. This fact makes the A-10C in DCS quite annoying to fly.
It's a bit strange that the developers can't chime in on this. Maybe there's some kind of purpose behind this behaviour and it would be nice to hear about it (if that's the case).
-
ASAP: Sorry for the late reply. I checked the slip indocator, but it's dead center, so no rudder issues from what it seems.
Don't know about the loadout, will check later. This is the instant action mission "Takeoff" for Syria. However, the problem doesn't seem to be loadout since the behavior is present in every mission.
I have also checked my control bindings and there are no conflicts or other issues there.
You can use the Syria "Takeoff" mission to test the behavior. It shouldn't matter which mission, but to be on the safe side and rule out any other differences. After takeoff, trim out the plane and then wait and see what happens. It might fly straight a little while and then suddenly start to roll. Just keep going and it will probably start to roll the other way after a while.
-
I wrote about this in a thread in 2020 and coming back to the A-10C it's disappointing to see that this is still an issue.
So in short:
The issue is that the A-10C seems impossible to trim out, most notably in the roll axis. Once it seems that you have managed to trim it out it soon starts to lean one way or the other. Interestingly enough I found out that it leans one way for a while, and then suddenly it starts leaning the other way, without any input other than pitch trim (to keep it somewhat level). So is there some kind of wind effect that affects the trim dynamically or what is causing this? I have attached a track file and this effect is best seen in the last five minutes or so, where the plane is tilting left and then suddenly starts straightening up without any roll trim applied. -
Thanks for your reply. I tested it again, but ut didn't work. So just to be sure I checked the bindings. I had these:
Coolie press up - mapped to down
Coolie press down - mapped to nothingSeems crazy, because I have never touched the bindings for this module. Either way, I'm glad I found the problem!
-
I have the Warthog throttle. When I start (for example) one of the instant action missions in Georgia the HUD is set as SOI. I press UP on the coolie switch on the throttle and the HMCS is set to SOI. Now, the problem is that if I press again nothing happens. The way it is described in the manual, successive presses of coolie switch up should change SOI between HUD and HMCS.
As it stands now, I can not find a way to return SOI to the HUD. Has something changed in the HOTAS logic or am I misunderstanding the manual?
-
I can't really find the answer to this: Is there any real purpose to TGP ATRK (area track) mode? As it seems now it works just as well to leave it in the slewable OPR mode. I can still use laser guided weapons by just designate the target point. What is the benefit of switching to ATRK?
-
Thanks Frederf, what a great reply! What I get is that it is not always obvious what mode is best to use, and sometimes two different modes could do basically the same job. With your description and more testing I believe I will get a hang of it. With some experience one will probably know instinctively which mode is best in different situations.
-
1
-
-
Thanks for the replies guys. Good info about EOM off boresight shots. I just tested and it works like charm. One question though:
Why does PB have longer range? If I'm flying straight towards a SAM and launch, both EOM and PB will loft. Why is the range in PB longer? Shouldn't they be about the same in that case? I have to confess that I haven't tested in the game, but I will tomorrow.
Also, another question. In the Nevada instant action mission with HARM and russian SAMs the briefing says "SAM target 2 and 3 are tactical mobile SAMs. As such, only their general position can be determined. SP2 and SP3 are in the general location of these SAMs. POS RUK mode is not viable for these targets. HAS is the recommended mode".
Isn't POS RUK actually a good fit for the scenario above?
-
So I'm studying the HARM at the moment, trying to get a firm grip of when to use which mode. Unfortunately there seems to be few descriptions detailing when to use each mode. Tell me if I'm right or wrong:
EOM: The most exact mode. Primarily used when we have a steerpoint on the exact location of the SAM. HARM missile lofts for greater range.
PB: A little less exact than EOM. Primarily used when we have a steerpoint in the vicinity of the SAM. HARM missile lofts for greater range. Lofting cues are also shown on HUD in this mode to increase range by aircraft pitch up.
RUK: Used when we only know the general direction of the SAM and not the range. HARM does not loft, and goes active shortly after launch to search for targets with a 120 degree FOV.
A few questions arise:
1) Is there any real benfit of using EOM over PB? PB seems to do the same thing just fine.
2) Even though lacking HUD lofting cues, lofting before launch seems to work fine in EOM too. Just pitch up 25 degrees and pickle. What is the advantage of lofting in PB mode? Also, lofting does not work like in the Hornet, where you hold the pickle button, pitch up and the missile is launched when the flight path marker passes the lofting cues. In the F-16C the missile is launched immediately when pressing the pickle button, even if the flight path marker is still behind the lofting cues. Therefore, exactly the same thing can be achieved in EOM as in PB (it seems)
Thankful for some input from more experienced Viper pilots.
-
1
-
-
I'm trying to make an SKU fix type 1 but I can't get it to work. I'm in SPA master mode, press LS/SKU button, radar trigger to T1, cross hair over target and hit TV, and nothing happens. No S1 is saved when I press "1" on the keypad.
On the other hand, MÅL mode works as intended. After I've made the target fix, M1 is saved at position one and I can transform it to S1 by double clicking LS/SKU button and then proceed to make the second fix after 3 minutes.
Have I misunderstood? Shouldn't it be possible to make an S1 point directly without first making an M1 point and having to transfer it to the SKU layer?
-
First, after pressing L/Mål and hitting T1 the crosshair on the radarstick works as I have configured it in the control settings. Then, after converting my M1 to S1, I hit T1 again to take the second fix. Now the Y-axis on the radarstick is inverted, so if I previously pressed up to make the crosshair go up, I now must press down to make it go up. That has to be a bug right?
-
1
-
-
I mentioned this several years ago but coming back to the Viggen recently I noticed that it is not fixed yet. Such a simple thing to fix, yet so annoying when flying the module.
1) The weapon selector dials rotate left with a right click while the TILS selector rotates the opposite way.
2) The two radio knobs rotate in the opposite direction to each other.
To make things easy I think all dials and knobs should rotate in the same direction. Preferably they should rotate right with a right click and left with a left click. Please fix this with the next patch!
-
I’ve been there and I have crawled through there too. The thing is, it is not big enough to walk, you’ll need to crawl (or at least squat). Either way, it’s quite cool.
-
I'm trying to get a grip of the offset feature of the TGP. I'm running the instant action mission "GRound attack practice" for the Syria map. I slew the TGP cross hair over a target, go into ATRK (confirmed by display), hit TDC depress, and nothing happens. The little movable cross does not show. If I'm doing the same on point track mode it works like a charm. The cross appears and can be slewed around. Anybody else have this problem?
Also, I'm wondering what's actual point of these functions are in DCS? Why not just use "normal" mode where you can slew around? ATRK mode, where the TGP is not slewable seems uttlerly pointless (unless I'm missing something).
-
Thanks for the replies guys. Will have to work around this until it's solved.
-
I'm learning JDAMS and I have two JDAMS loaded on the same station. There are two slots TOO1 and TOO2. First I use WPDSG to load the coordinates for target one into the TOO1 slot. I then switch to TOO2, change waypoint and press WPDSG again. When I go back to TOO1 the coordinates are erased from that slot. Only TOO2 now has coordinates. Why are there two TOO slots if they can't be programmed for different targets?
-
1 hour ago, Florence201 said:
As long as you’re still heading towards the tgt yes.
Great! Can you please describe how to do it.
-
1
-
-
1 hour ago, Florence201 said:
It will be ground stabillised as long as the tgt remains in the seeker FOV gimbal limits. If you fly through the tgt area, you’ll need to reacquire the tgt
Yes, but if I fire a Maverick, can I get the next one to slew directly to where the HUD TD box is pointing (ie where the previous Maverick was first ground stablized)?
-
So I'm in Visual mode and I have designated a point with the HUD TD box, I press TMS up to ground stabilize. I slew the Maverick onto the target, lock it and fire. How do I get the next Maverick to slew directly to where the HUD TD box is? If I press TMS aft the TD box is boresighted and I have to start over again. If I'm having several targets in the same spot it would be handy to be able to slew consecutive Mavericks to the same spot.
-
8 minutes ago, Taz1004 said:
Actual symbol wise, none. What I use to tell is that the Azimuth will automatically change to A2 and 3 bars in TWS mode.
You are correct. I just tested again. Two TMS presses are indeed required to lock the target. Also, as you point out, after the first press nothing actually show that the target is now a system target, apart from A2 and 3 bars. This means that it is not practical (or even possible?) to mark several system targets when datalink is involved, because you will not be able to tell which are system targets anyway.
It's nice that this behavior is confirmed, although the difference in meaning when it comes to hollow/solid tracks depending on whether datalink is used or not is a bit confusing.
5 minutes ago, Frederf said:I find correlated tank tracks are not locked with first press. It depends on what you mean by "locked" TWS bugged or STT. I'm using MIDs on/off to investigate each step of the way.
From TWS with only tank tracks, TMS forward presses gives:
- Elevate contact to tank track (if required)
- Elevate tank track to system track and snaps cursor to track
- Designate system track as bug
- Enter STT
From previous STT state pressing TMS aft gives:
- Bugged track
- System track (snappable)
- Tank track
- Contacts (all tracks)
- RWS (if no tracks)
The only differences I find between MIDS-on and system track and MIDS-on and tank track is that tank track is not snappable while system track is snappable. When snapped TWS will go into A2 B3 scan regardless of previous AzBar settings. The symbols can't be differentiated visually but they can be told apart. Snappable = system. Not snappable = tank.
Yes, this is correct. Thanks for the clarification. This behavior is not very clear in the manual I think. Or am I not reading it good enough?
Maybe the radar will be discussed more thoroughly when the manual is finished for release state.
-
26 minutes ago, SpaceMonkey037 said:
From what I remember they will be filled it, just like a radar + datalink contact. Not hollow.
When using datalink a hollow symbol will just indicate that the target is only seen through datalink and not with your own radar. A solid symbol indicates that your own radar has also picked up the target. Solid vs hollow seem to have no connection to track vs system file.
-
I will test again when the kids have gone to bed. I'm using the instant action mission "Fighter intercept" to test this btw.
8 minutes ago, Taz1004 said:Not based on the last mission I flew. I had to press TMS twice on red solid datalink targets to lock and launch.
Okay, but how is it shown that the target is made a system target after the first press? For non-datalink correlated targets you get an hollow symbol, but clearly that's not the case for datalink correlated targets. Just wondering what I should look for?
-
1 hour ago, SpaceMonkey037 said:
nono, there is no actual difference in the locking procedure between the two, only UI differences.
The problem is that right now there is actually a difference in the locking procedure. Non-datalink correlated contacts are turned into system tracks with the first press on the TMS. On the second press they are locked.
However, datalink correlated targets are locked directly with the first press on the TMS. This indicates that either the "system track level" is skipped for those contacts, or that all datalink correlated targets are per definition already system targets. In the case of the latter, why are the datalink correlated targets not switchable by TMS right?
1 hour ago, Taz1004 said:The question itself is somewhat confusing but I think you misunderstood the difference between Datalink and your own radar contacts.
Hallow datalink targets are reference only. You can't lock them unless you point your own radar towards it and make it solid.
Hallow datalink target is datalink target your radar isn't seeing.
Solid datalink target is datalink target your radar also sees.
White hallow target is unknown trackfile from your own radar.
White solid target is unknown correlated target from your own radar.
Bottom line is that the targets must be correlated by your own radar in order to lock.
No, I understand all that. See problem description just above this quote.
-
Yes, you're correct. I saw the bug report after a little bit of searching. Thanks.
Cockpit movement too restrictive
in DCS: Mirage F1
Posted
In just started the trial for the Mirage F1. One problem is that there is very little movement possible with TrackIR. There are these invisible walls that some developers set for some reason. In a plane like the Mirage getting in close to the labels and switches is important, because they are not very clear to begin with. How can I get rid of these restrictions? I have already tried modding ViewsF1Cmn.lua under "limits_6DOF". There was a line there with seemingly less restrictions that I tried to use instead of the original one (by putting "--" before the original one), but it didn't work. Any tips?