Pyrocumulous

Suggest that manual should state that the ejection handles (both red and yellow) are not functional in the simulation.

For affect, RB-04 is certainly not ideal for subs. I was just surprised to see it so effectively picking them out when pulled up right against the pier. The BK90s loaded with MJ2 seems to have good effect, although not sure that's realistic either.

I found DCS-Insight to be a good way to get to the LUA Console: https://github.com/DCS-Skunkworks/dcs-insight/

Anyone have knowledge of the RB-04e's ability to actually find a ship that is close to shore (against radar clutter)? In DCS, if I launch on submarines that are docked, it nails them every single time. I suspect it's over performing, but it would be a rather nice solution to avoiding pop-up into radar coverage in this one mission that I'm designing. That said, it doesn't seem to actually kill them. BK90 and especially RB-75T have far better effect.

I believe: B = bränsle = fuel V = väglängd = distance It appears essentially to be percent fuel per kilometer. Think of it as kilometers per liter (but the inverse, so lower number is more efficient), but we don't have a fuel gauge that measures in liters or kilograms, so they used percent capacity of the fuel tank. Each percent of the fuel capacity is about 42kg of fuel.

Given that we have fixed terrain sandboxes to play in, and really, there's only a handful of weather patterns per season per terrain: it might be sufficient to just create presets that mimic actual weather but aren't actually simulations. For example, windward coastal environments, versus inland deserts, versus mountains on the same map. Wouldn't need to necessarily model orographic lift or anything if it's just a set of curated weather scenarios.

Just to make it difficult: for the AJS37 on the Kola terrain, if set to the "Use real, and DCS codes" or "Only use the real codes" the airbase numbers are different and the TILS channels no longer match those airbase numbers. For example:

Here is an example for a jet fully fueled with external tank (XT) and four racks of bombs (SB) at sea level and 0.55m. It's curious that according to the nomogram, 0.50m should be the most efficient mach at sea level for all loads, but the Heatblur manual indicates 0.55m.

I found it in the lastalternativtabell (load option table?) on Page 8 of that document. It appears that you just look up the at start, 100%, 70%, and 40% fuel and then you have weight and the resistance (DELTAD) at several reference machs. It looks like jettisoning the external tank results in a -5 DELTAD.

The example line looks like it would make sense if I knew what DELTAD was referring to. My assumption is that it a drag coefficient. That is from page 93 of this document: https://www.ftfsweden.se/wp-content/uploads/2016/11/Fpl-AJ-37-speciell-förarinstruktion-SFI-del-3.pdf

For the below kilometerförbrukning nomogram, how do I calculate the percent fuel per kilometer? I've drawn (red) 0.55 mach, turned right (purple) at 1600kg flight weight (flygvikt). Where do I turn up on the DELTAD quadrant? I assume that this is a point in time, so if for a flight segment I start at 19000kg and end at 13000kg, 16000kg would be a decent approximation of the average flight weight. Is this correct? Testing the above approximation for a full 127.5% fuel cycle (rather than just a snapshot in time, since I don't have a way to precisely measure fuel in the tanks), I flew 1075km at ISA-15 and 5m altitude for approximately 0.12 percent per kilometer.

Experimenting further, this is just an issue with the Wrath of Thunder M05 mission because it doesn't have an invisible FARP. The module itself handles rearm / refuel from FARPs splendidly at present.

It appears that you can only refuel to 100% using the normal ground crew commands unless you use the kneeboard. The mobile ground crew can replace the external tank, but can not actually fill it up without using the kneeboard. Noticed this in the included Wrath of Thunder M05. or maybe I'm doing it wrong.

This isn't really a bug, but could use improvement none the less: there are no units listed for QNH, temperature, or cloud base. It's easy to confuse mmHG for hPA (problematic for Spitfire, Viggen, and M2000 pilots).

Mission 03 briefing says that TOT for Dodge 2 (AI flight) at M05 is 16:26:30 but Dodge 2 actually drops bombs a minute late at 16:27:30. Dodge 1 (player) briefed TOT is 16:27:00, but it should be after Dodge 2 drops bombs. TLDR: there is a discrepancy in briefed and actual TOT times for M05 by a minute. As mentioned in other messages, L1 is not set to 9011, so that's on the pilot.

