Rangoon

Good point! sorry I forgot to mention that part.

I think I have this sorted out. I created a delay in the Mi-24's startup. He appears at the normal mission start time but is not active, then after five minutes begins his startup procedure. I also added a five-minute delay to all of the timed triggers (the first few audio triggers). In case this helps anyone else: 1) Unit RU Mi-24 (105) Triggered Actions: added 1. Perform Command > Start > "Lead Startup" 2) Set Rules for Triggers: inserted (after first trigger): 1 ONCE (Lead Delay, NO EVENT) > TIME MORE (300) > AI TASK PUSH (RU-Mi24 (105)/1. Start "Lead Startup") 3) Added 300 seconds to TIME MORE condition of the next four triggers

I am starting the Ka-50 "Deployment" campaign, as updated by MadDog. I have practiced the startup dozens of times, and have a pretty decent flow, good checklist(s) etc., although the only way to get airborne alongside the Mi-24 I'm supposed to follow is to rush the startup and do things vastly out of proper sequence. Those poor batteries are being asked to power just about everything in the ship before the APU is even running, let alone the generators. And even when I do this rushed startup, I'm still hard pressed to get airborne in time. The vibe of this mission seems more relaxed, so I would like to edit the mission to allow more time. I have searched through the mission editor sections of the manual, but cannot seem to find what I'm looking for. I tried adjusting the mission start time. I tried just adjusting aircrafts 1st waypoint (SP) to have an earlier "arrival" time. I just can't seem to get this working so that I'm sitting in the ship maybe 10 minutes ahead of the mission start time. Is there an easy way to do this?

You were right; I reinstalled that module and it's working now.

Just loaded up the F-86 for the first time, in 1.5, and I have no cockpit. I can look around and see my fuselage, wings, etc., but I have no cockpit. I have tried two different quick missions, tried all the F views, back to F1, and still nothing. I have also tried moving the view camera around (RCTL+RSHF+numpad) - which functions, but doesn't fix the problem. Any other ideas?

Has anyone determined a solution for this? I am getting same symptoms. In Windows 10 "Game Controllers" I see both the "Thrustmaster Combined" controller and each individual controller ("F16 MFD 1" "F16 MFD 2" "Throttle - HOTAS Warthog" "Joystick - HOTAS Warthog"). This is after running a profile in the script editor. Prior to running the script I see only the discrete controllers. Of course in DCS, then, I see the same situation.

I'm using a Warthog stick and throttle, Cougar MFDs. Also Crosswind pedals, CH throttle quadrant/MFP. Windows 10 Pro, version 10.0.15063. I deleted (renamed) Device Management App executable I believe (per that thread over at the ED forums stating it was no longer necessary and just caused issues with Windows 10), so that doesn't run anymore. I was having issues with TARGET freezing/crashing. EDIT: I just ran the same scenario in the Ka-50 from a fresh restart. By the time I lifted off, the gear switch had broken again, though everything else was working fine at that moment. The shift key is working with other commands, and the China Hat is working fine to control RPM Norm/Low, however S3+China Hat does not affect the landing gear. It does however change the profile gear state (so TARGET is seeing it, but not DCS?). I changed the gear state back to GSD (1st MFD right-hand light lit) and tried again...nothing. China Hat still works, S3 still works for shift (TrackIR center, etc), but landing gear does not raise (S3 + China Hat aft). This is one example of how the same sorts of things seem to break in consistent ways. I'll restart Windows again, and this time it'll probably work fine. Just wanted to update. EDIT 2: in my "Services" list, I have: - TmWinService (Thrustmaster FAST service) - tmGAIinstall (Thrustamaster General Accessories Service) nothing else listed under Thrustmaster. EDIT 3: For reference, here is the thread.

