Ramsay
-
Posts
3744 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Ramsay
-
-
...is it possible to add a flight or make one also client flyable so COOP can be done without affecting the campaign?
You can perhaps try editing the Spitfire IX Operation Epsom Campaign Sample mission, that should work.
-
Is AWLS working in NTTR. I cant get it to work.
AFAIK AWLS worked in NTTR in the past, however last time I checked in 2.5.3 it was broken at Nellis AFB with zero wind (RWY 21/AWLS Ch 13).
I've rechecked using Open Beta 2.5.4.25729 and it's still the same.
Note: a A-10C detects the ILS in the same mission, so it's not a map/wind/ATC issue.
-
So, the ALWS works in the same channlization as it does in the Hornet and changing this value to 180 will give you a (more or less) accurate indication from in the jet?
The edit fixes the Tarawa's ICLS so the Hornet is able to fly the correct azimuth and glide slope for the Tarawa VSTOL/OLS ball.
... reguardless of how the AWLS channels are set up for the ground stations?I've never had the AV-8B AWLS give an indication for the Tarawa (though the AWLS tacan will read correctly if set to the right channel), which is unsurprising as, AFAIK Razbam's AWLS uses DCS's ILS frequencies, etc. as defined in "AN_ARN128_config.lua", not ICLS channels but perhaps you've found a working combination or a configuration edit that works ?
I suppose Razbam could make a DCS>Options>Special>AV-8BNA setting for AWLS with
• AWLS=AWLS (Case 3) - that is realistic and uses ICLS
and
• AWLS=ILS (FCLP) - for Field Carrier Landing Practice and uses the existing config file and ILS (as a faux for a AN/TPN-30B, etc. setup)
AFAIK Razbam haven't made a statement about the divergence between the publicly available information and their AWLS implementation.
-
How do you do this, please?
By editing GT.LSOView position in "LHA_Tarawa.lua" i.e. turn the camera 180° and point it up along the 3.6° glide slope.
-- Aviation Facilities GT.Landing_Point = {-71.0, 19.9, -8.0} GT.LSOView = { cockpit = "empty", position = { --[[connector = "",]] offset = {-69.0, 19.9, -8.0, [color="SeaGreen"][b]180.0[/b][/color], [color="seagreen"][b]3.6[/b][/color]} ---MONITOR DECK PLAT CAM --offset = {-69.0, 19.9, -10.75, [color="Red"][b]0.0[/b][/color], [color="red"][b]0.0[/b][/color]} ---ORIGINAL } }Note: The camera position is still WIP as I want to align it with the 'Tram Line'.
-
AWLS and ICLS are the same thing, right?
Yes i.e. the Navy was testing AWLS on a LHD but a Harrier wasn't available, so they used a Hornet as testing the AWLS 'beam' didn't require the Hornet to land on the LHD.
Note: The Hornet ICLS and AV-8B AWLS share the same ARA-63 decoder, however there may be some engineering differences.
All the information I've found suggests they function the same i.e. localizer +/- 20° Azimuth, only +/- 6° having proportional information.
-
I have tried to make an approach to the Tarawa using the AWLS and got the localizer and glide slope indications, but it brought me into the boat with about a 10 degree offset to the right, just like the ICLS on the Stennis. That can't be correct, can it?
TL;DR:
Unfortunately "LHA_Tarawa.lua" isn't setup with the correct Localizer value (180°), being set at 189° i.e. 9° off.
Detail:
You'll need to edit:
DCS World\CoreMods\aircraft\AV8BNA\LHA_Tarawa.lua
-------------------------------------------------------------------------------- -- SHIP DESCRIPTION -------------------------------------------------------------------------------- GT.life = 7300; GT.mass = 38900000; --7.2916e+007; 72916000 GT.max_velocity = 15.4333; GT.race_velocity = 15.4333; GT.economy_velocity = 15.4333; GT.economy_distance = 7.408e+007; GT.race_distance = 7.408e+007; GT.shipLength = 233; GT.Width = 48; GT.Height = 64.36; GT.Length = 250; GT.DeckLevel = 19.98; GT.X_nose = 108.728 GT.X_tail = -124.096 GT.Tail_Width = 31.753 GT.Gamma_max = 0.35; GT.Om = 0.05; GT.speedup = 0.119249; GT.R_min = 665.8; GT.distFindObstacles = 1048.7; GT.TACAN = true; GT.TACAN_position = {-37.969, 56.996, -10.786} GT.ICLS = true; GT.ICLS_Localizer_position = {-153.0, 12.0, 9.4, [color="Red"][b]189.0[/b][/color]} -- {x [m], y [m], z [m], yaw [deg]} GT.ICLS_Glideslope_position = {-79.0, 26.5, 32.7, 3.5} -- {x [m], y [m], z [m], glideslope = 3.5 [deg]} GT.OLS = { Type = GT_t.OLS_TYPE.IFLOLS, CutLightsArg = 404, DatumAndWaveOffLightsArg = 405, MeatBallArg = 151, GlideslopeBasicAngle = 3.5, VerticalCoverageAngle = 1.7 } --------------------------------------------------------------------------------I also did something similar for the LSO camera as it faces forward by default.
-
Any gray scale MFD's that you've seen on youtube for the AV-8B are from early wip builds i.e.
Note: ED are working on better FLIR, so it's likely to change again sometime in the future.
-
I am curious about when the AWLS will be available on the Tarawa.
It already is, it uses the same microwave system as ICLS used by the Hornet and can be set in the mission editor.
However Razbam modelled the Harrier's AWLS before ICLS was added to DCS, so made it compatible with land based ILS.
ED could enable an ILS option for carriers* but it'd be a simplification and unrealistic (so IMHO is unlikely to happen).
Perhaps a realistic AWLS was outside of Razbam's original plan and they are hesitant to change (remove) the existing ILS support that players have grown used to.
*Note: Even if ILS was added to the Tarawa, there's no way to set a ILS frequency in the AV-8B as AWLS uses channel numbers as ICLS, you'd need to edit the AV-8B configuration file.
-
The mission editor ? What has CA to do with that ? Is CA about creating own scenarios ?
As it only comes with a couple of scenarios, I'd say you need to be willing to learn the ME and add your own if you want to computer stomp but that isn't what I meant.
CA ai unit route planning/orders, waypoint setup, ROE, etc. are fairly basic (not as advanced as ARMA 3's), you can't drag/select a group and shift click a series of waypoints like in a RTS.
Rather you select a unit - add waypoints for road, cross country, pathing etc. and set ROE. Although the GUI is slightly different to the ME, the process of controlling units and their limitations are similar to setting up routes and waypoints in the ME and knowing it, helps (less stuff to learn).
My impression has been that CA is some kind of strategy game within the DCS framework.CA has potential (i.e. when used with MOOSE) but it lacks many 'quality of life' GUI improvements found as standard in modern (1990) RTS's because it's based off the mission editor.
IMHO CA works best for MP game masters who want better control of the AI or for a MP player JTAC who wants to talk-on/lase (it's what CA was designed for).
It's possible to play vs other players/the AI and I know of players who find it enjoyable but I found CA slow and micro intensive compared to other programs.
-
IN DCS a plane helo usually have interactive tutorials and some instant action missions together with single missions and sometimes a campaign.
How is it with CA in this regard ?
Very weak.
There are no interactive tutorials and IMHO, if you are not already familiar with the mission editor, it can be hard going.
There were a couple of standalone US and Russian scenarios to play and IIRC a A-10C version but I'm not sure if they've been updated to the 2.5.x map changes.
I played the US scenario once but as there's no way to save, I had to load and fast forward a track and then 'take control' to continue my session a second night.
I think the assumption is players will use time acceleration in the scenarios as ground combat/movement takes much longer than an airstrike, etc.
How do you learn to use it ?• watch a couple of youtube videos/read the manual
• Create a mission with a ground vehicle and some targets
• drive around and shoot stuff up using WSAD, etc. to learn the FC3 like controls
• progress to the included Scenarios to practice controlling AI units pathing, fire position, etc.
-
Carrier ATC is 'work in progress', previously (2.5.3 ?) after your initial 'air boss' contact, Carrier com's progressed automatically depending on your location/distance during the approach phase.
I haven't checked 2.5.4 Open Beta's carrier com's but ATC triggers for taxiway/runway interaction have changed, so it's possible carrier com's have also changed.
-
Is there a key binding I'm missing somewhere? I looked in the control settings and the NS430 is not listed on the drop-down list.
You enable/disable the 2D NS430 for individual modules using 'check boxes' in DCS>Options>Special>NS430
Key combos for the NS430 are defined in DCS>Options>Controls>NS430
• "LShift+LAlt+B" key combo brings up the 2D NS430.
• "LAlt+C" toggles mouse interactivity for FC3 aircraft (so the 2D NS430 can be turned ON, etc.) if needed.
IIRC the 2D NS430 only powers up with the engine running i.e. when sat on the ramp.
-
Just awful ...
Going to have to disagree with you.
I'll continue to recommend this campaign to anyone who buys either the F-86 or MiG-15, as neither come with a default SP campaign and this campaign fills a valuable slot.
-
I have just looked through your track. I can't confirm that airbrake isn't moving.
Same.
Tested DCS World Steam Edition, Open Beta 2.5.4.25729
-
I'm watching a lot a really great tutorials by awesome content creators and I'm watching them pan around the cockpit as a cursor sweeps over or uses a cockpit control.
I seem unable to do that.
Most players use head tracking via TrackIR, VR Headset, etc. - that is most likely what you are seeing.
My mouse has no functionality and when I go to map controls the column for the mouse is not available. It seems I'm limited to the number pad on my keyboard. It's doable but far from optimal.Thank-you in advance for any insights.
The number pad (and joystick hat) are the default controls to slew the camera in a clickable cockpit but you can use the mouse control toggle ("LAlt+C") - to switch between interactive (clickable cockpit switches) and mouse "look" mode i.e. the default Su-25T mode.
-
Can't be right can it now?
TCN in HUD view 20.1nm
"TKR" is activated in 'group' 'action' "ActivateBeacon" at waypoint 0 start
You see the boat at 10 o'clock, that's not 20.1nm ?
Perhaps there's a boat out of view, I swear I Tacan'd Stennis.I'll check
Assuming you've tuned to the Stennis (rather than a tanker), there's a general DCS 2.5.x bug were TACAN distance and direction stop updating after a time.
It's possible you encountered that - turning the TACAN OFF and ON, usually fixes it.
Ref:
F/A-18C specific thread for additional TACAN reports, tracks, etc. https://forums.eagle.ru/showthread.php?t=226304
-
DCS World>Options>Gameplay>Labels=None
or
if labels have been enabled in a mission, they can usually be toggled on or off using "LShift+F10"
https://forums.eagle.ru/showthread.php?p=3283219#post3283219
-
-
Unless things have changed switching to English in settings also removes the metric gauges so you end up with feet and knots.
•Avionics Language = English
enables English cockpit labels.
Whether you have Metric or Imperial gauges is determined by the Global Units setting.
I use the following and it works perfectly, English labels and metric dials :thumbup:GeorgeLKMT's mod forces metric instruments in the L-39 even with the global units set to imperial, so saves switching the default Global Units when switching between 'western' aircraft i.e. A-10, F/A-18, etc. and the L-39 with metric instruments.
-
I couldn't find the Kneeboard files in the DCS folders..
any ideas?
The naming convention for the F/A-18C Hornet Lot 20 kneeboard folder is
• "Saved Games\DCS\Kneeboard\FA-18C_hornet"
you can add kneeboard files for a specific mission by using .7zip, etc. to add kneeboard pages to the .miz file.
• MyMission.miz > "KNEEBOARD\FA-18C_hornet\IMAGES\kneeboard_1.jpg, etc."
-
By distinguishing pulse train characteristics the other bands or modes are filtered out. The whole point of the Y band was to increase the available channels. It would defeat the purpose of the expanded band if e.g. 1X and 1Y would interfere. Similarly A/A and A/G operation doesn't interfere.
Thanks, I wasn't aware of that.
-
A/A TACAN should function for both X and Y for all channels for 252 independent modes of connection.
My understanding was that X and Y shared the same 126 channels, as shown in this diagram
Y band transmit/receive channels overlap with a 63 channel separation and X band wasn't used for A/A.
Do you have a source that contradicts the above ?
-
To ensure the ILS switches direction correctly, have a +7 knot (+3.5 m/s) headwind for the runway you want to use ILS on.
Otherwise the 'active' ATC runway can be out of step with ILS and marker beacon direction for moderate headwinds.
-
Will we get E version?
We get the C version.
From Nov 6th, 2017
Weapons:AGM-88C HARM
AFAIK the main improvement of the D/E model were the addition or improvement of INS/GPS for accurate targeting of emitters that became silent.
The AGM-88D Block 6 HARM
Development effort continues on the HARM design to further refine its capabilities. The greatest weakness of established HARM variants is their inability to accurately home on targets which have ceased to emit. Often the missile may not guide close enough to inflict any useful damage.
The AGM-88D Block 6 variant is intended to eliminate this limitation in the HARM, for range known launches. The Block 6 upgrade is a cooperative German-Italian-USN effort to fit the missile with a precision guidance kit, employing GPS-inertial guidance. The HARM fitted with this kit would fly a much more exact trajectory, using GPS to aid its inertial package, producing some improvement to the missile's existing 50-80 NMI range. Should the emitter be lost, the missile will continue its flight under GPS inertial control to impact. The CEP of the GPS guidance package will be of the order of 20 ft, however the limitation to lethality will be primarily imposed by the accuracy of targeting receiver used to initialise the missile. Since target GPS coordinates for known fixed targets may be determined by other means, the missile has potentially very h
Using the AGM-65F
in DCS: F/A-18C
Posted
I've found the Barometric autopilot harder to engage in Open Beta 2.5.4 but the HUD climb rate is bugged (x2 standby VVI/real value), so perhaps is also effecting the autopilot.
Attitude and heading engagement hasn't changed as far as I can tell, YMMV.