Captain Orso

It doesn't increase hardware performance. Don't be ridiculous. It's interesting that you equate waiting for ED to fix a bug to waiting on Santa Clause. Santa Claus brings you what he wants to, and you get to fill out a wish-list too. Sometimes you get neat toys like the new Forrestal carrier, and sometimes you can wait for ages on a fix, or until you're in your grave. Autohotkey is another software to manage. You may think anyone can use it blind, but I've had experience with it. As I recall, I tried to use it to fix some issues with VAC and Viacom, and I discovered that autohotkey doesn't understand non-US keyboards, so it turned one mess into an even bigger mess, which in the end I couldn't solve. I appreciate your trying to help, but yours is not the only perspective.

I was hoping it was something that slipped in with the last update and the could easily be fixed. It makes using coppers on anything smaller than a aircraft carrier practically impossible, unless you use hot start and leave immediately, otherwise the rotor will be pushed into the superstructure.

If you want the closest thing to an actual WWII carrier for practicing on, try the Tarawa. It is almost the same size as an Essex - the island might be a bit more toward the center, but it's just for practice, and of course there are no wires to catch and nothing to catch them with. Just use the brakes liberally when you land. If you nose over, too bad, just grab another plane. I would practice with the Mustang. Without having flown the Corsair, but both the Mustang and Thunderbolt, I expect the Mustang to fly more like the Corsair does, than the Thunderbolt does. The TB is just too... stable to be a good representation of the Corsair, which should be at least as agile as the Mustang.

Has anyone else noticed that (at in SP, or on a local client running as a server) when the Huey is resting on a ship that it is constantly simmying forward a few inches, but over time like about a foot or two per minute at least. Happens apparently with spawned in AI Huey with no orders to startup, as well as client aircraft that someone is simply sitting it. Happens whether the aircraft is dark or has engine in idle. On the destroyers, frigates, and cruisers, with the blade starting out pointing forward, within a minute or so the blade is hitting the superstructure and breaking. I was on a friends server yesterday and he told me he saw it constantly happening, but I was a guest on his server and didn't see that, but I did note that the Huey was constantly wobbling back and forth, both with or without the engine running. Today, I setup a mission on my system and ran it in SP. The mission has at least one each modern US war ship which can start helicopters and the shimmying happened on all of them.

So I should have to install and manage yet another software to fix what ED hasn't managed to do simply and logically? I'd rather not, thank you.

That's true. I think I'd forgotten that you can use the PgUp key to get out of the stop-lock. And yet the way it works now is still unintuitive and confounded, and from what I can tell, doesn't even conform to the actual manual. It's a program. Programs are supposed to help humans achieve goals, not be confusing, and cumbersome. The actual Army manual from 1988 doesn't say anything about advancing the throttle from stop, past idle to full and then back to idle-stop (above the stop). It says to advance the throttle until movement to blocked by the stop (just less than 1/4 turn in the real-world from what I've read form an actual Huey mechanic) and then pull and hold the starter-trigger until N1 (gas producer RPM) reaches 40% (or 40 seconds of operation) then advance the throttle to just past the idle. When N1 is between 68 and 72%, twist the throttle down, pressing against the stop. On release the N1 should rise a tiny amount. This is just a check. BTW anyone know whyt N1 is called N1? Just curious. That's it; now the engine is running. After this you do the runup, which is more involved than I want to go into. So, without a collective throttle that has an actual idle stop button which works exactly like a real Huey, it is not possible to EXACTLY simulate the Huey engine startup, but it would be very simply to emulate it with very little effort: Throttle grips starts at stop position. Make all preparations for startup. Press and hold the start trigger. At N1 40% press the IDLE STOP REL button, which advances the in-cockpit throttle grip to idle. THAT'S IT! The rest is runup. The throttle grip is now free to move above the stop and the engine is running. At shutdown, throttle-grip to idle, press the IDLE STOP REL button, and the throttle goes to stop with all it's consequences. Could one add the throttle movement from stop to the idle stop blockage and require that to start the engine? Sure, but would it actually bring anything to the table for the 99.98% of Huey vPilots who don't have an absolutely conform throttle-grip? I think not.

I am. The current function is garbage. It forces you to use the mouse to unlock the throttle. It could be done with a simply button press.

Yes, thank you. Your suggestion works, kind of. It used to be in older windows versions that command line parameters needed to be within their own quote marks. It seems that in Windows 10 the quote marks for parameters is not even allowed anymore. The path and executable must be inclosed in quotes, if the path contains spaces within one or more of the directory names; eg DCS World OpenBeta Server. So this is what is exactly required: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin\DCS.exe" --norender --server as the link target - YMMV depending on the location of your dedicated server installation.

I did, long ago. It doesn't work. The server crashes during startup. Thanks for suggesting something you've never tried yourself and that doesn't work.