Does anyone else have to restart their computer frequently with TARGET and/or this profile to keep it working? If I don't, I routinely get very unpredictable behavior with the Ka-50 profile such as: - trim no longer functions because it thinks the shift button is still pressed even though TrackIR center still works just fine - engine control switches behave randomly (after pressing forward to open the left side red fuel cutoff lever, it springs back to center and closes the right side fuel cutoff switch) - landing gear doesn't work regardless of which "landing gear state" the profile is in Some things are just synchronization, but I feel confident I know how to reset the profile and the hardware for a cold start after flying a mission regardless of the end state (MFD lights are as they should be and switches are in the natural cold-start positions). But what's not synchronization is a bit mysterious. Restarting Windows seems to fix it. Some things are fixed by closing DCS and stopping/starting the profile, but other things require a Windows restart. Is this common with TARGET? The recent Windows update? I have seen other posts here suggesting the Windows caused plenty of trouble, but I don't really know how things were behaving before that update.

I wonder if I've screwed something up with my profile...is there an explanation for this or has anyone seen this with the Ka-50? -- 1) I can change the gear up/down state in the profile, but the gear in the aircraft aren't affected 2) when I use the trim switch (H4 press), the trim works but I always see a message in the script window that seems unrelated: "S2 Set to CommState...Done!" 3) when I press a snap view, such as "ARIS" (S3+H2U long) or "Right Console" (S3+H2R long), nothing happens except I see a message in the script window: "Map Cougar Left MFD (DX31)...Done! / Map Cougar Right MFD (DX32)...Done!" Something doesn't seem right here, but I can't sort out what is going on.

Going through the advanced configuration PDF, I found the VAC function to send PTT to voice control software. Is this not working in 1.68 or am I not doing this right? I turned that on in the main script (line 439). It defaults to middle mouse. I tried shifting (S3) the PTT switch (in Huey, MSU, MSD, or MS press). I don't get a middle mouse click. I tried changing the macro in the ttm file to a few different things, but I can't seem to get a proper result. Is there another switch I'm missing? I am pressing S3 and MSD (tried the others as well), but all I get is the standard PTT DX21 press and the right MFD left LED illuminates. Is this the correct way to go about this?

Huey searchlight: Am I understanding correctly that when the searchlight (not landing light) is on (Boat Switch forward), then H1 should aim the light, right? I can see in the keybinds that one of the three modifiers (forget which one) plus POV 1 does indeed aim the searchlight, but I haven't gotten it to work yet. It's as if turning on the searchlight isn't communicating its state and activating the modifier. I get the basic, unmodified H1 behavior. Any ideas? EDIT: looking through the script code, I found that the searchlight is controlled with the Coolie Switch, not H1. I just can't find that in the documentation anywhere, and assumed POV 1 was H1, and/or that "Station/Sling" for some reason might have jived with searchlight control (not the same thing, obviously). Home Fries, you mentioned that the micro stick doesn't work well for controlling the searchlight, however I've not had much trouble with it controlling the Shkval as long as I have my axis tuning in DCS set appropriately. When I tried to assign the micro stick to searchlight control in DCS, the axis just isn't available (doesn't register). Is this because you have that axis disabled in the controller? Or is it not a valid axis for that function in DCS? In my use, I've also seen that the gunner doors seem to be reversed. Pressing MS right opens the left door, pressing MS left opens the right door. Another kind of buggy thing I've seen in both the Ka-50 and UH-1H is that when I pause TrackIR and then use H1 to pan the view, it sometimes unpauses TrackIR. I then end up cycling TrackIR pause/unpause to correct it, and then I can re-pause TrackIR and get the H1 pan back (until/unless it glitches again). Not sure if this is buggy from TARGET or something in the script. Thanks again!!

Hi Home Fries - getting into the Huey now. Really like how you handled the throttle control. And in general, again, absolutely love the profile and appreciate the work you put into this. I think there might be a bug/inconsistency in the master weapon switch and the master caution switch. In the documentation, it says the far bottom (aft) left switch on the throttle base is weapon select, which it is, and the one to the right of that is the master arm switch, which it is (between off and arm, skipping "safe"). It says H2 up and down are also weapon select switch, which they are. However, it says with shift those two should be master caution switch up and down (which I believe should be the "reset" and "test" options on that switch) but they control the master arm switch (so that you can hit all three positions instead of skipping "safe", which is nice but I'm not sure it's intended or if that is even useful in practice). It also says the LDGH button should be master caution, but I'm not yet sure it does anything at all, FWIW. Just throwing that out there in case you're delving into details like this for 1.69. Thanks again!

