Captain Orso

It shouldn't. But I've had that happen to be a couple times before. Reinstalling got everything straightened out, so that I could do a clean uninstall.

If you are using the old control panel, Windows 10 takes time to fully populate Uninstall/Change Programs list. It may not have found it yet. Wait a minute or so. I find it both in the control panel as also Settings -> Apps -> Apps and features. Something may have gone wrong during installation. I would try reinstalling to get a clean install, and then check Apps and features. I found out my issue. I'm blind... err well I'm color blind - red-green to be exact. To me the red and grey icons look almost exactly the same. It is VERY difficult for me to see the difference at a glance, at any rate. Is there a way that I can modify the color of the grey icons so that I can more easily recognize them?

Oh, sorry. I misunderstood you. Glad you got it working.

There are Controls -> Modifiers -> Modifiers (hens forth called CMM in this thread), which have default setting like LAlt, LCtrl, RAlt, etc. There are Controls -> Modifiers -> Switches (hens forth called CMS in this thread), which have no default settings. I desperately want to create a CMS using a mechanical On-Off toggle switch. However CMS's only understand On(mom)-Off pushbuttons - "mom" = momentary, ie asserted only while being pressed, exactly like <Shift>. Is there any way to make CMS work with an On-Off toggle switch?

IIRC icons of enemy units used to simply disappear, if they were destroyed. Now I am seeing them remain in place and looking as fresh and alive as the day they left the factory. Is there any way to get dead units to be represented by dead-unit icons? or barring that, that they disappear again?

That is WAD (Works As Designed). It ALWAYS starts hidden, the same as the kneeboard. After using it--generally to record coordinates for putting them into the NAV computer--I always hide it again. Why would I want it up all the time? it would just obstruct my vision.

Okay. Are you a RW Apache pilot then? Anyway, I tried it in MP and I could use a target point as the Direct-To point; in this case an SA-6. So, what ever issue I had previously were apparently user error *sigh*

Works As Designed Correct In SP, correct. I haven't confirmed MP yet. I think ED would have to answer that. The manual says on page 341: and Note, that for Direct-To Navigation, at '4. Cursor select' TGT/THRT (target/threat) is included, but for Current Route it is not, so that confirms, targets are not allowed in Routes.

I just tried it again too, but this time in SP. Txx cannot be added to Route, which is I guess WAD. I also could set SA-11 as Direct To Point, both by entering it in the KU and by selecting it with the pointer, so I'll have to try it again in MP, but SP seems to be okay.

Thanks for replying. I don't recall not being able to put Target Points into a Route, but I guess that might be the cause. To make a Point a Direct To Point, you must first go the the Point page, by pressing B6 (POINT). When on the Point page, SA-11 cannot be selected using the pointer. You can go into coord and select is, but when your return to Point, it us unselected. When on the Point page, you can also just press L4 (or 5?) DIR and then L1 (Point?), but when you enter the CM number (it was C55 in this case), upon pressing [ENTER] the KU display blinked, indicating an invalid entry.

I had an SA-11 as a target, so I added a point with type "11" (without parenthesis), which shows up nicely on the map when allowed under "SHOW". What I could not do was to add the SA-11 Point to the Route, nor to designate it as a Direct To Point. Is the WAD, or is this a bug?

I downloaded the picture. Firstly, the downloaded pic has better resolution, and then I could zoom in on the grid size, and although it does get fuzzier, it also gets bigger. It's is 3km, so the targets are just over 6km distant, and well within range.

I use VR. Apparently everyone knows, one cannot use TheWay with VR in any reasonable manner. There is another app--a plugin actually--which also collects position data from the F10 Map to process it. This is the DCS Scratchpad In-Game Scratchpad Mod Available - Works Great In VR! . Since DCS Scratchpad works entirely from within DCS, it works seamlessly in VR. You might be able to pickup some tips on how to make TheWay work as a plugin as well, so that the UI is available to users in VR as well. Thanks. EDIT When I posted this, I hadn't seen that Scratchpad has already been a theme in this thread. My thoughts on combining the functionality of both mods. The way Scratchpad works, there would never be the need for an external Windows app to be running--as far as I know. As with Scratchpad, the UI would be built into a hooked script to collect the points on the F10 Map. Then the data could be read into the TheWay's app side for processing. What I cannot say is whether the TheWay app can be called through the hooked script, or whether it would have to be running outside DCS as it does now. This idea would simply use Scratchpads method of gathering the F10 Map point instead of the TheWay method. Maybe the author of Scratchpad, rkusa, could shed some light on the posibilty.

You don't make it easy. The screenshot is shrunk that one can almost not read anything, and the TADS page is cutoff at the bottom where the range is shown If I'm reading the TSD on the left correctly, the grid size is 5.0M--five miles per grid. This would make the range at least 10 miles, which is outside the Hellfire's range. From my experience, if the range is too long by a lot, George will say so, but I've had the same situation, where I though I was in range and George said "engaging" every time I hit [Consent], but refused to fire until I got closer, but never said that I wasn't in range. It was VERY frustrating, because the target was in an open field with nothing to interfere with the view and I was going crazy. Unfortunately, by the time I slid into range and George finally got the shot off, the target had fired a wire guided missile, and guess which one hit first...

Unless you have FFB, it is ultimately important to go into Options, Special, AH-64, and set joystick and pedals to spring return - this VERY IMPORTANT! Also, watch this video. It demonstrates force trim very well:

I noticed something different. 1. On the MPCD, on the WPN page, if the manual range is not boxed, you are not in manual range. Observer the IHADSS to the left of the box to discover the actual mode. If it says "An.n", you are in Auto-Range mode. Select Gun. Select Auto-Range mode. You will see that you are in Auto-Range mode in the IHADSS. Select Rockets. You will see that you are no longer in Auto-Range mode (probably in manual - on the WPN page 1500 is boxed. Select Gun. You will see that you are in Auto-Range mode in the IHADSS, again, because the Gun itself is set to use Auto-Range mode, not the Apache.

Okay, thanks for the clarification. It seems that auto-range-mode is on a per/weapon basis. If you have one weapon selected, set auto-range, and then select a different weapon, mode is not auto-range. Switch back the the previous weapon and it's auto-range again.

I'm sorry for being so dumb, but what does that mean, ".. pressed enter on your IHADSS .."?

96

Excellent! So, when does 2.0 come out? Two weeks?

Do I understand correctly, in 2.0 all the data will be recorded and when I quit the server it will all be present; only Tacview will only play it all at least 10 minutes after the end of recording. That would be outstanding!

I just read in the entire AH-64 Quick Start Manual (361 pages), without issue.

In MP, Tacview's writing of its file can be delayed by the server (options.lua: tacviewPlaybackDelay & tacviewProfilingPeriod), which prevents actual telemetry data from being used for cheating. However, if the delay is 10 minutes, it also forces players to sit around the server for 10 minutes to wait for the last 10 minutes of data to be purged into the output file, which is a total waste of time, and prevents players from going to another sever, and also blocks a slot, preventing other players from joining the serve. Whatever entity is writing the actual file is also monitoring being logged into the server, because on exiting the server, the file is closed out. Suggestion: Add a parameter to allow or disallow the server to purge buffered telemetry data out to the Tacview file on player exit. This would still give the server owner the control over when telemetry data is written, but also allow the server owner to decide to write the telemetry data to the player's Tacview file on his exiting the server, without uselessly waiting 10 minutes. What do you think?

How many do you want to add? I don't think there is a limit; maybe if you are talking about hundreds, or thousands, or more.