Nealius

My left throttle doesn't match my right--I suspect the physical detent is worn down on the left side--so I need curves for each side independently. Thanks guys. That gets me in the ballpark to fine-tune my messed up left detent.

In addition to the already mentioned hyperlinks not working, the table of contents is lacking page numbers and the title text of each section is unsearchable. E.g., searching "Normal Procedures" will not show the Normal Procedures section on p.726. This makes it rather difficult to find specific information in the manual.

Arguably the QC and "proper testing" should be finished at minimum a full business day before scheduled release. If that can't be done then reevaluating how release dates are set may be in order.

I wanted to throw my toys in the pram and go for a stroll, but the toy delivery is delayed; the driver forgot to fill up his tank yesterday.

Wondering if any of the staff or content creators or testers fly the Phantom on a TM Warthog with the afterburner detent, and could share their curve settings to align the Spook's detent with the Warthog detent.

Effective against that AH-1, which is a very small helicopter. Not equivalent to a large fighter. Generalization cannot be made from one very specific example. If you intend this example to be used when discussing effectiveness against DCS helos, and only helos, not other aircraft, then your point stands.

The snakeeye fins as well, now that you mention different bomb variants between the service branches. The 3D model has been in the file structure as long as the green and gray coatings have. On an unrelated note, why is this thread in Customer Support and not in DCS World Topics?

My question may not have been clear. Will we get both USN gray and USN green with the option? Pre-2002 the USN bombs were green, not gray. Both coatings exist in the DCS file structure. Wags' video only shows two options: USAF and USN, and makes no mention of what the USN selection will actually look like: gray, green, or dependent upon mission date.

@BIGNEWY @Flappie @NineLine Is the time period and availability of green ablative coating being considered for the upcoming fuse options and USN bomb options?

@renhanxue so if I want to fly using magnetic headings, I just need to set the KURSKORR knob to 0 and everything should be fine? Last year when I was flying the Viggen I was having some issues with the nav system error light illuminating and some nav accuracy issues even after setting BANS/GRANA course, because I hadn't been setting magnetic declination properly on the KURSKORR knob.

Previously, not setting magnetic declination FUBAR'ed the nav system. So ideally I'd like to have magnetic compasses show magnetic heading and a nav system that works.

All manuals and tutorials say to set magnetic declination knob to local magnetic declination on startup.

Having been personally hit by Iglas in both the F-16 and F/A-18 multiple times, I don't see an issue with the small warhead modeling. In the majority of cases I'm damaged enough to require ejection within a few minutes after being hit; usually fuel leak. I suspect this is an issue with AI damage modeling moreso than it is with the Igla itself.

When lining up on one of the Jokkmokk dispersal runways and inputing magnetic heading from F10 map (147 degrees), I noticed both compasses were showing about 152 or 153. Referencing the info bar 152 is the true heading.

Compare Mission Editor markings to in-mission markings. In the Mission Editor, the aft Tomcat's sidewinder rail is approximately 2ft away from the foul line, and both aircraft are covering ordnance elevators with their noses. In-mission, however, the sidewinder rail is crossing the foul line, and the ordnance elevators are starboard of the aircraft noses. Placing statics so that they do not cross foul lines or clip into other objects requires more trial-and-error than should be necessary due to incorrect marking placement in the editor.

Shouldn't Hatzerim be 100X, not 96X?

+1. Setting as uncontrolled AI doesn't allow specific placement of the static, often comes with various bugs (Petrovich sitting in uncontrolled Hinds, Mudhen's JFS sounds on infnite loop, etc.), and impact performance more than statics of the same aircraft model would in some cases.

My brain is having trouble making sense of the LOW display logic in the context of that screenshot. The altitude certainly is high enough for fusing, but it's showing >10 seconds (35 seconds) from release. While also simultanously showing 2.7nm and the release cue having already passed, which isn't making sense with the 35-second timer.

@Neuro246 Mercuryポッドは赤外線機能がなく、ＴＶ機能のみになっているので暗い夜に使うと画面が真っ黒になります。満月のあるミッションだったら表示される可能性あるけど、昼間のミッションだったら表示されるはずです。中間のミッションにも表示されない状態ですか？

The textures already look high quality to me when flying around, at least on par with all our other maps. The only texture issue I have is the mission editor/planner/F10 map SAT view having horribly low resolution textures.

How are the ranges set up? Setermoen has massive mountains with few flat areas for setting up targets. On Google maps I did find a range control tower in a large valley, but I can't identify any actual targets. I couldn't find any of the other ranges, either.

Directors as optional would be best. Users can enable for SP, disable for MP.

Now that I look at it, the beacon itself is on the wrong end of the runway, isn't it?

I'm curious if anyone else has tried Bodo ILS 07 and also found the glideslope too high and localizer left of the runway, or if I buggered something on my end.

Crossing my fingers for some default sounds that are better than the Echo19 offering