Zyll

hmm, I do that with every openbeta update, didn't seem to make a difference.

Hi team, I'm getting these errors over and over in my dcs.log when I log into some of our group's multiplayer missions. As far as I can tell, there's nothing wrong with the mission though, as others are flying it just fine without errors. Eventually, these messages just keep spamming until I hit single digit FPS, and then the game just goes unresponsive. 2019-08-25 04:05:56.180 ERROR EDTERRAINCORE: utm_private::fromLatLon Longitude 156.917d more than 60d from center of UTM zone 40 2019-08-25 04:05:56.180 WARNING LOG: 1 duplicate message(s) skipped. 2019-08-25 04:05:56.180 ERROR EDTERRAINCORE: utm_private::fromLatLon Longitude -78.2376d more than 60d from center of UTM zone 40 2019-08-25 04:05:56.180 WARNING LOG: 1 duplicate message(s) skipped. 2019-08-25 04:05:56.180 ERROR EDTERRAINCORE: utm_private::fromLatLon Longitude nand more than 60d from center of UTM zone 40 2019-08-25 04:05:56.202 WARNING LOG: 3 duplicate message(s) skipped. 2019-08-25 04:05:56.202 ERROR EDTERRAINCORE: utm_private::fromLatLon Longitude -33d more than 60d from center of UTM zone 40 I checked the server logs, and there are no such errors. Thanks in advance,

Is the consensus still that the in-game FPS limiter is inferior to using Riva tuner? What's the issue with the in-game limiter anyways? Thanks,

Being able to see the pitch ladder is more important to you than the VVI in certain situations, such as low level flying :)

That's apparently the realistic behaviour, to hold and slew. However in order to support HOTAS that don't play well with this, they added that option a couple months or so ago for unrealistic slew.

Oh no offence tak. FOX 3!! shit, sorry thought you were an enemy ;)

PLID.... So that's interesting now. If one Hornet were to ID a friendly as hostile using PLID, and one other aircraft were to interrogate correctly as friendly, when you try to IFF it, is there a 50 50 chance you get an ambiguous ID?

Given that all aircraft in DCS are either friendly or enemy, I believe it's safe to assume an ambiguous contact is an enemy. Please correct me if I'm wrong here.

thx for the heads up!

Cool thx for correcting me. Updating my notes!

Oh sorry, that's instructions to power the electrical systems with ground power. Not exactly what you were asking

With external electrical power - 1. Battery - OFF 2. EXT PWR switch - RESET - NORMAL (right click) 3. GND PWR switches 1, 2, and 4 - B ON (left click hold for 3 seconds) 4. L® DDI, HI/MPCD, and HUD - ON 5. COMM 1, 2, and ADF - AS DESIRED 6. Warning and caution lights - TEST 7. Inertial navigation system - ENTER WAYPOINTS DESIRED

Two weeks!

Nothing I'm aware of to set your cockpit displays based on flipping between master modes. Would be happy to be wrong though

Oh and I've been doing this for a while, it's definitely not a new addition for me.

Hmm, I may need to check again then. My usual workflow involved going into AMRAAM mode, putting radar on right MFD, RWR on left, setting 80 degrees radar sweep and 80 mile range, pressing the 'SET' OSB. Then if I were to switch to sidewinders and back to AMRAAM, my screens reset to the way I like them. Maybe the 'SET' OSB is key here.

If you use the AA weapon select modes, they will remember the MFDs that you used the last time you were in that mode. Maybe that will work for you.

Personally, I'm gonna continue to practice hitting the important markers, with the goal of making consistent landings that all look identical. I guess it's not real life, so whatever floats your boat if you want to wing it and go 10 to 90 degrees on the base turn, knock yourself out.

Huh??

If it was all easy, we would have gotten bored with the Hornet long ago ;)

Oh of course, the moving ship will affect your position when you come out of the turn as well, good point

I just watched the track. You are landing on an airfield, so the rules don't apply exactly. the most important thing is that on a carrier deck, the landing strip is offset 9 degrees from the bearing of your upwind and downwind legs, so you need to turn 189 degrees to be aligned with the runway. It also seemed you were quite fast, 171 knots, so you may have been heavy. For a carrier landing, you should aim for 33,000 lbs or lower when landing. Give it a try on a carrier, turn on TACAN so you can get an accurate reading of your abeam distance, and try to hit all the marks (Gs 1% of speed, 1.2-1.4nm from the ship, turn on base when you see the back of the ship for 30 degrees) and see how you fare.

I'm sure someone can view your track file and give some good feedback. I'm away from my computer otherwise I would take a look.

it really is about getting a feel for the whole pattern, which means repeated practice. 30 degrees and keeping your Gs at 1% of your indicated airspeed are good places to start, but I find (just like you), that these are not hard-set rules that will always ensure a perfect alignment on base. Personally, I find that I need to adjust my bank angle on base depending on how far abeam of the ship I am at the 90 degree mark (ie. when you are the closest distance from the ship). If I am 1nm from the ship, then the 30 degree bank is what works for me. If I'm 1.2 or 1.4nm abeam, then I use a shallower bank. These are what work for me, YMMV: Nm Bank Angle 1.0 30° 1.1 26° 1.2 23° 1.4 19° This is also dependent on how far downwind you fly before turning on base. I like to think I'm doing it at the right moment. What's interesting, is that I'm finding my banks need to be shallower than the recommended 30 degrees, but you are actually quite a bit steeper. Are you sure you are reading the bank markers correctly? 0, 5 deg, 15 deg, 30 deg, 45 deg

no, i don't believe so, but I didn't try to be honest. Just so you know, the watermark in question is on your desktop wallpaper only, it won't show in-game or if you have Chrome maximized or anything like that. Of course, if you have concerns about exposing your PC to potential malicious code while having integrity checks off, that's totally valid, and you need to weigh your comfort level with not being able to run vjoy.