majapahit

not for tripple screen only for Zeen

try to project them when you stretch your upper viewport to the whole your lower monitor is a black screen

OK thx weird actually, TARGETGUI.exe cannot load .tmc .. does run .tmc

TARGETScriptEditor.exe -r ? run script commandline not working anymore? Used to be able to run script from commandline with -r but not anymore? f.i. "C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETScriptEditor.exe" -r "i:\TEKST\My Games\TMWH_sc2324.tmc" only loads the .tmc doesn't run it ?

Will not work - yet - , overlaying the general view, only on black screens

With joysticks ..

Planes don't fly with keyboards, they're flown with joysticks.

A joystick (with a throttle and rudder twist) costs 40 bucks A semi HOTAS Thrustmaster T-Flight Hotas X about 60 bucks Even if you're on a notebook what's the problem?

I saw a documentary long time ago, the LSO camera is coupled to a monitor in the pilot’s mess, so they can make notes and comments (and no doubt to put some incentive in their asses). It obviously was also considered highly entertaining in atrocious weather in a pitch dark night, the wing commander swapping places in the sortie with the (female) rookie, stating ‘you’ll understand when we return’ .. and then you hear the (really) heavy thuds of the jets returning (I think they were six) in extremely foul weather that got worse by the minute, and this wing commander coming in last - flying fumes because of all the bolters from the sortie - and the LSO cam showing the deck rising and falling 10 feet or so, and he - of course - made quite the mind-blowing silky trap ..

One knows it caught, when there's steam coming from the rail. No steam no throttle, or you'll just drop from the deck.

yep

You still can, the HUD shows a 'shadow' vv, a cross, where the actual vv is.

Carrier take off defaults to 16 degrees for 33-34000 lbs (in the Quick Mission 'Carrier Take Off', resets to FCS flight mode after wheels and flaps up). More weight, then more pitch more power according to table and whats been said on the forum.

MDIs dont export on top of main viewports it seems

This doesn't quite work when exported 'on top of main export view', triple screen on side screens (MDI's don't, AMPCD does but has spider font which is unreadable)

dump everything

Nope, if you follow the plane to the very end, behind the crew it does not retract gear, end of view (~500 yards), AB blasting not pitching (whatever the weight the F18 can pitch with full AB) seems full Flaps so prob > 45000lbs

- with 'flew in' I meant final approach - caging the HUD is done when braking 180 your down leg turn in left and braking, so to see the HUD properly, across 90 across 45 and uncaging in the groove, supposedly - "It prob differs per year and which squadron" it is noticed on the interweb different squadrons and different years have different rules for their pilots. AE W who flew 20 years ago even mentioned 'it's up to the pilot to decide how he wants to fly' which is something I sincerely doubt these days (as in civil flying). He also mentioned an 'experienced LSO' can see from the plane behavior where the pilot is looking and this LSO has the authority to send you off the ship to 'refresher course' land side. In his time it was forbidden him, unlike what is said on the DCS forum today 'to fly the notch'. When the LSO notices the pilot does that he will down score, reprimand or much worse. They had to fly the ball. (So it now depends if you want to fly 'historically' of 'contemporary' ? :smartass: :) )

test with key assignment? assign f.i. "LAlt - 3" to ‘ UFC Option Select Pushbutton 3’ (I think its 3, right) be level and steady then keystroke ‘a’ then this "LAlt - 3" (EDIT: made a mistake here, 'a' is disengage, so you have to assign a keystroke to UFC 'A/P', f.i. "LCtrl + 1". So you would then enter "LCtrl + 1" then "LAlt - 3" to test the AP) if still nothing, check perhaps you have several redundant joystick axis assignments to pitch, ailerons or rudder? delete these in controls setup .. perhaps your joystick needs a small (1-3%) deadzone in the pith Y (unlikely) at the moment BALT ‘smashes’ the F18 to altitude hold (bit unrealistic) and shouldn’t have any problems (redundant joystick axis assignments my guess would be) Else ‘DCS_updater.exe -repair’ from a CMD prompt or something (within the .\bin folder?)

Real pilot AE W vid shows he always flew in with HUD caged, there's an indicator in the HUD when caged where the actual vv really is. It prob differs per year and which squadron.

A.E. W. also was a RL F18 pilot (20 yrs ago) he shows his truthful vids with all his errors and tell you what goes wrong AE W also points out where the DCS f18 model is still flawed which is of interest (f.i. the F18 should bounce from the deck and lift nose when on the deck still in a bolter, some flaps behavior etc) His YT channel https://www.youtube.com/channel/UCNvV27UZkI8W-jvMA-iGqyQ/videos

first press a/p ? be above 500feet (I think), RALT be below 5000ft

A workaround for the ‘define export per plane’ is (are) the *_init.lua files f.i. KA-50 ".\DCS World OpenBeta\Mods\aircraft\Ka-50\Cockpit\Scripts\ABRIS\ABRIS_init.lua" and the other one SHKVAL_init.lua F18 ".\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\MDI_IP1556A\indicator\MDI_left_init.lua" search for the *_init.lua files and change the default try_find_assigned_viewport("LEFT_MFCD") now change this default name ("LEFT_MFCD") and declare unique export names as f.i. FA18 try_find_assigned_viewport("F18_LEFT_MFCD") in case of KA-50 try_find_assigned_viewport("Shkval") and use the now unique per AC type declared name in <monitorsetup>.lua .. Shkval = { x = 1920-10-1600*0.75; .. and since "F18_LEFT_MFCD" you will not mention in <monitorsetup>.lua, F18 will not export its DDI’s, which is not supported and would result in blank cockpit DDI’s, so that what is wanted - for now - . The difference is now you do not have to go to options to change the <monitorsetup>.lua

I just discovered these new Mustang textures, thx mustang (best improvement of 1.5.8 )

One can dim the green and change color by RGB,brightness code in ".. \DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\materials.lua" : -- MDG_materials[MDG_SELF_IDS.HUD] = {2, 255, 20, 255} I changed to darker less bright (R,G,B,brightness) MDG_materials[MDG_SELF_IDS.HUD] = {65, 190, 65, 100} and --- MDG_materials[MDG_SELF_IDS.LMDI] = {94, 202, 0, 255} -- MDI original changed to same {65, 190, 65, 100} You might want {65, 190, 65, 155} but I liked a very dim font