Wow, thanks, that's pretty cool. Is it possible to build a hall sensor into the tiny engineering space? Has anyone done it? Any documentation? I was thinking of putting the sensor into a switch box and connecting the lever with a standard bicycle brake cable to the switch box, kind of like how the brake lever in the real Spitfires and Mosquitos worked, and then attaching the cable to the hall sensor inside the switch box. But you would still need to have a switch box/controller to hook the hall sensor upto. So, can you point me to instructions to build the controller/switch box? You can also mod the default.lua to use "press" to operate the latch at the same time the lever is moved, which partially works, but not everywhere. I have yet to figure out why.

For what? What does it bring to realism? Nothing, because it cannot simulate the stop, and even if you could configure YOUR collective throttle to stop exactly at the exact right point, practically no one else has the same hardware. What you are requesting can only be used by people with exactly your collective throttle. If ED programs that, more power to you, and I wish you fun with it. The rest of us want the ability to use the same kind of throttle motion we ALL can use.

And if once again DCS puts an update out just before my group meets, and the update needs an hour or more to download, how do I start the server without starting the download, because the binary executed when starting the dedicated server is DCS_updater.exe?

Why do you need the full motion at all? No other aircraft needs to have the full throw of throttle levers between stop and idle. You just need 'behind the stop = a key or switch assertion' and 'beyond the stop = lever axis motion'. That's it. Just like ALL the other aircraft. No need to make the Huey 'special', when it isn't.

Thanks for the reply, Mr_Sukebe, but all that refers to the DCS client running as a server, even if they say "dedicated server" they mean dcs.exe running by itself as a server without anyone using it to fly an aircraft. That is not the downloadable dedicated server software, which from the get-go had different command line parameters. Even asking in this thread about how to start the real dedicated server without updating, I got nothing but answers about how to run the client sw and the bitchy remarks that I didn't look enough. This is exactly why I requested to have a separate sub-forum for dedicated server discussions, but was directed here, which is like asking technical questions about the Boeing 777 and getting told to look in the 747 sub-forum

ooooOOOOOOoooo.... do you have a guide on how to build one of those things? Am thinking about putting something together with a bicycle brake lever and a hall sensor to use for the brake lever in the Spitfire and Mossie.

There is none. There is a guide for running the DCS client as a server but not the DEDICATED SERVER which is a different program.

No, that's not correct. I have the bomb bay doors assigned to a three way switch. To open the doors I flip the switch aft and immediately return it to center. In-cockpit the lever moves down and stays there while the doors are opening. Once open, in-cockpit the lever moves to the middle automatically. While closing it works exactly the same. The problem with the other levers (flaps and undercarriage), is that they have a lock mechanism to prevent you from moving them in one direction, without first unlocking the movement in that direction. NO ONE has enough buttons and switches on their HOTAS, button boxes, and control panels to have additional switches and buttons to emulate these extra unlocking mechanisms. You are forced to use the keyboard (NOT VIABLE IN VR!!) or the mouse (one of the worst and most lazy solutions implemented). There are many in-cockpit devices in aircraft with Real-World™ unlock mechanisms, which in DCS simply work by operating the device - the unlocking is understood and not required as an additional step. This has been done already many times. It's not a new invention -

Because Google wants your data. If you register, you must give them an email address. With your (an) email address, they far more easily track what you do in the internet, which they can leverage for advertising. If you are not paying for services someone provides, YOU are the product.

You ought to ask this in the AH-64 forum, or the DCS World forum.

YES! Thank you! That's them

Do you mean the two with the tool-tips "radio directional compass indicator power"?

Dumb question nr. 893, why doesn't my R.I. Compass Repeater work. It doesn't move for me. I can find no reference for turning it on or off, nor uncaging it, nothing. Tips?

If you have the WWII Assets Pack, there is a Jeep. I have no idea how to add any building to DCS. I'm sure it's possible. Look in the modders forum. I'm sure someone there can give you a tip.

IRRC you can fly the missions you set up for yourself anytime you wish, or you can edit the .miz mission to have them start when you want. It's up to you. If you want the AI flights to occur and terminate normally, you will have to let the mission run by itself until complete. If you are playing SP you can however accelerate the time to 20x so in won't take hours.

I depends on what you mean by "leave the simulator". If you have flown the mission(s) you wanted to and then quit DCS, everything in the Liberation mission remains as it is. There is no extrapolation of what might happen, if DCS ran another half hour, or an hour, or whatever. If you let DCS continue to run, even if you don't fly any further missions, the AI missions Liberation built (-- all those other flights going on around you, and those scheduled to start later -- they will continue to be flown until they have been completed. I don't know what happens after the last AI flight has RTBed; I've never tried that. Maybe Liberation ends the mission, maybe it waits for you to do that; idk.