Ramsay
-
Posts
3744 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Ramsay
-
-
Someone correct me if I'm wrong, but isn't that because the TACAN station only provides magnetic heading to aircraft tuned into the channel?
The behaviour is true for a mechanical HSI (i.e. as found in the F-5E) if not correctly aligned with magnetic north.
However, AFAIK for a more sophisticated system as found in the Hornet, switching the HSI to display 'true' bearings, changes the display format, rather than the underlying data (that may be a mix of GPS coordinates, moving map tiles, TACAN station, etc.).
So the TACAN station position on the DDI moving map shouldn't change when the display format (Heading tape, HSI, etc.) is changed from magnetic to true.
-
Trying to sort this mess out...
I have made a set of RSBN charts specifically for the MIG21 (one for each map) extrapolating the RSBN preset numbers directly from the Beacons.lua
Not sure why you'd use beacons.lua, when it's been explained that the MiG-21 uses it's own files - R_NAV_data_Caucasus.lua, etc.
ED's 'beacons.lua' RSBN's are only applicable to the L-39, as previously explained.
I know RSBN discrepancies have cropped up in the past but has this ever been fixed?IIRC, there was discussion of making the MiG-21 compatible with ED's generic beacons.lua map files but it has yet to happen.
-
I tried a number of TACAN flights on my own, I had no issue, can you guys give me your procedures to see if there is something off in that? So far I haven't had any freezes, but I will continue to test tonight.
Although it "can" fault at any time, TACAN usually fails after prolonged use i.e. +40 minutes of being on, tuned to the same station and flying around.
The reason I suffered initially was, I'd startup and tune in the TACAN and spend 20-30 minutes learning the cockpit, writing check lists, etc. before takeoff and the TACAN would often fail 10-20 minutes later.
It rarely gives issues today, as I typically takeoff from a AB, attack a ground target and only later tune to the carrier TACAN to find the carrier group and land.
I've lost TACAN in the Hornet, 7-6 nm from the carrier i.e. it was visual, so it's not a LOS or switch issue.
In the F-5E, I've spent the best part of an hour, dipping in and out of valleys (breaking LOS) and having NO BUG, only to have the TACAN freeze when I was in the 'pattern' and about to turn to the base leg (at the 55 minute mark).
This F/A-18C Tacan track still fails (distance freezes @ 34.1 nm) in Open Beta 2.5.324974 when played at x3
Note: On my system, the TACAN bug fails to reproduce when tracks are replayed at high fast forward speeds i.e. it stopped the TACAN freezing.
-
Any chance this could be explained so I understand this better?
The DDI behaviour matches that of the real Hornet (it's a FAQ and oft miss reported bug).
-
Channels: Are these an invention of DCS, or are they a real thing in the AV-8B?
Yes, channels are a real thing.
Radio channels are setup per briefings, flight plans, SOPs, etc.
AWLS channels are similarly configured but AWLS in the real AV-8B is the same as the Hornets ICLS - not compatible with civilan ILS and used to land on the Tarawa in Case II or Case III landings, etc.
ICLS uses higher radio frequencies and a narrower beam width than "normal" ILS.The AN/SPN-41A Instrument Carrier Landing System is a pulse coded scanning beam (PCSB) emitter that transmits elevation and azimuth guidance signals to appropriately equipped Navy and Marine Corps aircraft.The AN/SPN-41A radiates two coded microwave beams into the approach volume behind the ship.
The signal coverage from each beam is approximately 20-degrees to either side of centerline and 0 to 10-degrees above the horizon for a range of 50 miles
It is not compatible with ILS as found at Batumi, Kobuleti, etc. so you won't get localiser or glide slope indications.
What really has me asking this question, is that it seems so completely ridiculous to store every piece of information, except the runway heading. Or am I missing something?AFAIK the 'real' AV-8B has a +200 point data library that is used to store GPS coordinates for Nav aids, divert airfields, etc. and the info can be copied/pasted to tactical waypoints if needed.
I don't think the AV-8B MPCD pages have a 'divert' page like the A-10C that lists all the nearby airfield information, if that's what you are expecting.
-
Aircav1980 said:I have been trying to practice engagements with the Aim-120 and Aim-7 missiles. I follow the tutorials by setting up the target size and cross section size. I have the Aim-120s in visual mode but no matter how close I have my F/A-18C nothing ever shows up on the attack radar for me to lock.
IIRC, when you select AIM-120's the radar default is 2 bar/140°, which covers about 10,000 ft at 40 nm i.e. 22,000 - 32,000 ft
At closer ranges, the scanned altitude narrows i.e. 5,000 ft @ 20nm, 2,500 ft @ 10 nm, etc. and it becomes even easier to miss targets.
To avoid this I change to a 4 or 6 bar scan to cover a wider range of altitude, while narrowing the scan width to 80° as AWACS usually gives a good indication of azimuth.
I attach a practice mission that spawns a couple of hostiles (F-5E's with guns, L-39ZA with R60 Aphid or C-101CC with guns + IR) to practice with. AWACS is on 251 MHz.
There's a Tu-142 at distance to practice longer range detection. Detection range is approx. 26 NM for the L-39ZA and 118 NM for the Tu-142.
-
I saw a big difference between the HUD heading and the radar heading today. Something's definitely gakked up there. Never really looked at radar heading before, though, so it may have always been that way.
HUD is magnetic by default. Radar is true. AFAIK it's been that way for a while (since release ? ).
-
I tried with JsGme. No Joy, can you tell what directory you installed JsGme? Im running the steam version.
Tested the first TopGun mission in Steam without issue, perhaps this will help ?
The directories I installed to were
"Saved Games\DCS\Mods\tech\US Navy Equipment"
"Saved Games\DCS\Missions\Campaigns\en\FA-18C TopGun by florenceSSD"
Tested DCS World Steam Edition [openbeta] 2.5.3.24436
Ok got it working after making a mod\tech folder because it didnt have any & extracting the files directly to the mods\tech folder.Cool, glad you've got it sorted.
-
The planes, maps, DLC campaigns, etc. get updated along with the main install when there is an update.
One week the Open Beta gets updated (main game plus modules - AV-8B, F-18, Persian Gulf, etc.), approx. a week later if there haven't been major issues - it gets pushed to the 'Stable' branch i.e. Open Beta and release are on the same version.
https://forums.eagle.ru/showpost.php?p=3575286&postcount=1
There have been 3 Open Beta updates this cycle and we expect another this week due to various issues.
Currently
• Stable is 2.5.3.23225 (2018-10-31)
• Open Beta is 2.5.3.24436 (2018-11-21)
https://forums.eagle.ru/showpost.php?p=2249076&postcount=2
The default Steam install is 'Stable', however you can opt into the 2.5 Open Beta via "Steam>DCS World Steam Edition>Properties>Betas>openbeta-Public beta versions"
Updates usually get pushed to Steam within 24hrs of the stand-alone.
-
Next, will the GBU-24 ever get fixed? It still has a low-res model and doesnt follow laser guidance.
... I know Razbam isnt responsible for the GBUs, but does anyone here know if some officials have ever made a little statement about these in the last time?
AFAIK the GBU-24 is due a update after the implimentation of GBU-10, GBU-12, and GBU-16 for the Hornet.
We will later add the GBU-24, but this requires some additional work as it has some significant differences from GBU-10/12/16.The Paveway III, GBU-24 uses proportional steering and it looks like ED want to model that, rather than "copy and paste" the Paveway II code.
-
When I actually do the -2 trim I can barely rotate off the ground at the nras.
Not sure what you mean by "I can barely rotate off the ground at the nras.", at NRAS, you rotate the nozzles (not the aircraft nose) and it should lift off the runway (with the witch's hat more or less on the horizon, and FPM at 4-6° on the pitch ladder). If the Stab is set wrong, the nose will try to pitch down/up and need pilot input/trimming.
Once I am able to get it off the ground it’s a constant battle to clean up to wingborne flight and trim out the forces.I usually set | 1° | less than the real, so set -1° Stab for takeoff. The aircraft has small upward pitch moment that needs to be controlled as the gear is retracted and nozzles rotated back to 25° before switching to Auto flaps, and continuing the nozzle rotation to 0°
Okay. Last time I did that, the jet just bounced down the runway and eventually broke.What was your weight ? was this with 10° nozzles for the takeoff roll ? What RPM, 103% is sufficient in most cases.
I even use the VREST data to determine NRAS and noz angle.The VREST>STO page is likely WIP, most info is correct but nozzle angle is not !, IIRC I've only seen 60°
The STO nozzle angle is approx.
• 60° (25,000lb or less),
• 55° (26,000-29,000 lb)
• 50° (30,000 lb or above)
Ref: Figure 3-14. Short Takeoff Rotation Speed, STOL Flaps (Sheet 2 of 2), p73, NATOPS Flight Manual AV-8B Performance Charts, A1-AV8BB-NFM-400
The chart on page 70 of Chuck's AV-8B Guide is for the 406 engine but close enough.
I mostly set nozzle stop to 55°
Use STO flaps. Most of the time I do dry TO unless I absolutely have to do wetI'm the same, without a track, it's hard to see the details of why you are having issues but I can list my STO sequence
VREST>STO page• NRAS wet 93kts dry 102kts -->NRAS approx 100 KTAS
• GWT approx. 26700 lbs
On Runway
• Nozzles set @ 10°
• Nozzle Stop @ 55°
• Flaps to STO
• Stab set to -1° (set to -2° then inc to -1°)
• Water to TO (Take Off)
• Wheel brakes ON
• Throttle up to 80% RPM
• Wheel brakes OFF
• as speed increases, increase the Throttle to 103% RPM
• @ approx 100 KTAS - Rotate Nozzles to Stop (55°)
Once Airborne
• Witch's hat maintained near horizon +/- 2°
• Gear UP
• Nozzles slowly to 25° (controls FPM climbing the pitch ladder)
• When nozzles reach 25°, Flaps to AUTO
• Continue rotating nozzles to 0°
• Adjust Trim as necessary
Takeoff checklist
• Clear Nozzle Stop
• Water OFF
Continue Climb adjusting throttle/trim as req'ed.
Here's a track, it's not very good as I rotate the nozzles late (+114 KTAS) but it may be of use ?
-
You should even find the correct approach pattern to the runway in the kneeboard.
Not for IFR approaches (the diagrams in the kneeboard are VAD's = Visual Approach Diagrams), however the diagrams do include runway headings (magnetic), etc.
-
Is Link 16 and/or SA similar to AWACS' PICTURE request?
Sort of, I haven't read up on the Hornet and Link 16, as it's classified, I'm not sure how much is/can be modelled in DCS and there seem to be numerous versions/upgrades.
AFAIK :
Link 16 is the data protocol (like the A-10C's SADL) that's lets information be shared i.e. your GPS position, a air or ground target, waypoint/markpoint, etc.
The SA page (a little like the HSI/moving map) is on the Hornet's DDI and where the data is displayed graphically. Not only will it display the position of targets locked by yourself but also also contacts/threats shared by wingmen or AWACS on the same NET.
This means that with Radar silent, you'll still have SA of any contacts ahead being tracked by AWACS or if you need to 'reset' and put a bandit on your six (to disengage), you keep SA as long as the bandit is being tracked by AWACS, etc.
-
Video is not working...
-
-
Memory I can easily over come, but is that going to help - from what ive read on the forum - not really
To run the Persian Gulf you really want more than 8GB RAM.
For loading times, it depends what you are seeing
+5 min loads can be improved by adding a newer/faster HD
+2 min loads - is pretty normal, as the bottle neck switches from the HD transfer rate to the speed your CPU can unpack files/textures, etc.
SSD is a worth while investment - it reduced stutters/lags a little but didn't do much for map loads as I was already using a fast 4TB HD
My old i7@2.8GHz has trouble with lots of AI (+40), so MP servers are off limits (<25 fps) but it's good enough for SP and coop with my son.
My Specs:
i7 860 @2.8GHz , 12GB DDR3 , GTX1050Ti 4GB, 1TB SSD, 4+2TB HD, MSFFB2 joystick, X52 Pro Thottle, TIR5, Win 10 Pro x64, 1920X1080
YMMV
-
TL;DR:
You're encountering bugs in DCS 2.5.x
• TACAN/RSBN isn't always blocked by line of sight
• The ATC active runway and ILS/PRMG and inner/outer markers aren't always in step for moderate headwinds
Detail:
i was over 200km away from Mozdok and behind the Caucasus mountains ...the RSBN and the distance counter has contact to Mozdok ... really true ?
I often picked up 'phantom' TACAN signals the wrong side of the Caucasus mountains, I guess the RSBN signal uses the same line of sight code and suffers the same issues.
... but my problem was at the landing on Mozdok.Mozdok ATC gave advice for RWY 08 ...
but i could not get any landing information ...
later ... i try the other RWY 26 ...
And for my surprise the RSBN PRGM works fine ...
ATC active runway and ILS/PRMG and inner/outer markers aren't always in step for moderate headwinds
in mission i have set wind direction from north east to south west 4kn ...RWY 08 should be the right runway ...
A 4 knot headwind (2 m/s) isn't sufficient to keep ATC and ILS/PRMG in step (usually around 3.5 m/s).
Testing in DCS Open Beta 2.5.3.24436, 7 knots to 225°T, was and ATC RWY 08's inner/outer markers and PRMG were active.
-
Unfortunately, after five hours of going through checklists, following YouTube videos and even praying to some sort of winged god, I can't even get them to launch.
A track file would help us, help you ?
-
I know it’s early access, but I can’t see anything in BVR on the attack radar. Have all the systems on. Mainly having the issue with standard settings on Aim 120c.
Any ideas?
IIRC after selecting the AIM-120C, the radar defaults to 2 bar and 40 nm, I usually increase to 4 or 6 bars so the radar covers a wider altitude.
-
Yes, DCS 1.5.x will run under Windows 10 ( I currently run 3 installs - 1.2.16, 1.5.6 and 2.5.3 Open Beta)
One thing to be aware of is - the latest versions of Tacview aren't compatible with older versions of DCS, so Tacview needs to be removed from "Saved Games\DCS" folders of earlier versions, otherwise the older DCS versions will fail to run.
Perhaps you have other mods installed that are causing issues, so try rename "Save Games\DCS" and let 1.5 build a new folder ?
YMMV
-
Thanks, the mix of theory with a follow on example in DCS, really helped understand the concept and taught me a lot.
To test my understanding, I recreated your example mission with a MiG-29 "drone" and several F-18C air spawns that approached at different Target Aspects to put theory and example into practice.
I was surprised how fast the intercept progressed but it went well and I later used the concept to join up with a AWACS I'd also added to the mission.
Might be useful to include a simple mission file for those less familiar with the ME.
-
What are the actual keyboard keystrokes for nozzle swiveling angle so I can use them on my CH? I've looked on the control pages on DCS but didn't see them...maybe I missed it...
• Nozzle Rotation UP = "LShift + Num+"
• Nozzle Rotation Down = "LShift + Num-"
-
Was it once pointed out anywhere in this thread that mavs will not uncage if ream using single stores? Alot of us play MP with the AV8. This might help others.
Rearming AGM-65G's used to work in MP, main issue was the IRMV status was wrongly displayed on the stores page as RDY "Ready" after a reload, when the new loadout still needed it's 3 minute cool down.
IIRC deselecting the IRMV on the stores page reset it's status, so when selected again, "stand by" STBY showed and the 3 minute cooling cycle started. IRMV status would then switch to RDY, 3 minutes later and IRMV's could be uncaged, etc.
I haven't tested Open Beta 2.5.3.24436 though.
-
Am hoping to pick up this module during the 1/2 sale. Can I be assured it will run on my stable-only version of DCS World
The Yak-52 was introduced with DCS 2.5.2.20143 (release), so it's available to fly in the existing DCS 2.5.3 release branch (as is the Hornet).
... since the description doesn't include "early access" like the Hornet and now Tomcat, etc.???Note: The Yak-52 still needs a 'little' work 'here and there' i.e. the HSI ADF needle doesn't work, it lacks default skins (bare metal other than for Russia) and there are a couple of issues reported in the bug section.
First Impressions Review:
TL;DR:A good module but due to it's limited use in DCS, buy in a sale.
Detail:
+ A well made module
+ good soundscape (creaks and squeeks as it bounces along the taxi way, etc.)
+ good flight model
- very basic instruments, so no night flights/IFR
• metric instruments (- if you're used to knots/ft)
- no combat capability
+ good for basic instruction, aerobatics and formation flying with a friend
• multicrew compatible if both players own the module
+ easy to fly if you've already learn't the free TF-51D or flown the Spitfire, etc.
+/- it's slow (210km/h (114knots) @ 500m (1640ft)), which is a pain but also makes it great for low level sight seeing.
• produced for a private contract with permission to sell to the public.
Cons:
- 3 training missions and an average of 4 Instant Action Missions per map, so you'll want to learn the Mission Editor, etc
- ADF doesn't work on the HSI but is work in progress
- Very limited number of 'skins' and only for Russia, there's handfull of user files uploaded but ED should have included at least one (fictional ?) US skin for BLUFOR (or made the Russian skins available for all countries) IMHO
- It doesn't really fit with the rest of DCS (can't spot/mark targets, etc) and the free TF-51D is 'better' in most respects
Buy in a sale, as a 2nd or 3rd module for something a little different, that doesn't cost 'too much'
RSBN Channels (+1 again)...
in MiG-21Bis
Posted · Edited by Ramsay
spelling
IIRC RSBN, TACAN, PMRG and ILS weren't differentiated, with RED/BLUE FC3 aircraft using a common system.
The MiG-21 was coded with it's own RSBN/PMRG beacons/data (2014).
ED then differentiated FC3 systems and the Su-25T could no longer land using western ILS's and RSBN/PMRG refined further for the L-39 release (2015).
It wasn't