Raptor9
-
Posts
2161 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Forums
Events
Posts posted by Raptor9
-
-
20 minutes ago, GrEaSeLiTeNiN said:
My question though is this. As CP/G with HDU as Sight and TADS as ACQ, why can't I slew the TADS? I can see the RHG slew button moving but the TADS isn't slewing.
Because your selected sight is your HMD, but the RHG slew controller can't slew your own head.
-
1
-
-
@Caldera, what you are seeing in the manual is a graphical representation of symbology to illustrate that the Rocket Steering Cursor represents the allowable ballistic solution, but simply as an illustration of the Rocket Steering Cursor symbol, not taking into account all the various ballistics that affect rocket flight from a firing helicopter; further, in the graphic you posted you will notice that the aircraft is in a zero-airspeed hover, not forward flight. The reason that the rockets don't fly straight toward the head tracker when in forward flight is because they will weathervane into the slipstream. If you are flying in a crab, the rockets will curve in the direction of travel, and this ballistic effect is calculated by the aircraft computers, which is why the Rocket Steering Cursor doesn't always align with the Head Tracker, even though the rocket pods are fixed in azimuth.
This is not an Apache-specific behavior. The rocket aiming reticles in the Ka-50 and Mi-24 will also travel left and right to predict where the rockets will impact when the nose is crabbing left or right in forward flight.
-
1
-
-
-
53 minutes ago, Belphe said:
I'm having the same issue but with no external tank involvement at all. Simply, if I don't click the C AUX on the fuel page very early in the cold start process it is later impossible to activate it. Has this been ID'ed as a bug or it works as intended?
See bullet 1) in my response at the beginning of the thread.
-
1
-
-
On 4/12/2022 at 5:02 AM, bradmick said:
The tail numbers are 5 digits for our birds in the format: 00-0000.
But that's six numbers....
-
Books
in DCS: AH-64D
Those books are entertaining if not 100% accurate. The experiences while deployed to the Helmand province are a good read, however there is some embellishment and inaccurate info when it comes to descriptions about the Apache itself. I know there are differences in the UK Apache versus the American AH-64D, but some of the statements in that book regarding common systems are misleading at best and outright false at worst.
Not to trash-talk Ed Macy, that's not my intention; he sounds like a great warfighter and they are indeed good reads. Just take some of the Apache-related info with a grain of salt.
I will warn you about a book called Pale Horse by Jimmy Blackmon. It has an Apache helicopter on the cover but that is about as much interesting info you will get about it, mostly false advertising. It's written from the perspective of the unit commander (the author), and from what I heard from pilots that served under him while on that deployment, he spent most of his time during that deployment writing that book instead of actually leading the unit.
-
1
-
1
-
-
3 hours ago, Captain Orso said:
Management Summery
I was on a European 4YA Caucuses PVE server and tried to replenish flares and chaff at a FARP. After rearming, I never had what I set I wanted 90 chaff, but it would only give 30.
I don't recall everything I tried, but it was a mess, and I never got what I asked for.
Regardless of the sliders, you can only load 30 chaff and 60 flares as the respective maximums. These are preset configurations of the dispensers and cannot be changed.
-
1
-
-
A fairly eristic response to me giving my own opinion on the matter. You're certainly entitled to your own, but you don't need to falsely paraphrase my viewpoint in order to counter with your own.
-
2 hours ago, rcjonessnp175 said:
Maybe it will give people a little more respect and awareness how much war sucks......
I respectfully doubt that. First person shooter games number in the hundreds, a good number of which have substantial gore as an aspect of the gameplay. I don't intend to speak for everyone, but I don't think people have any more respect or awareness of what effect conflicts have on the world because of video games. If anything, it has had the opposing effect. This thread's request is (in my opinion) evidence of it.
I don't mean any disrespect to the OP or anyone advocating for this feature, but the very nature of wishing to experience such realism in a product meant for entertainment implies the opposite effect. This is just my assessment from where I see things, I'm not saying my viewpoint is right and other viewpoints are wrong, it's just a viewpoint.
-
2
-
1
-
-
4 hours ago, Whisper said:
AFAIK rockets are not intended to be fired from a hovering position
Indeed they were, as a method of "Aerial Artillery".
-
1
-
1
-
-
47 minutes ago, Scaley said:
is outside the timeframe of the version modelled.
It's not, it just wasn't a standard piece of equipment since it was relatively new.
-
1
-
-
7 minutes ago, SkateZilla said:
most of the users requesting ASPI Removal Option are so they can do Apaches from countries.
I understand that, but that doesn't make the option any less relevant nor does it make it less accurate for the AH-64D version that ED is simulating.
Further, the tag on this thread "not realistic for us late block ii" isn't accurate, since quite a few (if not the majority) of AH-64D Lot 9.1 aircraft in the mid-to-late 2000's still had legacy exhaust. Not saying it was deliberately misleading or anything, but probably stems from a misunderstanding of the timeline of the AH-64D in US Army service and associated configurations.
-
2
-
-
Yes, if you change the selected CHART map scale for a set TSD scale, it should remember it when returning. It shouldn't need to be re-selected each time. Probably WIP my guess.
-
1
-
-
2 hours ago, ApacheLongbow said:
I understand your assumption, but you failed to understand that in this case, we're not talking about 2 humans responding to their own inputs, but one human and a control interface that is made to artificially "emulate" an AI entity.
I haven't failed to understand a thing. The real AH-64 aircrew requires a lot of constant communication to work together, and there is no instantaneous reactions. Granted, no AI interface will ever be able to respond to the near infinite things a human could say, but if you want to fly and target at the same time, simply take the flight controls from George.
And it isn't my assumption either, some of the delays are built in by design based on how long it takes to actually perform such tasks by a human. For example, if you instruct George to slave his TADS to your helmet LOS reticle, it takes a second or two for him to slave the sight to the location, which is true to real life. If I am in the CPG seat and need to tell my pilot to fly a certain way or direction it can take several seconds to verbalize what I need and for him to initiate such an action.
-
1
-
-
5 hours ago, key_stroked said:
The OP's screenshot shows the gun is in FXD mode, which means it's not following the TADS crosshair but rather the fixed crosshair that appears in the HUD. Wouldn't that be more crucial than being outside of 2900 meters?
Very astute observation, this is indeed the likely cause.
-
The delay simulates human reaction time from having to state the instructions verbally over the ICS. Real aircrews don't operate telepathically.
-
1
-
-
The entire Cold Start is still WIP. Things like the Doppler and Radar Altimeter are supposed to be switched on automatically on APU power up. This is why they are not mentioned in the manual's start-up checklist.
Also, the manual itself is also WIP, and will probably be updated over time along with the module. This process is not new, the F16 and F18 was the same.
-
53 minutes ago, SkateZilla said:
If we are to go on tangents too, then it will be a never ending feature creep problem, as then users will want AMASE Pods, even though the components of the AMASE are already integrated onto the Block we have.
That wouldn't hold true either, since the AMASE pods were only on RNLAF Apaches, not US Apaches. The US Apache version being simulated between 2005-2010 had both exhaust types, but did not have any AMASE pods.
-
In my opinion, such a feature would be in poor taste and should not be present.
-
9
-
2
-
-
37 minutes ago, SkateZilla said:
ASPI is part of the ASE Package, so technically you want a Pre ASE Apache, in which case, You'd lose the Countermeasure dispensers, the sensors, and the cockpit systems to go with them.
ASE Initial Fielding was 2001-2003/04, there were Apache's in OIF and OEF with the ASE Kit's installed.
As for Pre-ASE Apaches, there is an AI Pre-ASE Apache in DCS Already.These statements are not accurate. The ASE "package" is not a holistic kit that is installed altogether or not at all, but a collection of components that can be installed, upgraded, or removed as needed, much like upgrading sensors, radios, etc. The up-turned exhaust is just one modification among a large number of items on the AH-64 that has seen change as the aircraft continued to evolve over its service life. The statement of ASE initial fielding occurring in 2001-2003/2004 like you stated is based on a false premise, and is not true at all; AH-64A's in the 1980's and 1990's had ASE equipment such as RWR, chaff dispensers, etc.
The first ASPI exhausts did not appear until post-2005 at the earliest, and even then were initially very limited in number. Even by 2010 (the tail end of the 2005-2010 window that ED is modeling with the DCS AH-64D), there were still quite a number of US Apaches that still had the legacy exhaust. Removing the ASPI exhaust has zero relevance to the inclusion of any of the other ASE equipment being modelled in the DCS AH-64D as all of it was present on non-ASPI Apaches in the 2005-2010 timeframe.
Personally, I would be for the exhaust version option down the road if resources/time permitted, but understandably this is a low priority.
-
3
-
-
Technically, the VID page should remain in the last state it was left, unless NO VIDEO was selected in which case the default underlay would display when returning to the VID page. The current behavior is inaccurate, and will hopefully be updated sometime in the future.
So in your case, when you press the VID button on the MPD, it should return you to the full screen TADS video like in your first image, but currently the behavior isn't reflecting that.
-
2
-
1
-
-
@osram, it's not "my reasoning", that's how it is. The grid on the TSD screen has nothing to do with coordinates, it is only for distance measuring.
As I said in my first reply, if you have a map underlay that displays a grid on it, you can use that for determining coordinates since that is actually part of that map. The TSD grid itself is only for distance measurement in relation to the ownship.
I understand what you are trying to accomplish, but the TSD grid is not used for that, nor is it designed in that manner. If you wish to find a grid on the TSD map without manually typing it in as a point, you can use the CURSOR INFO show option.
-
1
-
-
It says UTM LAT/LONG, which means it will accept either. Although technically UTM isn't MGRS.
11ABB22223333 is the required KU format for MGRS.
N112233E0112233 is required KU format for Lat/Long (in the format entered, this would be the actual coordinates N 11* 22.33' E 011* 22.33' is the coordinates entered)
-
1
-
1
-
-
The TSD grid is simply for distance measuring, which is why the little ballon at the top right corner shows the width of it based on the scale/zoom of the TSD.
If you are showing a Chart underlay with the MGRS grid on that map, you can use that as you move the cursor around for the purposes of looking at grid locations.
TSD: wrong point type assignment by identifier (possible bug)
in Bugs and Problems
Posted
That is inaccurate behavior in the current build. It should not automatically assign the point type based on the IDENT code entered. For example, if you select WP as the point type and enter an IDENT code of a point that is a HZ, CM, or TG, the KU is supposed to flash at you indicating an invalid entry.
Yes, currently it will change the point type for you, but it should not, and I would expect this to be fixed in the future.