ratkandy

As a separate window outside of DCS' main one?

I need it to pop out to a separate window and be resizeable. I haven't found anybody who knows if this is possible yet.

Can the NS430 pop out to a different window like the one in X-plane?

I tried this mission tonight, and visibility is about 200m through the fog. There's some enemy AA hidden between the first waypoint and the fence, and they had no trouble seeing me or my wingman. Of course I had no chance of spotting them or any other target. Pretty sure the KA-50 wouldn't leave the ground in these conditions in real life. This mission was flyable a couple years ago when the weather was rendered differently, as I recall. Is this a bug, or am I missing something?

Ah, I think this has been regarded as a bug in that mission for a long time. I never knew you could get around it by changing loadout. What change did you make?

Suggested values in the Axis Tune menu: Deadzone 30; Saturation Y 15. (Saturation X leave at 100, Curvature 0.) Do that for both the horizontal and vertical axes. I haven't tested this in the shark, but it's the default way a warthog slew control is set up in the A-10C.

We probably all know one of the annoying things about DCS is the inconsistent way control functions are named and organized. For instance, one aircraft has the landing gear listed as "Gear lever", another as "Landing Gear", another as "Raise/lower landing gear". I know we're probably not going to a perfect world where those inconsistencies are fixed anytime soon, so I suggest a quick new feature to help work around it, a search box at the top of the control editor.

I just checked the options for this, and it looks like rudder trimmer is unchecked by default. But the way this sim has traditionally handled, and the more realistic way, is with rudder trim? Seems like it should be checked by default. ED is forcing a change on some unsuspecting users here.

I can assign it to an axis in-game when linked (it's called JOY_SLIDER1 I believe) but as soon as I unlink, it goes dead. You can see this happen in the "axis tune" menu. Do you/your buddy have the same problem with the right throttle going dead in the test software?

Thanks for the replies, but I think only FraserNZL understands the problem. Throttle2 produces no signal whatsoever, even in the test software that comes with the driver. It only "works" when linked. (I think just means the driver mirrors Throttle1's output onto it--all in software.) I'm starting to think it's a hardware problem, like the potentiometer just died. Does that ever happen? I'm also failing at programming the ministick or scroll wheel to do anything so far.

I bought a used X-65f on ebay last week. Every feature on it works except the dual throttle, and I'm trying to figure out if it's a solvable issue. When the throttles aren't linked together, the right one doesn't register any motion. Neither DCS, nor X-plane, nor the driver software detects it. When linked together, Throttle2 suddenly starts producing output identical to Throttle1. I'm using the latest beta drivers 7.0.10.6. I've tried a couple of the registry hacks out there, they only succeed in swapping the label with some other axis, the behavior doesn't change. Has anyone seen a problem like this with the X-65f before?

No disrespect intended. I assure you I looked at the screenshots closely. If you want your work appreciated, I suggest that you describe what you did. Is this a whole new theater? Is it a re-texturing of the Caucasus? I have no idea. Maybe you assume that I've heard of this mod project before now?

Can you explain what this mod actually is or does? Is it the Caucasus with some palm trees, or what?

I tried renaming my "DCS World\bin" directory and running repair. The directory and files were replaced, but no improvement. I still get the following event data when trying to load a Huey mission: dcs.exe 1.2.15.37241 54eef04c WorldGeneral.dll 1.2.15.37241 54ee2dcb c0000005 0000000000083b40 ddc 01d0537c6ba7ac92 C:\Program Files\DCS World\bin\dcs.exe C:\Program Files\DCS World\bin\WorldGeneral.dll b5376eef-bf6f-11e4-9c17-448a5bcffdf5

I'm unable to fly the Huey, Ka-50, or A-10C since the update. As the mission loads, it crashes out with a "DCS has stopped working" dialog box. I was able to load missions successfully for the Su-25T, TF-51, and F-15C. I've tried running the repair tool already. From the Windows event data: dcs.exe 1.2.15.37241 54eef04c CockpitKa50.dll 1.2.12.0 547f06e3 c0000005 000000000004ccec 4bc4 01d05312a9b34de1 C:\Program Files\DCS World\bin\dcs.exe C:\Program Files\DCS World\mods\aircraft\Ka-50\bin\CockpitKa50.dll f1a771c7-bf05-11e4-9c17-448a5bcffdf5 dcs.exe 1.2.15.37241 54eef04c Cockpit_A10Common.dll 1.2.12.0 547f05a7 c0000005 0000000000013efa 4028 01d0531002aa2482 C:\Program Files\DCS World\bin\dcs.exe C:\Program Files\DCS World\mods\aircraft\A-10C\bin\Cockpit_A10Common.dll 4b992ece-bf03-11e4-9c17-448a5bcffdf5 dcs.exe 1.2.15.37241 54eef04c WorldGeneral.dll 1.2.15.37241 54ee2dcb c0000005 0000000000083b40 44f0 01d0530f4dfbbbce C:\Program Files\DCS World\bin\dcs.exe C:\Program Files\DCS World\bin\WorldGeneral.dll 967c1683-bf02-11e4-9c17-448a5bcffdf5 Edit: I fixed this by uninstalling DCS World, re-downloading and reinstalling everything. Sigh.