Wrench

How do you get the cokcpit to use roughmet? I've been on this for a few hours and can't get the model viewer or the sim to load anything but the default specs. (bf109) I've gone over the description.lua about a million times to make sure everything is right.

I'd like to do some cockpit mods, but I can't find any templates for them, and I don't particularly feel like spending many hours carefully selecting one pixel at a time. Anybody got some?

Know system-wide problem. Missiles in DCS have various problems, daring back to version 1.0. My understanding is due to reliable data (a lot of this stuff is still classified) and that they were hampered by simulation tech at the time. Therefore, the underlying code makes a great number of (inaccurate) assumptions about missiles. Namley their drag coefficients, guidance programming, thrust capabilities, etc. I know ED has had this on their RADAR for a long time, and the drag stuff is being worked on (IASGATG did a mod a while back, and has since worked with both heatblur and ED on this issue) and we've seen in recent changelogs that they're getting to the guidance issues. The guidance issues are the biggest factor in what you describe. The trouble is that DCS missiles just fly straight at the target all the time.This is why you see AMRAAMs pull 40 G off the rail with a 20NM shot. In reality, missiles don't maneuver at all unless they have to, and even then it's very energy efficient. Sounds like we're finally getting movement on that now, too.

It's been a bit since I've flown the hog. But I think you can to this with the TAD. iIRC, one of the hook funtions is (for displaying bearing and range) is hook>SPI. You you can set one waypoint to SPI and hook the other. Not sure though you'll have to check.

I hadn't planned on it given you have TACAN, but sure.

That's badass. I'll be first in line to download it.

I give the AI warbirds a centerline bomb and add the "restrict jettison" action It doesn't fix the underlying problem, but it does take a rocket booster down a few isp.

Also, if you're creating waypoints manually, they should "snap" to the ground if you don't input an elevation. You'll see CR pop up on the WP page when this happens If it doesn't input to coordinates again after creating the WP.

It sounds like you waypoint is at altitude. Verify that waypoint's altitude is at ground level. As for the Mavericks, they won't launch without a lock. I assume you mean IR guided mavericks, as that's what 99% of pilots use 99% of the time. You WP problem shouldn't have any effect on mavs, though. Not sure what the problem is there, I haven't flown the 'hog in a while.

When he says "BRA" then a bunch of numbers; BRA stands for Bearing, Range, Altitude. So the first thee numbera are just that. bearing and range from your aicraft to the target. Altitude is their altitude above sea level, in feet. He'll then say "cold" "flanking" or "hot" This means they are flying away from, perpendicular to, or towards you respectively. When he gives a call using "BULLS" it's the same information, but using a reference point called the "bullseye" instead of your aircraft. You'll see the bulls on the map, and in certain aircraft can display your bearing/range to the bullseye on the HUD or MFD. A "PICTURE" is just that: a report of all known enemy activity. Usually given in BULLS format, IIRC. A "vector to home plate" is to help you navigate back to where you last took off from. I think that's about it.

Suddenly have a reason to start learning German again.:book:

The AI is particularly good at tainjng to fight the alternate history version of the spitfire, in which von Braun was paperclipped by the Brits in '39 and helped supermarine design a rocket-powered spitfire.

Nice VR recording, man. It's gonna be pretty imperative to have pedals for a helo. I used to fly the Huey with an old (old, old, old) saitek x45 with the rudder paddle on the throttle, and even with that it was nigh-on impossible.

Multicrew really needs to be a thing. I know the devs are always busy as hell, but I'd like to see it as a priority now that the devs of the l-39 are also the devs of the Huey. Maybe after heatblur drops the tomcat, #twomoreweeks, multicrew will get a bit of a boost. From what I've heard, they've done a lot of work on the underlying systems to make that work well. Sorry, that was kinda OT. I wouldn't hold my breath for a later version of the Huey. I think they made a post a while back denying rumors that something like this was planned, didn't they?

Can you post you Miz? Or send me a PM if you'd prefer.

I did this way back when I first started flying helos. Disable any/all cyclic curves, auto pilot systems, trim, and anything else that can change the feel /help you hover. Seems counter intuitive, but the logic goes like this: Firstly, you can't take full advantage of systems designed to assist a capable pilot in hovering if you aren't a capable pilot. (Not to doubt your skills here, I just mean that you can't perform the task at hand to a level with which you're satified) Secondly, those system act as a crutch for those who lack the fundamentals of hovering a helo. Thirdly, making it as difficult as possible (within reason) to hover will force you to develop the skill required. Remember that's its actually harder in the sim as you don't have your natual physical sensation of balance to aid you, and have to go by sight alone. Then, take some time to just practice hovering. Start with an object (somewhat) nearby. Hangars at the end of a long ramp work well for this. Use them as a point of reference, and resist the urge to look at the ground directly in front of you. Add ~5knots of wind, fly a heavy helo, whatever else you can to make it difficult. Set aside any other goal, and just practice. Don't allow it to frustrate you, but remember that every second you spend not hovering, your brain is storing every mistake, and you will suddenly subconsciously be able to hover. At some point, it will "click" and you'll be able to hover while holding a conversation with one eye closed while smoking a cigarette.(shame on you, you really should quit:lol:) I'm not suggesting that something isn't broken, and that hovering this particular helo at this particular time is not more difficult than it should be. But by doing all of this you'll get to the point that no matter how broken the FM is, you'll be able to handle hovering it. But seriously, I use both a Warthog and an sidewinder ffb2, and I don't use curves for any module, except on rudder pedals as they are very coarse from the factory. I've flown helps a lot with both sitcks and can tell you that especially with helps, all that curves do is mess with your subconscious/"muscle memory" ability to control the aircraft. Anyway, to sum up the novel I just wrote, Curves bad, practice good. And even if it's broken, you can make it happen. And also, I'll add that in the Gaz it's very important to have an almost perfect hover for autohover to come on, so that's the cause for the diatribe on hovering.

I know multicrew has been broken for a while. Is there a better source to get news from than here? I'm not complaining, but I'd like to at hear hear about some progress, and get an idea of when functionality might be restored.

I've always like the 109 and bought it a few years ago. Finally getting around to posting this question here: Is there anybody who flies the 109 regularly that can help me get proficient in dogfighting in the thing? I'm pretty familiar with the aircraft, but I'd like someone who really knows how to fly max perf to help me learn how to really be an effective combat pilot. The trouble has always been there's not enough WWII activity online. Burning Skies is really the only server I'm aware of, and there's almost never anybody on. And those who are on don't even use Voice Coms, which I largely consider a basic requirement of MP now that SRS makes it so easy.

Carrier script HOTFIX 1.0.1 uploaded. In other news, RE: Got it fixed. It was a combination of a few errors. I also took the liberty of updating it to version 1.0.1 as added to the 1st post. _1_test.miz

I'll have a look asap. I've gotten a few bug reports and I'm making some tweaks, so I'll make sure that yours is a known issue.

That's odd, since it only runs once at mission start. after that it shouldn't matter.

Polychop pulled support for the gazelle's multicrew. Apparently it's broken.

Found them in the Stennis.lua. to ideal glide is 3.5 with a total range of 1.7. some math later I figured out the angles needed.

Does anybody know the exact angles that DCS used to determine the IFLOCS ball? As in your glideslope angles. Like 0-2° is low 2-3° is on 3+° is high. That kinda thing. Need it for a script, thanks.

True speed is groundspeed+windspeed. Hence the difference between the two. But is the speed in the ME should give you that groundspeed in the sim for sure. For reference, I wrote a script to deal with carrier's speeds and directions in the missions subforum.