Tiger-II

Not all of us have cushy 9-5 jobs. I'll take the updates as and when. I understand the frustration regarding MP, but I think much of that has to do with combating online cheating; it's simpler to at least ensure everyone is on the same version before doing deeper checks.

This is why it won't happen. It matters.

My rig: * i7 9700K @ 5 GHz * 16 Gb 3466 MHz RAM * GeForce 1080 (NOT Ti) @ 4K res * All settings maxed except AA options which are set to NONE.

The night lighting generally looks OK. The nav lighting in the sea for shipping looks absolutely amazing. The lighting at airfields, and particularly buildings, looks like it is on fire. Performance at night is lower than the day, suggesting the light sources are attempting to illuminate massive distances.

The external position light on the tail is still very bright when the switch is set to DIM. Nav Bright position is OK. Fomation lights suffer the same technical issue as the cockpit flood lights in that they are very bright at only 2/5 of the knob motion, and anything higher makes the lights look like they're on fire.

Hi, The night lighting looks stunning, but it needs balancing. The integrated lights in the panels are OK. The caution/warning lights do not dim enough. The panel flood lights are too bright too soon (anything over 2/5 setting is just far too bright). MFD day/night balance is totally out of whack. Day/night switches don't operate as expected. Map on MFD becomes hard to balance at night and contrast/brightness steps are far too large. HUD symbology jumps to maximum day brightness when FLIR is projected on the HUD. It should remain at the present setting.

I have the map, and see between 20 and 45 FPS. It's smooth, if a little slow. Perf was measured with deep overcast clouds.

? You need to add enemy units. Map loads fine here. From where are you trying to fly?

@CybrSlydrYou Sir, "get it"! Great screenshots and thanks for showing the perf data top left!

The point is, if you know where to point your RADAR, you can lock stuff further out without having to wait for it to scan first and build a picture. Think of the RADAR beam a bit like a variable flood torch. If you set it to light a wide area, it is dimmer and doesn't go as far. If you set it to be a really intense beam, it doesn't light much, but shines much further, allowing you to see further.

Nice going!

If they do, I hope they make it an option.

I remember watching videos mid-2020 of this thing. What happened? I get the "part time" thing, but those videos and streams were of a nearly complete project. Before anyone says "software" - that's my job so I know how that works. Did they go on holiday or something? This extreme delay of nearly 3 years is long enough to have started from scratch. Twice. I understand the FM problems with the Gazelle (I have it) but I'm left questioning if they can actually do this.

20 kts is a lot. What was your entry speed? Altitude? All my missions are set up for STP (Standard Day temperature/pressure). No wind.

Seems the binding is at fault. From the info I have it is tied only to the EXT LIGHT master switch, and when it is ON and the probe is extended, the boom light illuminates. As you state, AUX light is for the secondary landing light and is ON only when the EXT LIGHT master is ON, gear is DOWN, and AUX is set to ON.

It may be the AUX light, next to the position and beacon switches (left console).

I was just going to post this. These limits are SERVICE VOLUMES where accurate reception is GUARANTEED, but it says nothing of the absolute ranges they can be received at. If the simulation is half-way reasonable, it will at least compute the radio horizon, meaning if you're reasonably aligned with the ILS and at a suitable altitude, you can receive it. At the freqencies they operate on, you can expect to receive a typical VOR or LOC signal out to about 200 NM before it becomes too weak to receive (terrain and other ground features permitting). Glideslope is directional, as are localizer signals, so there will be an area where you can receive them, and a much larger area where you can not.

...so the answer is yes, you modified the sim. Users wonder why developers go insane at them... We know way more about it than you do. If we tell you to not modify it, we mean not one single byte.

Just knowing how RAF bases are laid out generally, these are munition stores. The buildings are seperated by distance so if one building goes boom, it doesn't take the rest of them with it. There may be other stuff there too, but for DCS purposes, treat it as munitions.

Interesting. What is the rationale? To highlight that it is in the DATA page?

AHHHHH!!!!! This may very well correct the problem! Going to try it now!

I can change the color of the pages as it is supposed to work, but the DATA page goes from green to red at some point during alignmemt process. Do you see this at all? Nothing is clicked - all it may require is switching INS from GND ALIGN to NAV. Changing the page color does NOT affect the data page. It remains red. I think this "issue" occurred after the last update a day or two ago.

The TPOD page doesn't appear to want to work correctly sometimes, as it is apparently being overdrawn by the FLIR or DMT or other page, and sometimes even if TPOD appears to be the active page, it seems something else is hijacking the inputs and it is actually another sensor that is being operated. I got it into a state last night shortly after starting the aircraft whereby FLIR was overriding the TPOD display, and the commands were apparently being sent to the DMT. Only after I got airborne and switched the pages a few times did it seem to "sort of" sort itself out and allow the TPOD page to be displayed and operated. Despite this, it still didn't appear to function quite right.

Hi, Continuing from the click registration problem with the MFDs, there seems to be a more general problem with MFDs and their handling. When aligning the INS (first flight after loading the aircraft) the DATA page of the EHSD changes color (usually to red in my case) for no apparent reason.The only operations made up to that point were to select EHSD -> DATA -> AC and enter aircraft position. No other selections are made. The color change happens when the INS is either aligning heading or enters NAV (I need to check). There is no apparent reason for this to occur.

Hi, This one will take a little explaining. When clicking on some OSBs particularly for the TPOD, but also some other functions, the "physical" button pressed moves in response to the click, but the systems do not respond and behave as if it was not clicked. This requires that the OSB is pressed several times before the click is registered and the system reacts. Note that I am talking about clicking the buttons with the mouse.