Just thought I'd jot down a few notes for anyone else that that is considering an alternative to a mouse for DCS World in VR. I use a tray that sits between my throttle and HOTAS, and while one could put a mouse on it, a stationary pointing device makes more sense given the limited space and limitations of VR. I've been flying with the Apple Magic Trackpad 2 for several years, and then just started testing a Kensington Slimblade Pro this week. I'll just place a list here of what each does well and what the limitations are. Both devices can be used wirelessly via bluetooth, but I use both via USB. The Magic Trackpad utilizes the Mac-Precision-Touchpad driver, which allows it to be used as a Windows Precision Touchpad. This gives the ability to use a lot of gestures, but not a lot of customization options here. The Kensington Slimblade Pro utilizes Kensington Works. A regular mouse with a scrollwheel is really the gold standard to judge against, so if that fits with your sim setup, just go with that. There are two primary functions that utilize the mouse in DCS World: the map screen / mission editor and clickable cockpits / comm menu / rearm menu. Apple Magic Trackpad Great for no-eyes ambidextrous use. It's a large touchpad, and wherever your finger makes contact on the trackpad, that's where it is. If you've used a laptop, you already have the muscle memory built. No moving parts, and no crevices to gather any grime. Scrolling is intuitive, two fingers swiped up or down and the knob spins. Zooming in and out of maps and external views is accomplished with the pinch gesture. It can be a lot of pinching (and whatever the inverse of pinching is) when moving around on a map. Scrolling lots / fast is easy, precision scrolling is very difficult. For example, trying to set the altimeter or just barely turn on the lights. It's a large touchpad, so you can drag a long way before you run out of space, but if you have to raise your fingers the click-drag is terminated. Left clicking and right clicking works quite well, just tap with one finger for left or two fingers for right Holding the left mouse button is done with a quick tap-tap of a single finger. This works pretty well for most applications, although sometimes you get a click-click instead of a click-hold due to the speed of your taps. Precision dragging a slider such as changing the curve on a axis is also a challenge. Holding the right mouse button down is impossible. There are clickable cockpit switches that you need to hold with right click, measuring in the map, are among the challenges here. Precision is improved by turning down the pointer speed, and given the size of the touchpad you can turn it way down and not run out of space. Precision Touchpad settings in Windows initially looks pretty exhaustive, but there is not much customization that can be done that is applicable to flight simming. The most useful is probably the three and four finger tap, for which you can create a custom keyboard shortcut. Polling rate appears to only be 92 hz, which makes for a less smooth operation on the desktop, but realistically, I can't tell the difference in the VR cockpit. Photo plus screen capture from Windows touchpad settings in spoiler: Kensington Slimblade Pro Your fingers have one home base: they need to be on that ball. Fortunately the ball is easy to find in the blind. What isn't always as easy to find is the clickable buttons, they are huge buttons, but only the 1/3 closest to the ball is actually clickable. Not a huge problem, but not as good as the Trackpad in this regard. It might make sense to add some masking tape or similar tactile indicator. There are four physical clickable buttons, of which you will probably want to make the bottom right and left the left/right clickers, and then you have two more to be creative with. The Kensington Works software allows you to select anything for those four buttons: launch programs, keyboard shortcuts, etc. One limitation is that the only modifiers keys for keyboard shortcuts is ALT, CTRL, SHIFT, and Windows: there isn't a Left Control option, for example. You could even customize shortcuts for two buttons clicked simultaneously. You can hold those clickable buttons down easily while dragging with the ball. It's really pretty easy and intuitive. Right, left, middle, it's glorious in the F10 map compared to the Trackpad. Scrolling is handled by twisting the ball horizontally. You can customize the rate of scrolling in Kensington Works, and I found that the Intertia Scroll setting is excellent for allowing precision adjustments (e.g. setting altimeter) but also being able to spin a dial all the way. The mouse pointer is held stationary (in software) while spinning the ball; this works surprisingly well but still can be challenging to keep the pointer on the knob while you are spinning it. This also accomplishes zooming the map and external views. There is an audible and tactile clicking sound when twisting the ball which comes from a speaker in the device; I kind of like it, but it's odd that there is no way to disable this affect. The trackball plus physical clickers means that you have unlimited dragging. You can set the CPI (Counts per Inch, essentially resolution) with a button on the right side of the device, which combined with adjusting the pointer speed is pretty effective at maximizing precision while still maintaining range of motion. CPI can be set to 400, 800, 1200, and 1600. 1600 will move your pointer across the cockpit by only nudging the ball 30 degrees or so, 1200 seems to be about ideal for my setup. Polling rate appears to only be 128 hz, which makes for a less smooth operation on the desktop compared to a good mouse (1000 hz), but realistically, I can't tell the difference in the VR cockpit. Previous firmware versions (<4.49) had a wired polling rate of 500 hz, but this caused problems, so as of v4.49 both bluetooth and wired modes are capped at about 128 hz. Photo plus screen capture from Kensington Works in spoiler:

