dwm

Thanks for addressing the issue. Here the DxDiag.txt, and a screen shot how it looks like CU

Yup, mee too, with only one single monitor. The NS430 is only fully seen if you drag the window of the NS430 to the full monitor size ... which makes it rather big and quite useless

Regarding Yamato ... and let me add a disclaimer here: Not really knowing what I'm talking about, but: If you look at the lua files of Yamato and Musashi, thats bb_Yamato.lua and bb_Musashi.lua, in line 29: GT.life = 400 ... while other battleships, like Iowa or also Bismarck have there (e.g. iowa.lua, line 38): GT.life = 6000 My guess would be this are the "Life points" of the ship. The huge discrepancy could explain why Iowa always beats Yamato. @chompsky: Just for playing around, i'd replace the 400 in the bb_Yamato.lua with ... 7000 ... restart DCS and try what happens in your mission. Maybe someone could comment who has more knowledge about these model descriptions? A little below, there is also a GT.DM list, which seems to describe a more detailed damage model of parts of the ships. Also here, the area_life fields are generally smaller for Yamato than for Iowa, but it's kind of less obvious. CU

That did it! Tnx 100x

Hi guys, first, thanks for this phantastic plane. Really nice, will be my trainer for learning carrier ops. A few things I'm not really clear about or which I think are not correct are obviously also there: One thing i'm currently not clear about is the shutdown procedure. With the throttle fingerlifts, you cannot get the throttle back to the "off" position once you moved it up to idle? I found one strange behavior: I cannot use TACAN any more (shows only "000" and the dials are not responding) if i place a ship on the map Tried with a Perry, a Ticonderoga and even the Truman (!), all of them made TACAN behave like that, making it kind of unuseable. Doesn't happen with the speedboats. The log complains about problems in a "get_carrier_data" function ... 2021-04-27 12:40:21.642 ERROR SOUND: source_add(host:COCKPIT_TACAN, proto:MorzeDot, alt_proto:): can't find proto 2021-04-27 12:40:21.642 ERROR SOUND: source_add(host:COCKPIT_TACAN, proto:MorzeDash, alt_proto:): can't find proto 2021-04-27 12:40:21.727 ERROR Lua::Config: Call error post_initialize:[string "C:\Users\dwmin\Saved Games\DCS.openbeta\Mods/aircraft/VNAO_T45/Cockpit/Scripts/Nav/MissionData.lua"]:79: attempt to index field '?' (a nil value) stack traceback: [C]: ? [string "C:\Users\dwmin\Saved Games\DCS.openbeta\Mods/aircraft/VNAO_T45/Cockpit/Scripts/Nav/MissionData.lua"]:79: in function 'get_carrier_data' [string "C:\Users\dwmin\Saved Games\DCS.openbeta\Mods/aircraft/VNAO_T45/Cockpit/Scripts/Nav/TACAN.lua"]:54: in function <[string "C:\Users\dwmin\Saved Games\DCS.openbeta\Mods/aircraft/VNAO_T45/Cockpit/Scripts/Nav/TACAN.lua"]:48>. 2021-04-27 12:40:21.727 INFO COCKPITBASE: lua state still active TACAN, 16 2021-04-27 12:40:21.735 INFO COCKPITBASE: lua state still active VOR_ILS, 17 2021-04-27 12:40:21.735 INFO COCKPITBASE: lua state still active NAV, 18 2021-04-27 12:40:21.735 INFO COCKPITBASE: lua state still active EFM, 19 2021-04-27 12:40:21.735 ERROR COCKPITBASE: TACAN::update:[string "C:\Users\dwmin\Saved Games\DCS.openbeta\Mods/aircraft/VNAO_T45/Cockpit/Scripts/Nav/MissionData.lua"]:118: attempt to get length of global 'miz_carriers' (a nil value) 2021-04-27 12:40:21.745 INFO Did anyone else observe that? Ups, and one more thing ... flying on the Nevada Map to a waypoint. There is a discrepancy between the direction to the waypoint on the HUD and HSI. Pretty exactly 12°, which makes me think about some handling of magnetic variance? CU

+1 Same issue also for ATC

Well, I downloaded it ... and it's missing textures, quite a lot of them. I tried the dropbox stuff, the textures were available there.

I'm asking myself how this is done IRL, or phrased in other words, are there procedures where the ground crew does the boresighting? An option or comm-menu-item for boresighting would be exactly that, right? Leaving the work to the crew chief. At least I can remember of a few videos where the boresighting was done on the ground, so basically it doesn't seem impossible.

Yesterday I realized these are the Marine VHF channels, wanted to know if this is implemented. After looking up the frequencies on https://en.wikipedia.org/wiki/Marine_VHF_radio, i placed in a mission a radio transmission on 156.8 MHz in FM. And - as it should be - the Hornet listening on S 16 - which is international distress, safety and calling frequency - can receive perfectly that transmission. Don't know if the Duplex-channels are implemented, but this can add pretty cool to immersion when a mission implements a ship calling Mayday on the correct frequency :) Tnx ED - this is pretty cool :)

Hm ... just looked at some Moose documentation - meaning, you have to get to scripting, of course So, without having tried: In PRINCIPLE, its possible to get the list of (unoccupied) parking slots on an airfield, which also contains the according coordinates. You can also spawn statics. So in principle, you can take the parking slots and spawn in some statics randomly on that positions, BUT: I don't have a idea, how to pass on the heading of these statics. Maybe i have to play a little with lua on the coming vacation days, that's an interesting idea

Hi, I tried to create a better immersion by placing a generator or air supply device close to the plane when ground power or ground air supply is connected. Unfortunately, i did not find an event to trigger such thing. Is there any way to get notified from such a event? Of course, I'm thinking for the same for refueling and loading ammo, would be nice to see a HEMMT or ammo truck. Its kind of strange to be on the airfield, seeing nothing, totally alone, nothing in sight, but someone is telling you "refueling" and "ground power is now connected". This causes some "Hey, what you're doing?" questions :) Tnx Werner