rikkles

Too bad about the seasons. The winter mountain snowline so close to the sea makes for a great vista.

Lebanon Ministry of Defense in Yarze has large helipad areas. I've seen 2 helos on the pads at once many times. Large ones as well. See yellow area on the map. Unfortunately the DCS Syria map does NOT have the big ministry of defense compound modeled, nor the helipads. https://www.google.com/maps/place/Ministry+of+Defense/@33.8408869,35.5559458,503m/data=!3m1!1e3!4m5!3m4!1s0x151f17f0ee3454d1:0xa95f7345dcb39fed!8m2!3d33.842123!4d35.5529725

The area of the Map in Lebanon has way too many mosques. Any high structure has been converted into mosques. For example, the Chekka area has 3 cement factories. All those have turned into mosques ( 34.19N, 35.44E). That's the reason for mosques right by the piers, which are piers for the factories. Many more areas are like that, and the most obvious ones being of course in the Christian areas of Lebanon. That's why it's so glaring.

I've been playing DCS in VR ever since it was an option. VR is really the only way to play flight sims that need immersion, as it gives you a subconscious feeling of the environment (as long as the physical modeling in-game is good enough). You don't necessarily feel it in jets, but in helicopters it is shocking, in a great way. In VR you feel the machine like you never could with a 3-screen display in 8k, even with the first gen VR rigs. I have an ancient mildly overclocked 4Ghz/980i with medium settings but could never go back to a screen when flying helos or piloting a plane. On the other hand, playing RIO is a different ball game. The amount of technical work you have to do is something a hi-res screen is better suited for.

I recommend leaving it linear but cutting off the movement at 90% on both stick axes (i.e. you never move more than 90% of maximum even if you go all the way to the edge).

Classic ED problem. Wingmen handle throttles as binary: Slow or afterburner. In many missions you'll see the wingman literally bail out while still ingressing to target.

Try the Caucasus reactor strike misson. Here the wingman breaks all records and runs out of fuel half-way to the target. Wingman AI has been broken forever.

The 4th waypoint is home base (HB). That one works fine. I confirm that Initial Point (IP) and Surface Target (ST) are missing.

I've never tried 250kts, I was generally at 350kts at half power. I'll try that next, to see if I can keep that idiot alive. The mission being pretty easy, this is a good challenge. Questions about the mission though: 1- There are two caution lights on, from the mission start: - WING SWEEP: I thought this should only happen from damage - CADC: Failure in the air data computer, what's that? 2 - CCRP doesn't work, the diamond marker always flashes and doesn't lock. Does that have anything to do with the caution lights? Looking at the mission in the editor, nothing is set to create failures so I'm a bit surprised as to how these happened.

Don't feel bad, most of the pre-built missions have the waypoints already entered in as you step into the cockpit. That's why so many videos makers forget to point that out.

The wheel is not automatic. It changes the release timing based on what entry is selected in the wheel. So make sure you select the correct ordnance, or (when using bombs) whatever computed impacted point will be wrong. You have to flip up the switches for stations 3,4,5,6 in RIO (or use jester command). And of course master arm on.

Iceman won't take control and keep the plane level if there are any pilot actions on the flight surfaces. This includes the plane not being level, or the trim being too aggressive. This is of course wrong from a UX perspective, and hopefully it'll be fixed soon. In the meantime, level the plane and keep the trim centered before jumping seats, and the autolevel will work.

Wingman always bingo fuels in the mission. In trying to keep formation, he alternates between speed brakes and afterburner, dramatically reducing his range. If you fly slow it improves his range, but never enough to have him able to return home. Also having him trail is slightly better than other formations it seems. It's probably nothing you can fix, but it's surprising that he's so inefficient even with external fuel tanks (which you don't have yourself).

Did anyone notice that the GBU-16 falls way in front of the diamond marker when in TGT mode, no lantirn? I do select the GBU-16 in the RIO scroller, and I've tried straight and level, shallow dive, different speeds, etc... The bombs always fall about 100-200m ahead of the diamond.

The bandits remain unknown although the RWR is screaming 31s, the awacs is calling bandits, and even jester is saying "let's do this". And when I go into STT there's an instant lock.

So I'm flying the Tomcat meets Foxhound mission. I fly towards the Mig31s. I go straight. I zigzag. I tell jester to STT, he locks one. Then I go back to TWS. Nothing. 70 miles. 60 miles. 40 miles. The Migs start shooting. Jester still completely blind. No lock for the AIM54s, nothing. Over and over again. Am I missing something?

https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Core.Spawn.html The Core.Spawn module takes care of all of that.

Hello, I don't understand why the following seems not to work 100%: coalition.addGroup(country.id.RUSSIA, Group.Category.AIRPLANE, groupdata) It works in the sense that the planes show up, and are seen as red on labels. But the AAR shows them as not from any side, and they're seen as numbers like 1000021. Destroying them doesn't show in the numbers of red/blue destroyed. They're fully functional though, and shoot at my own airplanes. Russia is the only red country, and USA is the only blue country. Thanks for any help.

The patch dramatically decreased loading times, especially for VR. Frame rates also increased significantly. Also when mistakenly keeping SteamVR on but launching DCS with VR off, the frame rates used to be like Flight Simulator II on my Apple //e. Now they approach 15fps (quit SteamVR and you're fine), and it shows how big an improvement the patch has made.

No. In the mission editor, you select your flight of F-14. One of the tabs on the right where you have the waypoints and the loadouts looks like a square. This is the tab for navigation target points. You click where you want the NTP to be, then in the comments you write "IP", "FP" or "ST" whatever you want it to be based on the table in the docs. This automatically maps the point to the onboard steerpoint. You don't need to tell Jester anything, as the idea is that he's entered those in the computer before the flight.

Well in any case entering an IP named waypoint in the mission editor doesn't translate into the IP waypoint when you fly. You have to manually tell jester the coordinates. This is in contradiction with the documentation. EDIT: Ok, my bad. One needs to enter NAVIGATION TARGET POINTS, not waypoints. Those are different things in the mission editor. Also the name "IP" is to be entered in the comments section of the navigation target point. Then one can use the IP as a destination in game. You don't need to tell Jester to enter it during the flight.

I'll try that right away. But the docs say: Waypoints 1 to 3 work as expected. The others don't. I'll revert with checking using jester.

CCIP is easy. You slew the caret and freeze it over the target. The problem is CCRP. It's supposed to work in a way where you pre-enter the target info. One of the ways is to put in the IP or ST, as named waypoints in the mission editor. Those are supposed to automatically be input by jester as you enter the aircraft, just like waypoints 1-3. But for some reason I can only see waypoints 1-3, the others don't show up in navigation. What am I missing?

It's not a bug. You need to create a binding for the "target designate fwd". You move up and down the bomb line, and then press that button to put the caret over the target. I've done it many times and it works as described.

What I was saying in the first response is that in theory you should be able to set in the Mission Editor a waypoint by name “IP (or “ST”) and select it during flight. Unfortunately it does not work right now. You can select waypoints 1 to 3 correctly, but not the named waypoints. And that is a bug, since the docs state that you can do it. And for people saying the Mission Editor ahould not be used, that’s just a replacement to the ground entry of waypoints.