heloguy

Wondering if anyone else is having this problem. It seems like since I updated to 1.2.6, I can't take a screenshot of the mission editor anymore. I like to scale the map, and make strip charts, and then put them on my iPad to use to navigate during the mission (great for the helos, as 1/500k isn't the best for terrain flight). Anyway, when I try to take a screenshot, it's nothing but a black screen when I paste it into Paint. I'm running windowed mode with two screens, and the second screen with my desktop shows the desktop, but the other is black. I tried putting it back into full screen, with the main screen as the only one as I have had it set up in the past, but the same result.

In the US, this depends on the helicopter. The CH-47 actually has a flight engineer, and in combat an extra crewmember to man the second gun. Same on the CH-53. Most of the time, though, these guys can't operate the engines, only the APU.

This may, or may not be true. The National Guard still flies A model Apaches, and who knows what is actually classified and not classified about this aircraft. Could be why ED said they were going to do it a long time ago, and it hasn't moved forward.

UH/MH-60

Okay, so I looked a little more in the mission editor, and Springfield 1 had a landing trigger on Waypoint 0. I deleted that, and the mission played as I assume it was supposed to. Of course, both myself and my copilot were wasted on our second gun run on the vehicles, but better than doing circles at the airfield. Edit: Confirmed that this worked, just finished the campaign.

Yeah, just tried this one for the first time. Definitely not too realistic for the poor Huey. It's just not made to go that high. If you look at the -10, the performance charts only go up to 14,000ft PA. It could be completed with the hop method, by letting the emergency governor at full throttle build the rotor up, then max collective while moving toward the edge in order to takeoff, but this would definitely destroy the engine, as my EGT was well over the 625 maximum, and probably close to 760 (didn't notice during my attempt, just that it was in the transient range, which isn't supposed to be used on purpose). So, it could be done in the SIM, just not in IRL. Need a Blackhawk to do it safely, and this would even be a tough mission for that helicopter.

