dwm

Cool

Also had a crash after a Bronco mission... used also NS430 there. Needs probably a little invstigation ...

The amundsen.zip file - the textures for the Amundsen Icebreaker seems to be broken in the download. These are cool ships ...

Thought about that too ... Rudel_chw, I think thats exactly the way to go. Maybe there would be the possibilty to define "routes" which are just a "series" of trigger zones, so ships could randomly spawn in one of the zones of a "route" and then follow through ... Think of a Tankers going through the street of hormuz ...

Very cool, thanks very much for that

Hat perfekt geklappt. Vielen Dank für die Organisation!! CU

Nice skins ... i wonder if we could have also the west german variant with the new template? The 24+20 ? tnx !

Bin da auch dabei.

Really cool mod, a big thanks to all the creators! This thing has potential! I struggled a little with the same issues as Fab8ball - Gear up/down mapped to a switch on the Warthog throttle need switching TWICE to work, Canopy open/close don't work, Canopy "toggle" works, but cannot be assigned to the keyboard, but only to a button? Does anyone else have the issue, that when pressing the engine crank, the throttles go to max?

I think thats the Su-35 mod. The radar is basically the Su 27. Would be cool to borrow the datalink from there? In the chinese mod, likely the J16, but not sure 100%

+1

Well, its weapons, so its ED ... thats at least what's Deka claims now for a few months Was also hoping for that fix.

I just played around, because i experienced yesterday also strange behavior. Scenario: Cold startup from Andersen AFB, TACAN 54X - TACAN takes quite some time after switching it on. Ok, just something to know. Its not "instantaneous" like in other planes, but after waiting ... around 30s i think, then it seems to show the tacan 2 miles from the parking place. Fine. - When NOT using the mouse scroll wheel, but "click and drag" on the channel button, it seems to come "loose", and is not adjusted to the displayed numbers any more. After this effect, if you scroll fully down it shows an "8" instead of "0". Also, to tune Andersen, you have to set the TACAN to 24X instead 54X. So it simply has an "offset" on the numbers displayed. Talking about the left button for the "tens". Well, its an old plane, you know. Very sophisticated simulation of buttons come loose Track is attached, together with the misson. CU Edit: I just reviewed the effect on the track - its NOT shown there. On the track you see me just adjusting the tacan to 54X, which then works. In play, different numbers are shown on the channel display. It's clearly reproducable with a "click and drag" on the channel button. dwm_f5tacan.miz dwm_f5_tacan3.trk

I think I found the problem ... It's related to the date of the mission ... you see the new islands ONLY on radar if the mission is in the month of June. Default mission date is 21st of June 2016, there everything is fine. Just switch over to November, and the new islands are gone on radar. I can reproduce that behavior on old missions and also ones created from scratch. Moved my old mission from October to June, and everything is fine. Can please someone else verify? To me, it looks like some development/debugging switch is still in there - or we found the secret of the Bermuda triangle ... äh ... Marianas ... CU

Aha ... interesting ... version is the open beta 2.7.7.15038, should be the latest. Just did some experimenting: - I used an older mission i normally use as template. Placed a F-18 airstart there ... I see the blip from Farallon de Medinilla, but not from Anatahan - I created a mission from scratch, with the same F-18, both Farallon de Medinilla and Anatahan are visible. Its in the MISSION? Thats ... interesting behavior. CU

Happens also in the F-18 ...

Hi @Flappie, just played around with it a bit... - changed pc resolution to 1980x1080, ran DCS - no success,issue still there - changed DCS resolution accordingly, switched off full screen ... no success, issue still there - changed back PC resolution to 3860x1600, ran DCS on only part of the screen ... no success, issue still there. Ok.. I thought, back to my normal settings ... - so DCS back to 3860x1600, full screen. Just for fun, changed shadows from "middle" to "Flat", switched cockpit from 1024 every image to 1024, shadow terrain objects also "flat". Tried again. ISSUE WENT AWAY!!! - changed back to settings before (Shadows middle, 1024 every image, Shadows terrain obj. "standard". ISSUE NOT REPRODUCABLE. This is how its now: The good message is, I now have a working NS430. I tried also to drag and scale it, everything seems now like it should. I really don't envy you to track down that one ... I can't find some direct relationship to one of the settings, but just fiddling around in the settings and one or two restarts seem to have fixed it? TNX Werner

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.