-
Posts
1192 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by FalcoGer
-
CA is rather lacking. It would be nice to be able to call for fire without extra people. If you have extra people you can still do it via voice. But the AI won't listen to you.
-
Missiles communicate their status to the aircraft. I assume that when those no longer report back to the aircraft, the pylon is considered failed. This should be indicated with a yellow box around the pylon on the weapons screen with the message "FAIL" in yellow beneath it, inverse video (black on yellow) if the weapon is selected. Missiles should get a code that identify a particular missile failure. (Failed bit, misfired, launcher failed, etc)
-
now that i read it, it seems rather vague and limited. "Data Link System to share and assign targets between flight members" I'd rather have all the data link features. For example FARM reports will not be in the final release if you take this at face value but it would be helpful.
-
they should've done it right the first time around and attached the rings to threat point idents, not what the mission tells the apache the range on a particular point should be.
-
it appears that threat rings are only displayed for threats that are added via the pre planned threat thing, but not for own threat points. Also, when the threat file is full and a new threat is created with the TADS Store function, a target point is overridden. if that point has a threat ring, it will persist for the new point, even though the new point isn't an air defense threat. Threat rings ranges should be derrived from the ident only, not what the mission is telling the apache what the range of the threat on the map is. The only thing the mission should tell the apache is what kind of ident to use for the threat and where it is.
-
maybe i did something wrong. would you care to check?
-
I did. I see the threat markers, but no rings. Bug report with track file here:
-
I popped down an SA5, SA8 and SA15 threat point, turned the rings on for Threat and ACQ and I get no rings.
-
I usually run around 30FPS, which is good enough for me. When I look into a forest horizontally with the TV camera, the frames drop to around 10 FPS. If I slow the TADS off the forest the framerate returns to normal. When using FLIR the framerate is also fine. Perhaps trees are not properly culled on the day tv camera? AMD Ryzen 5 1600 Six-Core Processor AMD Radeon (TM) R9 380 Series 32GB DDR4 2666MHz Dual Channel NVMe Samsung SSD 970 SCSI Disk Device Windows 10 Pro, x64 TV_Forest_Framedrops.trk
-
correct as is PAN mode RTE buttons don't work as intended
FalcoGer posted a topic in Bugs and Problems
In TSD -> PAN there are 4 buttons related to panning along a route. L2 and L5 pan to a point. L3 and L4 are supposed to pan along the route smoothly, however right now they mirror the behavior of L2 and L5. PAN_RTE_wrong.trk -
On the digital map, one may add shading for various points to indicate visibility, such as targets/threats. This will shade in the digital map in different colors to indicate the visibility from those points. This would be really helpful to plan routes or battle positions. Right now the buttons are present, but don't do anything. Same with threat rings. They do not appear.
-
On the TSD main page, several buttons are missing as evidenced by [Rule 1.16]. RPT (Report page) to send messages and request messages REC (Receive) to view received messages JAM to switch jammer between standby and oper (only displayed when jammer is on) I'm aware those features are not yet implemented, however other not yet implemented features such as FARM reports in the COORD page are barred out instead of missing.
-
i made the same request yesterday
-
How does it work then? The way I understood it is that some observer (perhaps an oh-58) is sending a air fire request message to the apache. the apache then can accept the mission, gets a target. Messages are sent back and forth regarding the different stages of engagement as outlined in [Rule 1.16] Where did I go wrong? Who can receive which messages with what DL protocol is outlined in [Rule 1.16] In this case Tactical Internet and Fire Support networks are available on the FM radios, both of which may be used for the airfire mission messages. The apache may only receive requests and the assosiated messages from the observer and may only send messages meant for the observer, meaning it's confined to the shooter role.
-
George just lets his crosshair wander around when he looses sight of the target. A real human would anticipate target movements behind obstacles or look to where he anticipates the target to reappear. Then once he reacquires, he snaps back to the target. It's a mess and if it's intended, it's not right.
-
In the A10C, a mission from the JTAC is sent over the datalink system to be indicated with a red triangle on the TAD. A similar system is in place for the Apache. The Apache is able to be the recipient of an airfire mission for remote laser guided missile shots. I would like this system be used for JTACs capable of tactical internet datalink or fire support net datalink.
-
Don't forget to include action items for failures please. I want to be told what to do when a failure message pops up on the engine format.
-
rivers would be nice, too. I mean they already know where the roads are, otherwise vehicles wouldn't be able to path on them. Forests are colored in green on the F10 map, I imagine they used some sort of tool to generate those polygons that are different colored. They should be able to use the same tool to generate the maps. I mean it is a digital map, it's fine if it's generated from the same digital data that was used to generate the F10 map in the first place.
-
The apache has a comprehensive communications suite. MFD formats allow the selection of targets, both from points as well as from the FCR to be sent to artillery for a fire mission. I would like this to be tied in with DCS in such a way that artillery fire missions are generated for the selected artillery unit on the selected fire support element (FSE). Artillery should be selectable as the FSE if it has that option set in the mission editor, perhaps as a route special option to be available for unit/group/coalition datalink tasking. In practice this is hardly used, but in DCS it could tie in nicely.
-
In DIG map mode, contour lines may be displayed. Currently this does not work. I wish it to work.
-
Apache Bros: https://discord.gg/Je6MRzrg Wingman Finder: https://discord.gg/GgpwybsE DCS Multi-crew Finder: https://discord.gg/TWnDCta2
-
Single/Burst scan switch are momentary position switches. if you press them once they do the scan if you press them again they stop the scan. pressing them also does some other logic, such as clearing the tracks.
-
The fuel tanks are evenily filled when requesting a refuel, but the aux fuel tank should only be filled when the main tanks are full. To reproduce: 1. Defuel to 50% 2. Refuel to 60% Aux fuel tank now contains fuel, but all it's fuel fits into the main tanks. Related: When putting a non maximum fuel load into the mission editor, the tanks are equally drained, but the aux tank should be empty first. To reproduce: 1. Put an apache with 50% in the mission editor 2. Check fuel levels Aux fuel tank contains fuel. Also related: Fuel starts with imbalance when aircraft not 100% full in ME. Track attached. In the track file the aircraft starts with 60% fuel. You can see the aircraft pumping fuel for 13 minutes from the aft tank to the forward tank because it starts imbalanced. You can also see the aux tank having fuel, despite all it's fuel can fit into the other tanks. You can see that while refueling, the ground crew pumps fuel into the IAFS as well as the other tanks despite the other tanks being able to hold the fuel they pump into the aux tank. Correct behavior: Fill the aircraft so it's trimmed from mission start or from refueling. Fill aux tank only when other tanks are full. low_fuel_start_and_refuel_to_IAFS.trk
-
I think you're confusing something. The abbreviations list is for the ident on the TSD points. We're talking about the george target selection.