Went and turned on labels just to confirm: I am following Springfield 1-1, and he continues to just do circles over Kutaisi in mission 15 of the UN campaign. Just updated to 1.2.6, and was going to play this mission (I guess it's the last one in the campaign), but have never played this particular one before. Never had troubles with A/C not flying their waypoints on other missions. I looked at the mission in the mission editor, and it has a defined flight path that looks right, but seems to get just to the eastern edge of Kutaisi, and turns around right when he says "Form up heading 060, 90 knots." Edit: Sorry, but by Kutaisi, I mean the airfield at Koptinari.

Okay, who the heck am I supposed to follow. If I take off and assume the hueys will form up on me, and follow the H60s or the Mi-24s, I get a mission fail for not following the leader. But, if I follow the Huey that is hovering in front of me, I can follow him forever, and not get a mission fail, but he will just fly around Kutaisi at 100 ft, acting like he's trying to form up on me while the rest of the aircraft actually go do the mission.

Yeah, who knows who posted the video, and how much they know about helicopters. If you artificially induce ground resonance, I'm sure you understand that it will destroy the helicopter if you let it continue. That test was done as a demonstration on what it will actually do. Probably in an old A model 47 that the Army was throwing to the boneyard already.

The aero manual mentions that ground resonance is more prevalent in 3 bladed, fully articulated rotors systems. Hence this video:

Ok, just flew it again, and didn't have any issues. Weird. Of course, Murphy's law, I saved my rockets until the last engagement, and ended up only using miniguns the whole time. Made the take off from the embassy building or whatever it was real interesting. Stayed in ground effect, flying around the buildings until I was through ETL.

There are no set numbers for vertical speed, forward speed, and power. It's all based on gross weight, and density altitude. No one has ever tested an aircraft and made a chart, to my knowledge, that specifically tells you the parameters that an aircraft will get into VRS at specific gross weights, pressure altitudes, and temperatures. There is just advisement that if you are at least descending at 300 fpm, little to no forward airspeed, and some power applied (between 20-100%). If you are in those parameters, you are taking a chance, and you need to be able to recognize the symptoms in the aircraft. Unfortunately for sim players, a lot of those symptoms are vibration and feel, but luckily, Belsimtek has included the feature of the model itself vibrating, which some people have hated, and some people have liked. I for one love it, as I can fly on the sim, and know pretty much what's going on, especially transverse flow. Btw, if you find yourself in suspected VRS, you just need to fly out of it, either forward (preferred), or any other direction really. Hopefully you have enough altitude when you figure out.

Yeah, I just flew that mission for the first time, and when attacking the insurgents on the rooftop that are firing down at the H-60's, there ended up being one dude stuck half inside and half outside of the building on the ground. I was out of rockets, and hovered in front of him expending all of my minigun ammo, and then landed to have my door gunner try. Nothing worked, as I guess his 'hit box' was inside the building. Not sure if rockets might have worked. The Mi-24's couldn't kill him either. P.S...I love the campaign Belsimtek, and this isn't a complaint, just advisement really, but no self-respecting Blackhawk pilot would just sit there and let his crewmembers fire back at a bunch of dudes shooting down on them from a building. There's no such thing as being pinned down in a helicopter. You just take the hell off, and get out of there.

I had this same problem, but upon reinstalling the module, realized you have to choose the type of activation key when it comes up, otherwise it will say yours is invalid.

At least you got the update. My auto-updater hanged, and won't do anything now after repeated "repairs" and retries. Now I'm downloading everything for a clean install...if my load times suck with that, I'm going to strafe civilians. In the sim of course.

I really hope you mean reticle lamp, 'cause if there's a rectile lamp, I don't want to find it... Anyway, still downloading, so can't help yet, but I'll let you know, just couldn't resist the reply.

So, I started the updater yesterday when 1.2.6 was released, but decided that I'd wait a little while until the server wasn't too taxed. Last night before I went to bed, I ran the updater again in order to let it run all night. The updater hung at 15.6kbps, and the amount downloaded never changed after 8 hours. Right now I'm downloading 1.2.6 to do a clean install, but I'd really like to know if I will have to run a deactivation, and activation during the process.

I'm having issues with this too...dropped it in the Scripts folder under my user name as described before, and the only profile working is A-10C. I've deleted and added the interfaces for BS2 and FC2 on both of their respective profiles, but so far no dice.

Wow, thanks. Guess I need to brush up on my search skills...

I'm trying to use both an A-10c profile and Ka-50 profile in Helios, but it seems that every time I update the path for one, it breaks the gauge exports for the other. I can get each to work, but only if I start up the profile editor, and update the path before switching aircraft (ie, quit Helios, quit DCS, update the path, then restart everything). Anyone know a way to get everything to work to where I don't have to do that?

Not sure what you're talking about here...if you mean how they switched sides with the tail rotor, that has nothing to do with what direction the rotor head spins. It still provides thrust in the same direction, just on the opposite side of the tail. Some people get confused when they look at a UH-60 tail rotor when compared to other U.S. helicopters, but rest assured, it still provides thrust to the left, just as a UH-1, H-53, or B206. I'm pretty sure the answer as to why different helicopters spin different ways is as simple as someone chose one way, someone else chose another.

Alright, cool. Thanks a lot for the info. I have several mods I use already with JSGME, and just started setting this one up. Shouldn't be too hard now that I looked into it. Thanks again!

I just downloaded the mod, but my next question is, everything my install is updated by ED, I'm going to have to reinstall this mod in order to have my monitor setup correctly, right?

I didn't install any modded files, no. I must not have read that post. I have tried just using RWR and RWR_Screen, though, without any modding. Are both of these wrong?

Okay, so this is weird. I'm running the most current version of DCS-World, 1.2.5.16508, and I'm trying to get my second monitor up and running with both MFCDs and the RWR. So far, I've got the MFCDs working just fine, but for the life of me I can't get the RWR to come up. Weirder still, I can only get the MFCDs to come up if I name them Left_MFCD and Right_MFCD respectively, instead of the newer names I've seen that are supposedly the right ones with DCS 1.2.5. I had everything working with the MFCDs, and then decided to add the freeware version of A-10C Virtual Cockpit server for my iPad. Once again, everything is working fine now, except the RWR. I've tried three different names for the gauge, but no dice: RWR, RWR_Screen, and ED_A10C_RWR without result. This is my current config: _ = function(p) return p; end; name = _('A-10C Virtual Cockpit Server'); Description = 'Setup for A-10C Virtual Cockpit Server MFCD and CDU Exports.' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.7777777777777777777777777778; } } LEFT_MFCD = { x = 1978; y = 105; width = 391; height = 391; } RIGHT_MFCD = { x = 3149; y = 105; width = 391; height = 391; } ED_A10C_RWR = { x = 2442; y = 138; width = 159; height = 159; } UIMainView = Viewports.Center Any help would be awesome!