I have a few questions about PTT Common. Browsing through a few profiles, for example, A-10C and Ka-50, I see PTT common in more than one place. A-10C has it as Mic press as well as Mic up (Warthog). Ka-50 has it as S2 and Mic switch press. 1) These are redundant, then, right? 2) If I want to add another "comm" function, precisely a Voice Attack "listen to me" button, would it make sense to use one of these redundant PTT Common slots? Or will that get me into trouble with other profiles down the road? Is that a consistent situation for there to be more than one PTT Common? 3) would this simply involve making a single edit to the tmc? And then whenever there are updates, just remember to make that same edit again? Or am I thinking about this wrong? I want to have Voice Attack control over my AI wingmen, ATC, etc but not lose the ability to use TeamSpeak etc for multiplayer. If I only played SP, then I could obviously just assign DX21 to Voice Attack and be done with it.

Home Fries - I can't thank you enough for these profiles. I installed 1.68 and have everything up and running for the Ka-50. Fantastic work! I have a question (possibly a bug?) about the Ka-50 fuel shutoff valve switches. I think I understand the basic switch states and how to adjust if things aren't synchronized (such as the Automatic Tracking switch, for example - hold down S3 and switch to match, then release for actual use), but it seems the Left and Right fuel shutoff switches are backwards. The APU switch is correct, but the main engines are opposite. The documentation shows it the way I think it should be: aft position is fuel off, sim switch on wall panel down; middle position is fuel on, sim switch up; fore position toggles large fuel cut-off lever on left side). Is this something I'm misinterpreting? Or misunderstanding initial states for a cold/dark aircraft? Thanks! EDIT: I wonder if the logic is that the "shutoff" valve is "on" when it's in the "cutoff" position (down on the aircraft wall switch but middle on the Warthog Throttle) and the valve is "off" when in the aircraft switch up position... Is that it?

Regarding the hardware deadzone, I am having two issues with it: 1) It resets to "enabled" every time I click on the button to "Control Hardware Deadzone" in the GUI - this makes me suspicious that it's not saving the setting when I disable it (remove the dot in the circle) 2) I can't see any difference in the Device Analyzer with it enabled or disabled. I am running a profile with no deadzone, but whether the hardware deadzone is on or off, the response is the same. Does this setting control whether the profile's deadzone is recognized or not? Or is this a separate deadzone that can be enforced regardless of the profile and of course the particular sim you're running?

Thanks!

Looks like the download link is down until the 1st. Would anyone be so kind as to share the 1.68 file with me directly (dropbox etc.)? I have today and tomorrow available, then out of town next week at the start of the new month. Would appreciate being able to put some time into setting this up today! :)

Got it, thanks.

I'm a little confused on what the newsletter meant by "60% savings using bonus points". Does that mean I earn 60% more bonus points than usual? Or that using bonus points on a product in the list have 60% more value? Or something else?

Yes, this particular flight took place in the early morning. That's probably it. Thanks. And let's hope, if this isn't realistic, it does get addressed. And I'm in the camp that would love an actual, fully fledged, battle-ready production Ka-50 DCS model rather than just the prototype. Then we'd have night optics and such, from the sounds of it.

I'm wondering if I'm employing the systems incorrectly, but I seem to have bad luck locking up targets with the Shkval if I'm moving at all. I've got a nice profile on a tank, tried all the way from 8km down to 2km and still never got a track. My ground speed was only around 50kph. I tried varying the gate size and kept pressing lock every 10 seconds or so. I also tried with ground moving target selected and not selected. Master Arm was on, Laster was on Standby. Should I have been getting a lock? A few specific questions: Does ground moving target mode affect the situation if the target is stationary and the Black Shark is moving? Or only if the target is moving? Does the contrast/brightness affect the actual camera and how well it "sees" targets? Or only the display for the pilot's benefit? I assume the latter.

Since this is going into a common folder, will these pages show up in all aircraft kneeboards? Or only the Ka-50?

Gotcha. So as of now, it shouldn't make a difference between settings. Hopefully in time...

Sign me up. That is some serious Mad Max stuff right there.

Thanks. I've been flying around at 1000% all this time! :) Gonna change that right now.