Ramsay
-
Posts
3743 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Ramsay
-
-
1 hour ago, C525 said:
I took the time to create VFR Approach and Departure Charts for the airfields I use the most.
Thanks for sharing your work.
Looks like there may be error on the Buchel (ETSB) Chart for the "ENTRY WEST" Radial i.e. "R-010/15" is the same as ENTRY NORTH.
-
5 hours ago, RogueRunner said:
Also Sperenberg RSBN (ch 28 per F10) for me (mig21) did not work at all.
The MiG-21 doesn't use the Cold War Germany "beacon.lua", it uses it's own definitions files and requires a user mod.
-
1
-
-
On 6/23/2025 at 11:44 AM, zsoltfireman said:
Ticked no change
Other maps work without a tickThe default "MiG-15bis - GermanyCW - Free Flight.miz" mission (GDR REDFOR) is set on 16th August 1990, so before the full GPS Satellite Constellation was in orbit/operational (March 28th 1994 in DCS).
With ...
1. Mission date adjusted to 16th August 1994 and
2. Options>Gameplay --> Unrestricted SATNAV = CHECKED... the NS430 popup worked as expected.
-
1
-
-
4 hours ago, clanitho said:
I had DCS crashes due to insufficient memory ... after setting a 32 GB pagefile, the errors stopped.
This is common/normal behaviour due to how DCS and Windows interact if Windows is allowed to automatically manage virtual memory.
Hence this DCS recommendation :-
QuoteDCS crashes and doesn't work
Some IMPORTANT notes !
6. It's important to set the Windows page file to a system managed size or a custom size to 16 - 32 GB or more
find more information on the website https://www.thewindowsclub.com/increase-page-file-size-virtual-memory-windowshttps://www.digitalcombatsimulator.com/en/support/faq/startup/
Quote32 GB (or equal to RAM):
A page file size equal to or slightly larger than your physical RAM is often recommended to avoid potential memory issues during DCS sessions, particularly when using high-fidelity aircraft and maps.Fast drive:
The page file should be placed on a fast SSD to minimize access times and reduce performance bottlenecks.-
1
-
-
4 hours ago, Nealius said:
Will test with other wind directions.
Just did a quick check - there's nothing fancy (or relative) here, it's just wrong.
• wind to 90° is reported as 270° (correct)
• wind to 118° is reported as 242° (wrong i.e. 118 + 180 = 298)
• wind to 45° is reported as 315° (wrong i.e. 45 + 180 = 225)
Looks like it was pure chance the Airboss's relative wind bearing of 242° in the OP's mission was in the same quadrant as the actual "relative wind" !!!
-
1 hour ago, Nealius said:
My question is, though, how is wind changing mid-mission?
Apparent wind:
Apparent wind is the wind experienced by a moving object, like a sailboat or an aircraft, and is a combination of the true wind and the object's speed and direction.
Relative wind is the direction of the airflow relative to the moving object (carrier), rather than the true wind direction.
Comment:
AFAIK the Airboss screen's "relative wind" direction is only calculated at mission start and doesn't update when changing the carrier's speed/direction or switching to a new player slot.
The magnitude of the Airboss's "relative wind" only considers the metrological wind component (perhaps adjusted for deck height) and doesn't include the additional component due to the carrier's own speed/direction.
1 hour ago, Nealius said:To my knowledge there is no way to change wind direction/speed mid-mission.
Dynamic weather adds cyclone type weather systems to DCS and metrological wind direction and speed can/will vary with the carrier's location i.e.
-
21 minutes ago, Nealius said:
Wind is showing as "to" instead of "from," like in the mission editor wind settings.
This is incorrect.
The "Relative Wind" direction shown in the bottom left appears to be calculated at mission start? and won't necessarily be the metrological to/from direction i.e. the OP's mission has a 12 kts wind towards 188°T, yet the Airboss screen shows the direction as 242°
-
29 minutes ago, AndyJWest said:
Wind speed and direction can vary with altitude.
Yes, in this test mission 12 kts @ 33ft increases to 25 kts @ 1600ft (and I'm guessing the 72 ft deck height is responsible for the increase to 14 kt in DCS).
-
3 hours ago, Solo_Turk said:
If the mission had dynamic weather and changing wind speed-direction, what would we do?
Unfortunately the Relative Wind direction and magnitude on the Airboss's screen doesn't update when changing the carriers speed or direction - so even if you bring the carrier to a full stop, you can't see the meteorological wind across the deck.
Here, I've turned the carrier into the meteorological wind and adjusted the course so the crosswind needle is centered i.e. at 0 kts
... this is far from ideal, but I'm at a loss for what else you can do if the briefed wind direction changes and isn't updated in the mission brief (LALT+B).
-
25 minutes ago, Solo_Turk said:
So, what is 242 for?
It's the relative wind across the carrier deck i.e. a helicopter taking off into a hover or flying parallel, would fly 242° at 28 knots to remain stationary relative to the moving carrier.
The relative wind across the deck is dynamic and will change with changes to carrier's speed/direction.
The meteorological wind is usually static (in DCS) and/or slow to change - so matches the mission briefing.25 minutes ago, Solo_Turk said:"how am I suppose to know what course I should turn the ship to have zero crosswind on landing area?"
Not sure on the exact maths but I'd turn the carrier into the meteorological wind (305°T) and add a "fudge" factor to compensate for the angled deck, OTOH in DCS I general consider "into the wind" close enough when making missions.
-
14 minutes ago, Nealius said:
Natural wind direction would be 298.
Is that what is/should be displayed at the Airboss's "station ?
Do you have a real life example/link for US carrier operations you can share ?
-
11 hours ago, Solo_Turk said:
In this mission, wind blows to 118. So, on airboss screen it should be 118 or 298(idk which one is used irl, probably "from 298"). However, the screen shows 242. When I turned the ship to 242, crosswind wasn't 0.
Not sure if everything is reported correctly on the "Airboss's Windspeed/Direction Screen" but neither 118° or 298° is close to the resultant wind across the deck due to the carrier's speed/direction combined with the meteorological wind in the mission.
This diagram might help ?
Comment
ARCTAN (25/13) = ~62° so the wind direction from 242° in DCS is perhaps derived from the "measured ?" landing deck headwind/ crosswind components (and ED are modelling real life rounding errors, instrument limitations or similar ?)
However, the magnitude (14 kts) of the wind doesn't make sense (to my eyes) as (from Pythagoras theorem) the landing deck wind components equal 28 knots i.e.
• √ ( 25² + 13² ) = √ ( 625 + 169 ) = √ ( 794 ) = 28 kts
but perhaps I'm misunderstanding what is being displayed in the bottom left of the Airboss's screen ?
-
On 5/24/2025 at 6:48 PM, bmbpdk said:
Can i ask you how you got the Kiowa MFD´s exported to your Winwing MFD´s?
The Kiowa MFD's (LEFT_MFCD and RIGHT_MFCD) will export (with a stretched ratio) using most? SimAppPro display profiles i.e. A-10C, F-16C, F/A-18C or similar.
TL;DR:
https://forum.dcs.world/topic/371974-radar-on-an-mfd/#findComment-5632094
Detail:
Here is a Kiowa example using the WinWing F/A-18C profile.
Monitor setup
F/A-18C Cockpit Profile (CENTER_MFCD, LEFT_MFCD and RIGHT_MFCD)
DCS Kiowa export to WinWing MFD's
Copying WinWing's Export .lua ("DCS World\Config\MonitorSetup\wwtMonitor.lua") to "Saved Games\DCS\Config\MonitorSetup", allows the exported displays to be adjusted to a 3:4 ratio (the HSI, etc. isn't stretched but instead has black bars top and bottom).
Custom Export .lua (positions require adjusting to fit your own monitor resolutions/arrangement)
_ = function(p) return p; end; name = _('OH-58D_3xMFD_4x3_Aspect'); Description = 'Custom positions and sizes for 3x Winwing MFD.' --created 2025-04-10, Exported Displays given 4x3 Aspect, RB Viewports = { Center = { x = 0; y = 0; width = 5120; height = 1440; aspect = 3.5555555555555554; --32/9 } } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center --L2MUMS is mapped to CENTER_MFCD (and permamently displayed) CENTER_MFCD = { x = 8; -- 0+8 offset y = 1794; -- 1440+256 offset +20 for Kiowa +78 to centre width = 752; -- 768 - (8+8) height = 576; -- 4x3 aspect for Kiowa (was 732) } --Custom MFD sizes and positions to fit inside button bevels. LEFT_MFCD = { x = 776; --768+8 offset y = 1794; -- 1440+256 offset +20 for Kiowa +78 to centre width = 752; -- 768 - (8+8) height = 576; -- 4x3 aspect for Kiowa (was 732) } RIGHT_MFCD = { x = 1544; --(768x2)+8 offset y = 1794; -- 1440+256 offset +20 for Kiowa +78 to centre width = 752; -- 768 - (8+8) height = 576; -- 4x3 aspect for Kiowa (was 732) }
More detail on viewport exporting can be found in this excellent Export FAQ
-
1
-
1
-
-
12 hours ago, grim_reaper68 said:
As told, there is no runway inversion, but the Localiser needle is on the wrong side. I repaired DCS to be sure to have the original file, and the issue is here.
Sorry if I wasn't clear in my feedback, I wasn't seen the the inverted F-16 localiser when using a modified beacon.lua file.
10 hours ago, grim_reaper68 said:So to correct that, ILS loc and GS frequencies should be corrected as in the file joined, same for the directions.
Thanks, I'll copy and paste your changes to my copy to fix the non-working glide slope on 25L.
-
18 hours ago, grim_reaper68 said:
Second thing: the localiser on the same runway is inverted too.
When the localiser is "inverted" in the F-16C - it means you are flying a "back course" i.e. the wrong localiser direction is activated.
This is similar to when the glide slope is "missing" and only appears after overflying the far end of the runway.
Although I don't have "inverted" localisers for 25R and 25L, I'm still working out how to configure a working glide slope for 25L (wrong end/frequency is activated) - so cannot offer a comprehensive Frankfurt config yet.
-
13 hours ago, MAXsenna said:
The DCS.log would be nice.
Attached are two of my own (the zip includes a track file).
A few common lines in the log prior to the CTD.
2025-05-24 01:44:27.458 WARNING EFFECTS2 (Main): OParticleSystem: preset 'missile' not found in 'volumetricPointLight.lua', using default 2025-05-24 01:47:19.786 WARNING LOG (9368): 20 duplicate message(s) skipped. 2025-05-24 01:47:19.786 ERROR GRAPHICSVISTA (Main): Can't open model AV-8BNA-OBLOMOK-ELEVATOR-L. 2025-05-24 01:47:19.787 ERROR GRAPHICSVISTA (Main): Can't open model AV-8BNA-OBLOMOK-ELEVATOR-R. 2025-05-24 01:48:14.306 INFO EDCORE (Main): try to write dump information 2025-05-24 01:48:14.641 INFO EDCORE (Main): # -------------- 20250524-014815 -------------- 2025-05-24 01:48:14.642 INFO EDCORE (Main): DCS/2.9.16.10523 (x86_64; MT; Windows NT 10.0.26100) 2025-05-24 01:48:14.643 INFO EDCORE (Main): H:\Steam Library NVMe\steamapps\common\DCSWorld\bin\DCS.exe 2025-05-24 01:48:14.644 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff6cb3836f3 00:00000000 2025-05-24 01:48:14.645 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'H:\Steam Library NVMe\steamapps\common\DCSWorld\bin;', symOptions: 532, UserName: 'Ramsay' 2025-05-24 01:48:14.646 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x100-0x1 2025-05-24 01:48:14.647 INFO EDCORE (Main): 0x00000000007b36f3 (DCS): SW + 0x19BC73 2025-05-24 01:48:14.648 INFO EDCORE (Main): 0x000000000078bd6a (DCS): SW + 0x1742EA 2025-05-24 01:48:14.649 INFO EDCORE (Main): 0x000000000071285f (DCS): SW + 0xFADDF 2025-05-24 01:48:14.650 INFO EDCORE (Main): 0x000000000000461b (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB 2025-05-24 01:48:14.651 INFO EDCORE (Main): 0x0000000000004c42 (World): wSimCalendar::DoActionsUntil + 0x262 2025-05-24 01:48:14.651 INFO EDCORE (Main): 0x0000000000a4eeba (DCS): SW + 0x43743A 2025-05-24 01:48:14.651 INFO EDCORE (Main): 0x0000000000a4eb91 (DCS): SW + 0x437111 2025-05-24 01:48:14.651 INFO EDCORE (Main): 0x0000000000a74032 (DCS): SW + 0x45C5B2 2025-05-24 01:48:14.651 INFO EDCORE (Main): 0x0000000000a28d04 (DCS): SW + 0x411284 2025-05-24 01:48:14.651 INFO EDCORE (Main): 0x0000000000a2a3c3 (DCS): SW + 0x412943 2025-05-24 01:48:14.652 INFO EDCORE (Main): 0x00000000025abc5f (DCS): AmdPowerXpressRequestHighPerformance + 0x10C0C5B 2025-05-24 01:48:14.652 INFO EDCORE (Main): 0x00000000010ad99e (DCS): SW + 0xA95F1E 2025-05-24 01:48:14.652 INFO EDCORE (Main): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17 2025-05-24 01:48:15.413 INFO EDCORE (Main): Minidump created. 2025-05-24 01:48:15.413 INFO Lua::Config (Main): stack traceback: 2025-05-24 01:48:15.419 WARNING LOG (9368): 3 duplicate message(s) skipped.I tested the original Portuguese .miz and also an edited version with English text - the track file has a lot of wasted time (on the runway) as I refamiliarised myself with the JF-17 / assigned control bindings, however it does CTD on replay in the current version of DCS 2.9.16.10523, so should serve it's purpose.
Looks like the CTD may be related to the HQ-7 shooting down an AI AV-8B ?
-
On 5/19/2025 at 1:21 AM, CommandT said:
Am I right in saying we currently do not have a Tacview map for CWG? Or is there a way of getting it to show in Tacview somehow?
Tacview 1.9.5 Beta 8 has added support for CWG, however you'll need to be licenced/registered user to run it (or else wait for the update to come to the open/free branch).
-
1
-
-
52 minutes ago, scommander2 said:
The recent release has shipped the latest DLSS, why the "DLSS_Preset" option is required in autoexec.cfg?
Because by default DCS will use "Preset C" i.e. the older, more performant CNN (Convolutional Neural Network) mode.
Detail
DLSS 4 has advantages and disadvantages. It is not a "no cost" upgrade for all graphics/stuations (yet?) i.e. temporal artifacts/ghosting. Choosing the "best model" is often a matter of personal opinion.
DLSS 4 looks better in certain circumstances but has a negative impact on fps - this can be offset by choosing a lower quality upscale i.e. DLSS 4 Balanced -> DLSS 3 Quality, however this can have negative effect on MFD text, etc. in DCS and require tweaking using "sharpening" or similar effects.
17 minutes ago, scommander2 said:So, it is more for the backward support...
IMHO rather for user preference, improvements to temporal artificing in DCS with DLSS 4 - often seem to be a placebo effect, rather than "real".
Nvidia continue to improve DLSS Super Resolution, so the "preset" default may change once ED feel DLSS 4 has "matured".
-
3
-
-
46 minutes ago, Silver_Dragon said:
Mig-29A has only capable to dump bomb and rockets. The ED module has none guided ordenance.
Correct, nether I or the ED store quote I made say the MiG-29A carries guided A2G weapons "the [DCS] MiG-29A is also armed with ... a 30mm cannon, and unguided bombs and rockets."
-
1
-
-
20 minutes ago, Mad Dog 762 said:
What kind of air to ground weapons is it able to carry?
From the first lines of the store page -
QuoteIn addition to the R-73 and HMS, the MiG-29A is also armed with medium-range radar-guided missiles, a 30mm cannon, and unguided bombs and rockets.
https://www.digitalcombatsimulator.com/en/shop/modules/fulcrum/
-
1 hour ago, Dangerzone said:
I used the option to display information when running NVCleanstall to update my driver (which has an option to show the information in game).
This is how I also see which DLSS I am using.
1 hour ago, Dangerzone said:I was choosing preset-K in the inspector, but it's showing as C in DCS.
Which Nvidia driver are you using ? Did you re-apply the Nvidia Inspector changes if/when updating the driver ?
This still works for me with an RTX 4070 using Nvidia Geforce 576.28, DCS 2.9.15 and NV-Profile-Inspector-Revamped 2.4.2.3
-
2
-
-
19 hours ago, grim_reaper68 said:
I'm unaware about using scripts, maybe you can explain me or send me a mission where it's used, so I could try to use it on CWG.
@Stehas78 I managed to create a script to log all the Cold War Germany Airfield ID's
Spoiler2025-05-18 07:05:13.145 INFO SCRIPTING (Main): There are 201 getAirbases in the World
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 1 getID = 1 getName = Wittstock
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 2 getID = 2 getName = Altes Lager
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 3 getID = 3 getName = Barth
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 4 getID = 4 getName = Zerbst
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 5 getID = 5 getName = Bremen
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 6 getID = 6 getName = Briest
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 7 getID = 7 getName = Buckeburg
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 8 getID = 8 getName = Celle
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 9 getID = 9 getName = Cochstedt
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 10 getID = 10 getName = Damgarten
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 11 getID = 11 getName = Fassberg
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 12 getID = 12 getName = Finow
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 13 getID = 13 getName = Garz
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 14 getID = 14 getName = Gatow
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 15 getID = 15 getName = Templin
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 16 getID = 16 getName = Gutersloh
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 17 getID = 17 getName = Hamburg
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 18 getID = 18 getName = Hamburg Finkenwerder
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 19 getID = 19 getName = Hannover
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 20 getID = 20 getName = Laage
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 21 getID = 21 getName = Larz
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 22 getID = 22 getName = Mahlwinkel
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 23 getID = 23 getName = Neubrandenburg
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 24 getID = 24 getName = Neuruppin
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 25 getID = 25 getName = Peenemunde
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 26 getID = 26 getName = Schonefeld
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 27 getID = 27 getName = Stendal
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 28 getID = 28 getName = Tegel
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 29 getID = 29 getName = Tempelhof
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 30 getID = 30 getName = Tutow
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 31 getID = 31 getName = Werneuchen
2025-05-18 07:05:13.145 INFO SCRIPTING (Main): World Index = 32 getID = 32 getName = Wunstorf
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 33 getID = 53 getName = H FRG 01
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 34 getID = 54 getName = H FRG 02
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 35 getID = 55 getName = H FRG 03
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 36 getID = 56 getName = H FRG 04
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 37 getID = 57 getName = H FRG 05
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 38 getID = 58 getName = H FRG 06
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 39 getID = 59 getName = H FRG 07
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 40 getID = 60 getName = H FRG 08
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 41 getID = 61 getName = H FRG 09
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 42 getID = 62 getName = H FRG 10
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 43 getID = 64 getName = H FRG 12
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 44 getID = 65 getName = H FRG 13
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 45 getID = 66 getName = H FRG 14
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 46 getID = 67 getName = H GDR 01
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 47 getID = 68 getName = H GDR 02
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 48 getID = 69 getName = H GDR 03
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 49 getID = 70 getName = H GDR 04
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 50 getID = 71 getName = H GDR 05
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 51 getID = 72 getName = H GDR 06
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 52 getID = 73 getName = H GDR 07
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 53 getID = 74 getName = H GDR 08
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 54 getID = 75 getName = H GDR 09
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 55 getID = 76 getName = H GDR 10
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 56 getID = 77 getName = H GDR 11
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 57 getID = 78 getName = H FRG 15
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 58 getID = 80 getName = Gross Mohrdorf
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 59 getID = 81 getName = Lubeck
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 60 getID = 82 getName = Kothen
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 61 getID = 83 getName = Dessau
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 62 getID = 84 getName = Parchim
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 63 getID = 85 getName = H GDR 12
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 64 getID = 86 getName = Uetersen
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 65 getID = 89 getName = Luneburg
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 66 getID = 90 getName = Northeim
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 67 getID = 91 getName = H GDR 13
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 68 getID = 92 getName = H GDR 14
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 69 getID = 93 getName = H GDR 15
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 70 getID = 94 getName = H GDR 16
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 71 getID = 95 getName = H GDR 17
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 72 getID = 96 getName = H FRG 16
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 73 getID = 97 getName = H FRG 17
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 74 getID = 98 getName = H FRG 18
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 75 getID = 99 getName = H FRG 19
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 76 getID = 100 getName = H FRG 11
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 77 getID = 101 getName = Sperenberg
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 78 getID = 102 getName = Uelzen
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 79 getID = 103 getName = Dedelow
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 80 getID = 104 getName = Kammermark
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 81 getID = 106 getName = Weser Wumme
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 82 getID = 107 getName = Braunschweig
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 83 getID = 108 getName = Wismar
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 84 getID = 109 getName = Waren Vielist
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 85 getID = 110 getName = Bienenfarm
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 86 getID = 111 getName = Pinnow
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 87 getID = 112 getName = Gardelegen
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 88 getID = 113 getName = Glindbruchkippe
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 89 getID = 114 getName = Ummern
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 90 getID = 115 getName = Hildesheim
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 91 getID = 116 getName = Verden-Scharnhorst
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 92 getID = 117 getName = Rinteln
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 93 getID = 118 getName = Holzdorf
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 94 getID = 119 getName = H Med GDR 01
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 95 getID = 120 getName = H Med GDR 02
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 96 getID = 121 getName = H Med GDR 03
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 97 getID = 122 getName = H GDR 33
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 98 getID = 123 getName = Airracing Koblenz
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 99 getID = 124 getName = H GDR 34
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 100 getID = 126 getName = H Med GDR 08
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 101 getID = 127 getName = H Med GDR 09
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 102 getID = 128 getName = H Med GDR 10
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 103 getID = 129 getName = H Med FRG 01
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 104 getID = 130 getName = H Med FRG 02
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 105 getID = 132 getName = H Med FRG 04
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 106 getID = 134 getName = H Med FRG 06
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 107 getID = 139 getName = H Med FRG 11
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 108 getID = 140 getName = Hasselfelde
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 109 getID = 141 getName = Grosse Wiese
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 110 getID = 142 getName = H GDR 18
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 111 getID = 143 getName = H FRG 20
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 112 getID = 144 getName = H Med FRG 12
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 113 getID = 145 getName = H GDR 19
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 114 getID = 146 getName = H GDR 30
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 115 getID = 147 getName = H Med GDR 11
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 116 getID = 148 getName = H FRG 21
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 117 getID = 149 getName = H FRG 50
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 118 getID = 150 getName = H FRG 23
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 119 getID = 151 getName = H FRG 39
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 120 getID = 152 getName = H GDR 21
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 121 getID = 153 getName = H GDR 22
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 122 getID = 154 getName = Fritzlar
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 123 getID = 155 getName = Hahn
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 124 getID = 156 getName = Sembach
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 125 getID = 157 getName = Allstedt
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 126 getID = 158 getName = Zweibrucken
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 127 getID = 159 getName = Giebelstadt
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 128 getID = 160 getName = Schweinfurt
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 129 getID = 161 getName = Haina
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 130 getID = 162 getName = Spangdahlem
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 131 getID = 163 getName = Frankfurt
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 132 getID = 164 getName = Bindersleben
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 133 getID = 165 getName = Ramstein
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 134 getID = 166 getName = Fulda
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 135 getID = 167 getName = Obermehler Schlotheim
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 136 getID = 168 getName = Mendig
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 137 getID = 169 getName = Merseburg
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 138 getID = 170 getName = Wiesbaden
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 139 getID = 171 getName = Leipzig Halle
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 140 getID = 180 getName = H Med GDR 12
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 141 getID = 181 getName = H Med GDR 13
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 142 getID = 182 getName = H Med GDR 14
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 143 getID = 184 getName = H Med GDR 16
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 144 getID = 185 getName = H GDR 24
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 145 getID = 186 getName = H Med FRG 13
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 146 getID = 187 getName = H Med FRG 14
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 147 getID = 188 getName = H Med FRG 15
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 148 getID = 189 getName = H Med FRG 16
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 149 getID = 190 getName = H Med FRG 17
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 150 getID = 191 getName = H FRG 25
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 151 getID = 193 getName = H Radar GDR 01
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 152 getID = 194 getName = H Radar GDR 02
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 153 getID = 195 getName = H Radar GDR 03
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 154 getID = 196 getName = H Radar GDR 04
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 155 getID = 197 getName = H Radar GDR 05
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 156 getID = 198 getName = H Radar GDR 06
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 157 getID = 199 getName = H Radar GDR 07
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 158 getID = 200 getName = Bitburg
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 159 getID = 201 getName = Airracing Lubeck
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 160 getID = 202 getName = H FRG 27
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 161 getID = 204 getName = Airracing Frankfurt
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 162 getID = 208 getName = H Med FRG 21
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 163 getID = 211 getName = H FRG 30
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 164 getID = 212 getName = H FRG 31
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 165 getID = 213 getName = H FRG 32
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 166 getID = 215 getName = H FRG 34
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 167 getID = 218 getName = H FRG 51
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 168 getID = 219 getName = H FRG 38
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 169 getID = 220 getName = H FRG 48
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 170 getID = 221 getName = H FRG 49
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 171 getID = 222 getName = H Med FRG 24
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 172 getID = 223 getName = H Radar FRG 02
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 173 getID = 225 getName = H Med FRG 26
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 174 getID = 226 getName = H GDR 25
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 175 getID = 227 getName = H GDR 26
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 176 getID = 229 getName = H GDR 31
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 177 getID = 230 getName = H GDR 32
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 178 getID = 231 getName = H Med FRG 27
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 179 getID = 232 getName = Pferdsfeld
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 180 getID = 233 getName = H Med FRG 29
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 181 getID = 234 getName = H FRG 40
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 182 getID = 235 getName = Buchel
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 183 getID = 236 getName = Leipzig Mockau
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 184 getID = 237 getName = H FRG 43
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 185 getID = 238 getName = H FRG 44
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 186 getID = 239 getName = H FRG 45
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 187 getID = 240 getName = H FRG 46
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 188 getID = 241 getName = H FRG 47
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 189 getID = 242 getName = Bad Durkheim
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 190 getID = 243 getName = Gelnhausen
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 191 getID = 244 getName = Herrenteich
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 192 getID = 245 getName = Hockenheim
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 193 getID = 246 getName = Langenselbold
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 194 getID = 247 getName = Walldorf
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 195 getID = 248 getName = Ober-Morlen
2025-05-18 07:05:13.146 INFO SCRIPTING (Main): World Index = 196 getID = 249 getName = Pottschutthohe
2025-05-18 07:05:13.147 INFO SCRIPTING (Main): World Index = 197 getID = 250 getName = Worms
2025-05-18 07:05:13.147 INFO SCRIPTING (Main): World Index = 198 getID = 251 getName = H Radar GDR 09
2025-05-18 07:05:13.147 INFO SCRIPTING (Main): World Index = 199 getID = 252 getName = H Radar GDR 08
2025-05-18 07:05:13.147 INFO SCRIPTING (Main): World Index = 200 getID = 253 getName = H FRG 41
2025-05-18 07:05:13.147 INFO SCRIPTING (Main): World Index = 201 getID = 254 getName = H FRG 42
2025-05-18 07:05:13.147 INFO SCRIPTING (Main): All Airbases printed to DCS.log !
Unfortunately the getAirbases ID does go out of sequence with that seen in the SU-25T/FC3 (not sure if a bug or intended), however we can use the table index as a proxy and cross check with the already known ID's from in game testing i.e. in game Ramstein has ID 133 which maps to the getAirbases.ID 165 and getAirbases.Name Ramstein.
Here is my script
-- Runs once, prints to DCS log file -- Prints a table of all airbases with: -- Table Index -- ID -- Name local aerodromes = {} local bases = world.getAirbases() env.info("There are " .. #bases .. " Airbases in the World") for i=1, #bases do local index = #aerodromes + 1 aerodromes[index] = {} aerodromes[index].id = bases[i]:getID() aerodromes[index].name = bases[i]:getName() aerodromes[index].pos = bases[i]:getPosition() env.info("Table Index = " .. index .. " getID = " .. aerodromes[index].id .. " getName = " .. aerodromes[index].name) end env.info("All Airbases printed to DCS.log !")
and is based off this post
Sample mission, the data is written to DCS.log
World Airfield ID's using Script (WIP), GermanyCW.miz -
3 hours ago, grim_reaper68 said:
Those informations doesn't appear in any lua file, so I presume that they are part of core files only the devs have access.
I believe you can use a script to get the data but haven't found an example myself i.e. using
• AERODROME NUMBER - getAirbases > ID
• AERODROME NAME - getAirbases > CallsignFor the Caucause map the ID is offset by 11, so ID 12 (Anapa-Vityazevo) --> SU-25T/FC3 ID 1 (i.e. 12-11 = 1 )
But for Afghanistan and Kola the ID's are 1 to 1, so "getAirbases ID" = 16 and is also the SU-25T/FC3 ID
Perhaps Germany is the same and you have better scripting skills ?
-
1 hour ago, grim_reaper68 said:
I suppose you have to fly to all of them know which ID number correspond to the airfield.
No, it just takes time.
Place a few SU-25T around the map and cycle through the ID's in LANDING mode - record the
• HSI's thin needle for bearing
• HSI Distance for distance in km
• Course for a runway cross check when identifying the airfield (and/or to discard heliports ? with a (000) course).Switch to the F10 map and use the ruler to map each ID (with it's recorded bearing and distance) to it's airfield name, rinse and repeat until done or hope @Minsky updates his excellent "Aerodrome Data and Frequencies" kneeboard pages to include Germany soon™.
Screen_250520_235922.jpg.73302768d28f5e4a1a0638426235070d.jpg)
Sa342 high tourqe when increasing fuel
in SA-342M Gazelle
Posted · Edited by Ramsay
Test start up in current DCS version and add a list of potential pitfalls that may cause an issue.
TL;DR:
Can you share a short track or video of your engine start procedure - this will greatly help in diagnosing why you are having an issue(s). Thanks.
Detail:
Common fuel control lever issues are duplicate (axis) control bindings and/or a lack of dead zones at the end/start of the fuel control lever's movement (when bound using an axis).
However ...
... sounds like you are starting the rotor spinning with the collective lever "FULLY UP", rather than "FULLY DOWN".
This causes the centrifugal clutch to slip under load (as the rotor and engine RPM aren't in sync) and it will quickly overheat/disintegrate both IRL and in DCS.
So also check you flight control control bindings/settings when starting i.e. using RCTRL+ENTER to display the DCS controls indicator.
Tested using the SA342 Caucasus Cold Start Tutorial in DCS 2.9.18.12899