wolle

Just want to make sure you have the latest version (called The Helicopter War, see here)

Holy crap, that's impressive. What IAS and rotor RPM do you recommend for autorotation? At what radar altitude do you start pulling on the collective to cushion the decent? I mean for a general autorotation, not your "stunt" involving the friate.

I am presently looking into buying a new high-end gaming PC for DCS. Unfortunately I am not much of a computer expert, so I need to rely on complete computer sets I can buy online. Does anyone have experience with http://www.cyberpowerpc.com/, their prices seem to be quite competitive. However, I emailed them about a week ago with some questions, no answer yet. So, I would be glad if people could tell me how their experience with this vendor went, and how satisfied they are with the product. Thanks.

I agree, that's why I wrote "seems". Seems to me that player aircraft and client aircraft are coded in an identical way (e.g. you can select freely among the client aircraft of an MP mission even if you play the mission in SP), that's why it is hard for me to understand why some things only work for "Player" but not "Client". But again, probably just "seems" that way to me.

This would be a really important feature. I don't understand why they haven't implemented it yet. Seems like that would be a 5 min programming job, at the most...

I haven't looked into that in the latest version of DCSW, but in previous versions it was important to set the connection speed to LAN (which you did), but also to disallow an option in the config file called something like "allow object_export". Unfortunately I am traveling right now, and don't have access to my DCS install. Maybe someone else can clarify.

I am having the same difficulties, glad you bring this up. Although with some practice and "tricks" like those mentioned by cibit you can minimize the difficulties. Nevertheless, I have the feeling that the wheels-mechanics and rolling motion on ground of the Hip is not yet modeled well. This reminds me of the early P51D betas, when rolling the Mustang on the ground (i.e. taxiing) was a near impossibility...

Helicopter War mission with Mi-8 ADF I quickly adapted the Helicopter War mission to allow use of the presently available Mi-8 ADF system. I have not yet carefully tested it, and hope I didn't break anything when I made those changes. Since I will leave for a three week business trip tomorrow, I will not be able to work on it for a while, so I thought I'd throw out the present version. Maybe someone has time to test fly it. Other changes compared to the version posted in the "User Files" section of the ED webpage include: now uses mist 3.2, which means that several bugs caused by bugs in mist 3.0 are fixed. now includes the possibility of helicopters ferrying supplies between ships and airbases (co-pilot will call out instructions to the pilot to aid landing on ships) I'd be glad to learn if the Mi-8 ADF stuff works for them. B.t.w. since there are presently only 6 available ADF frequencies, units will eventually reuse frequencies. For that reason, a given ADF frequency may guide you to a different unit than you might think... EDIT Oct 12th: fixed bug with F10 radio items. The Helicopter War Oct 11.miz

Does that mean ADF is working now? Are the 6 preset channels the only frequencies available? How can the preset frequencies be changed?

I have a hardware question. Is it better to invest in a single super-duper-mega graphics card, or several lower-end cards instead? What considerations go into such a decision?

The following code works local vars = { units = { [1] = { ["type"] = 'Infantry AK', ["name"] = 'Unit #1', ["heading"] = 0, ["skill"] = "Random", ["x"] = pos2.x, ["y"] = pos2.y, }, -- end of [1] }, visible = false, hidden = false, category = 'GROUND_UNIT', name = 'group name', country = 'USA' } mist.dynAdd (vars) The following code doesn't local vars = { units = { [1] = { ["type"] = 'PERRY', ["name"] = 'Unit #1', ["heading"] = 0, ["skill"] = "Random", ["x"] = pos2.x, ["y"] = pos2.y, }, -- end of [1] }, visible = false, hidden = false, category = 'SHIP', name = 'group name', country = 'USA' } mist.dynAdd (vars) It works after I change your code from if newTable['category'] == 'GROUND_UNIT' then mistCategory = 'vehicle' newTable['category'] = mistCategory elseif newTable['category'] == 'AIRPLANE' then mistCategory = 'plane' newTable['category'] = mistCategory end to if newTable['category'] == 'GROUND_UNIT' then mistCategory = 'vehicle' newTable['category'] = mistCategory elseif newTable['category'] == 'AIRPLANE' then mistCategory = 'plane' newTable['category'] = mistCategory elseif newTable['category'] == 'SHIP' then mistCategory = 'ship' newTable['category'] = mistCategory end

dynAdd doesn't allow ships Hi Grimes, Not sure if this was raised before. dynAdd in Mist 3.2 does not allow creation of ships, because it only recognizes categories "GROUND_UNIT' and 'AIRPLANE'. Is there a reason for that? I modified your code a little such that it also checks for category 'SHIP', but I am wondering why you left it out. Does it mess up something else?

I hope that we will get interactive training missions for the Doppler navigation and other navigation systems. Reading a manual just isn't enough for me to understand those things.. Or at least a demonstration video..

I want them to add operational navigation radios, akin to FM homing and/or ADF that we have in the Huey. Those are not yet operational in the Mi-8, yet, right? Does anyone know what sorts of navigation radios the Mi-8 will have/has in real life?

Hi Grimes, Great thanks!

Hi, Is there a way, using the scripting engine, to inquire whether or not a unit is out of ammo?

For me the highest priorities are: - implement missing radios, in particular navigation radios. - more tutorials - English manual

Got it, thanks!

I can't even find the clock. Where is it in the cockpit?

Sven and Grimes, If you also want to fix the "On Road" bug (making groundunits move on a road doesn't work any more), change the lines: if point.form and not form then form = point.form end in mist.ground.buildWP to if point.form and not OverRideForm then form = point.form else form = OverRideForm end That at least works for me Wolle

'On Road' doesn't work any more path = {} path[#path + 1] = mist.ground.buildWP(position1,'On Road',speed) path[#path + 1] = mist.ground.buildWP(position2,'On Road',speed) mist.goRoute(groupName, path) does not make a group move on a road connecting two points any more. Not sure if this is a MIST issue or DCS World 1.26 issue. This used to work perfectly in MIST 2.0 and DCS 1.2.5. I updated both recently so I am not sure which is at fault.

Is it only me or does the Hip hop around excessively when one lands on grass or uneven ground? Landing on a tarmac works fine, but landing on grass makes the ship want to roll over on its side or hop up and down.

Thanks for figuring this out!

Thanks man, got it.

I'll have to look into that. I did not disallow rearming. It rearmed OK in the Huey version AFAIK. So, it could be either a beta thing with the Mi-8, or it requires different ground units to be present. Need to do some testing. I am very new to the Mi-8, and don't master using the weapons systems, yet. So, I chose this weapons load-out blindly, and haven't yet tested it if it is reasonable regarding game play of the mission. You can very easily change the weapons load-out in the mission editor. Maybe you can play with that and report to me what is a good weapons load-out. At the moment the number of troops it loads is a fixed number (8 for the Huey and 20 for the Mi-8 to reflect its larger payload capacity). But I can easily change that number to any value (maybe to 8 and 16?). Possibly, I changed some things, and then back again, and so on. Not sure any more how it exactly compares to the previous version. In addition there are now 2 escort helos on each side flying around too...