The mounting is easy if you use the Airtac F-MF25SDB and the hardware linked in my post. The fake Matris MB2901x damper that I used has some stiction as well, although it's not too bad if you spend some time fiddling with the resistance knob. I'd like to find a better one for fine rudder adjustments, but we're definitely not the target audience for any of these motorcycle dampers. For fixed wing aircraft, I would leave springs in place, but for rotor wing or a combination of the two, the damper mod is preferred.

M21 - Rb04E Anti-shipping Missile does not have RB04E missiles installed on the aircraft. For the ground start, that's easy to fix, but not so much for the air start. These are great missions for becoming reacquainted with the Viggen after several years away, thank you

How deep did you make it? "Thickness" appears to be roughly fog depth from MSL. I say roughly because at 100m of thickness in my testing doesn't seem to even get through the sea surface. I haven't tested on flat maps where you would expect an unending blanket, but with topography it looks pretty good. Example of 250m thick fog with 100m visibility on South Atlantic map:

Just a comment: It seems to me that if there is going to be a version number on the manual, it should be updated with each revision rather than staying fixed at RC 2.1. Appreciate the constant improvements, though!

My suggestion would be to open a Command Prompt, navigate to your \Program Files\Eagle Dynamics\DCS World\bin folder, and then run DCS_Updater.exe update 2.9.8.1214.1. After that is complete, try updating all but the Syria terrain from the launcher.

null With the launcher, you can selectively update all but Syria, which allows you to fly FIWOS (over the older Syria terrain) and have the current version of DCS World.

After completing campaign (another stellar set of missions, BTW) I decided to try some Gauntlet Ops to keep fresh until LOWOS. If I press END MISSION after completion, it'll reset the entire campaign progress, right? Not a big deal, but the 95 score on Mission 12 is nagging at me, and I might have to make another run at that one...

I've been flying in VR with an Apple Magic Trackpad (in Windows functions as a generic "precision touchpad") for quite some time now, and I mostly love it, but the two things that make me reach over for a real mouse consistently are 1) right-click-hold which is sometimes needed to get a switch to hold or in the F10 / editor screen, and 2) precision scrolling, like when trying to set altimeter Anyone know how to accomplish these things with a precision touchpad? I'm considering switching to a trackball, but I 90% love the Trackpad for VR.

Have you tried cycling between black hot / white / tv? Some of those radars are practically invisible in IR in the targeting pod, as currently implemented in DCS. When I flew Mission 8 yesterday, I found the SA-11 site, but could only pick out the Command Post for whatever reason (I assume the others weren't running their engine, so no heat). Fortunately, it let me drop a GBU-31 on it while only waking up long enough to pucker me up but not long enough to give rotor an opportunity for a HARM. Another potential issue is that this is a super high CPU load mission. My 7950X3D CPU was heavily taxed once I entered Sierra, and it kept framerate down at sub-50fps (in VR anyway). Looking at GPU Wait, it was at 18 ms or so for that entire period, while CPU Wait was around 0.17 ms (millisecond), meaning that the GPU was always waiting on the CPU and for a really long time every single frame because there was so much work to do. All that to say, you could potentially be seeing a performance issue depending on your hardware, as this is a particularly taxing mission. (I find that DCS World in VR is essentially always CPU limited in VR with my RTX 4090, this mission is just particularly so)