majapahit

Why would I care exactly .. ?

If you're precisely in the groove you won't know the difference. Like I said before. Be at the top of the groove. Go 100 feet to the right and up with speed. And then land after all. That is what seems to be easier (and more real).

Was approaching at 180, good control, trapped 150 I think. It's not about the numbers its about how the F18 behaves, which before the update 7 its controlled behavior was only in a very (very) narrow envelope, which was a bit suspect I'd say. (I was not the only one) Try flying off the numbers and feel how it's correctable now (unlike before).

This is what IvanK ED Testers Team wrote “ .. Autopilot coupling is possible (not yet implemented) using the VEC option. .. “ notice “ .. yet .. “ ACLS should be implemented for the F-18, would make for great fun, and all kinds of people would be able to land on the deck like landing a Cessna instrument rated.

Yep. <Modsfolder>\<name mod>\<dcs_sub_dir\dir\dir\dir\edited file> and this will show up in your mod management prog

make your own JSGME mod create directory in JSGME mod directory add edited file apply before update revert after update apply is how I run my 10 mods

(not yet implemented) means it is coming ICLS with VEC coupling Me thinks ICLS stands for ICarrierLS and ACLS for Automatic Carrier Landing System (prob) in a academic doc about ACLS "The United States Navy currently has only one aircraft type that is capable of fully automatic carrier approaches using the ACLS. This aircraft is the F/A-18 Hornet." (2007) F/A-18A-D Hornet Current and Future Utilization of Mode I Automatic Carrier Landings http://trace.tennessee.edu/cgi/viewc...t=utk_gradthes Several miles from the deck all F/A-18 fly-by-wire systems are coupled with the Carrier computer over the data link the F/A-18 is then fully hands off guided down the glide slope to the deck

not quite (not yet implemented) means it is coming ICLS with VEC coupling Me thinks ICLS stands for ICarrierLS and ACLS for Automatic Carrier Landing System (prob) in a academic doc about ACLS "The United States Navy currently has only one aircraft type that is capable of fully automatic carrier approaches using the ACLS. This aircraft is the F/A-18 Hornet." (2007) F/A-18A-D Hornet Current and Future Utilization of Mode I Automatic Carrier Landings http://trace.tennessee.edu/cgi/viewcontent.cgi?article=1356&context=utk_gradthes Several miles from the deck all F/A-18 fly-by-wire systems are coupled with the Carrier computer over the data link the F/A-18 is then fully hands off guided down the glide slope to the deck is what happens (can not wait)

Some DCS developer included in an answer to me that 'capture ILS' (which is 'ILS') "Autopilot coupling is possible (not yet implemented) using the VEC option." It's coming.

Update 7 flight model improved I think Testing update, joystick binding broken, no trim, no rudder. Take-off and circle, wide, correct, coming in at 180kn, 2nd wire, easy peasy. Before, I really (really) had to be close to the groove, and exact pitch. Suspect lots of little improvements on the flight model envelope / flaps / hitting the deck .. :)

getting there, great

missions might not be compatible with ICLS update

Anyone please post your ICLS .miz with freq. active Anyone please post your ICLS .miz with freq. active carrier takeoff or circuit land or straight in (I'm bad with this ME stuff)

so, ICLS is only FD on the HUD not actually capturing and auto holding the ILS path, right?

You have to use 'user snapviews' so to change the view of the default cockpit view which is shown by Num5 for default angles and Enter for default zoom. Snap views WIKI http://en.wiki.eagle.ru/wiki/Snap_views "In the DCS World, DCS A-10C or DCS Black Shark 2 installation folder, then folder config, then folder view, find file View.lua" UseDefaultSnapViews = true and change it to UseDefaultSnapViews = false "Customisation Procedure The keystroke RAlt+Num0 (default binding) will save the current view position against the last-selected Snap View ... " .. bla bla all of the NumKeys Snapviews .. Then this: "Customising the Default View" 1. Press Num5 to reset your view to the current default. 2. Adjust your view to what you want as the new default but do not use any snap view keys in the process!. If you have TrackIR, you will probably need to shut it off while doing this, otherwise it won't save the view the way you want it! My comment: for the new default cockpit view ONLY adjust Zoom so your zooms later in the game are not distorted by tilt or height change, where DCS expects zoom-in to go to expected positions 3. Press RALT+Num0 - your new default view should now be saved. "Test it by changing your view, then pressing Num5 - your view should return to your customised default! " You actually do Num5 then Enter to go from any position and zoom to Default cockpit view. It's a bit awkward to set up at first, but when you know, you know.

right one default? has the orange glow ..

'More' (not better) supposed variety ground definition in stock which gets all mush when at altitude. Orange saturation glow on stock doesn't help the mushiness either, on the contrary. Mustang makes for a clear color neutral landscape.

Editing the *.lua my DDI's, both in cockpit and exported to triple side screens look great. Not so much the AMPCD, thick horrible font and symbols still. running 6k

I downloaded a 1.08 version couple of weeks ago. how does that work? ?

Using the Zeen *init.lua added is ------------------------ added by Capt Zeen dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_AMPCD") ------------------------------------- end of added by Capt Zeen AMPCD_init.lua

you need to see steam. else you're not properly hooked up.

":\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\materials.lua" dim Intensity -- MDG_materials[MDG_SELF_IDS.HUD] = {2, 255, 20, 255} -- <<< MDG_materials[MDG_SELF_IDS.HUD] = {65, 190, 65, 148} and -- MDG_materials[MDG_SELF_IDS.LMDI] = {94, 202, 0, 255} -- MDI original -- <<< MDG_materials[MDG_SELF_IDS.LMDI] = {65, 190, 65, 148} format is - (R,B,G,intensity) helps (get rid of the glow), too low will become transparent (~135)

":\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\AMPCD\indicator\AMPCD_init.lua" .. try_find_assigned_viewport("F18_AMPCD") ..

Something got fixes in the latest 2.5.2.19157.408 "MDI's blank when trying to export to other displays - fixed." (can't resize yet, I think) I'm using triple screen and 1 screen underneath width = 5760 height = 2160 using the mods that specify a specific MFCD name in the Multipurpose_Display_Group *init.lua that translate to the <monitorsetup>.lua Looks great

Something got fixes in the latest (can't resize the MDI's yet, I think) I'm using triple screen and 1 screen underneath width = 5760 height = 2160