ldnz

One possible subtlety here is the track sweep time. Lets say you've got a track at the center of the sweep pattern, and the antenna has just moved over it moving left. If the computer swings the pattern left to follow a new track - the antenna has to go all the way to the new edge and back. Does this make it take longer than the strict 2 second refresh time?

Yep this one drives me nuts. I've taken as rio to binding 'do not attack' CAP button and mashing it on every new track I can see before the radar slews over to it. I especially hate it when it slews towards a track at ~100nm and trashes my missile that was on a high threat at ~30nm. Surely active guided tracks should have priority. Re de-sync and dropped tracks - me and my pilot have just given up on at least the first missile in any fight as its almost guaranteed to suffer immediate track loss. I assume there is a slight hesitation as the missile spawns, textures load or something, but again its enough for a single missed sweep and wasted launch.

FYI there are jester binds for switching between aircraft and ground stabilised - I use this to switch between Navgrid + ground and aircraft stabilised when committing.

Hi, check out Oceanic Combat Group. While we conduct much of our training in F-18 we heavily utilize Vipers for in our missions with a dedicated SEAD and a Multi-Role flight. We participate in SATAL and are looking to grow more people into competitive PvP. https://oceaniccombatgroup.com.au/ http://discord.gg/ZmXEBSU

Yeah gonna add to this - seems to be a very particular time of day that petrovich just takes a nap, often when the sun is well up. Wish it used local light levels instead of a simple clock.

So if I understand @GGTharos the missile is essentially doing intermittent SARH until such time as commanded active? It makes sense that the messages are getting reflected off the target - the missile isn't necessarily in the radar scan volume (given its large loft) so 1. the F14 doesn't track it, and 2. couldn't transmit direct path to it. Questions I have: 1. what could the datalink message usefully communicate to the missile? If missile knows angular position of the target (monopulse from reflection) then it could communicate information on velocity, heading, which would allow it to refine the intercept? 2. what happens in a track hold target? Is the radar just blasting this coded DL message out in the hope it sweeps over the target and the missile still gets it?

When creating a steerpoint from map, jester won't enter the ground altitude at that point - altitude on lantirn for QWP will be zero. This means cueing the lantirn to that waypoint is hopeless unless vertically overhead. Manually setting waypoint altitude via CAP works, but not available on multiplayer. Cueing lantirn directly to the markpoint does seem to point at ground level at that point, so is a valid workaround.

Hi mate, Oceanic Combat Group - http://discord.gg/ZmXEBSU

We've seen a couple in our group have problems trimming the Mi24 - no effect with the button (you could see it move in cockpit, but no effect), but the directional hat trim would work. Haven't found a consistent issue/fix - one guy fixed it after jumping into the Mi8 and then back and has had no trouble since.

I get this exactly as per original poster, both before and after 2.7 update. Worst offender is multiplayer on Syria map, where repeated F2, F6 to follow a missile, or F10 is almost guaranteed to cause it. Only remedy I've found is to turn down terrain textures and PD/steam SS. I get kicked to WMR failure (4 white balls on VR) and DCS still running at 5 fps on monitor, sometime still responding to position of the VR set. Restarting WMR is required. 2080 Super, G2, 32gb ram. I'm fairly sure its VRAM related.

Have you got options.graphics.stereo_mode_use_shared_parser = true set in autoexec.cfg? That will cause it.

This has happened to me twice - hook up to the shuttle and just as I run up engines the left engine shuts down. No obvious indications. I can restart the engine but as soon as it runs up to idle settings it immediately shuts down again. Respawn has been the only solution. This has happened once tonight and once on the previous patch, both times spawned on the super carrier.

Ok on re-reading the manual and thinking it through there is no issue here. To resync the AHRS there must be no acceleration - so level flight, at steady speed. Pressing the adjustment knob in for ~15 seconds brings everything back into alignment. I don't remember this ever being an issue before the supercarrier though?

I'm seeing this too. Immediately after a supercarrier takeoff the compass sync goes full deflection left andI'm about 40 degrees out. No other warnings or indications. Very frustrating! Happening everytime on OCG through the inferno server from cold start

Just wanted to say thanks to Mbot for this campaign. I'm about 8 missions in and really enjoying it. Everything working remarkably well with very effective strikes by the AI. Only thing noted is that HARM shots vs Hawk tend to go to the stratosphere, I don't think I've seen any Hawk radars taken out by HARM. Had the message that the CVN would be able to move closer, but still operating from the original location. Hopefully it will relocate soon, some long flights in! Only tweak I've made was dropping wind over deck/CVN speed as recommended to avoid catapult cold shots. Haven't had any issues at all since that. Thanks Mbot!

Its in Mods\Aircraft\Mig-21bis\Entry\03_Views.lua. The problem is changing it invalidates the integrity check. Could we please get a wider view by default to avoid this?

I had to edit options.lua and disable oculusrift - that fixed all view issues for me in all modules. Couldn't do it in the menu as would immediately go black screen.

That works - but just check your last digit :) format in NADIR is DD MM.M instead of DD MM SS shown in mission editor. I think? Polychop - can anyone weigh in on polar coordinates? I doubt that button was included purely for decoration.

Ah good find, at least you got it to do something. There must be other uses for the POLAR button, that seems like a rather pointless piece of functionality if it is all it does.

Thanks Erk104, I'm happy with entering coordinates normally, its quick and easy. What I would like to do is create a new waypoint as a bearing/range from either current position or an existing waypoint. The manual suggests its possible (POLAR entry) but doesn't show how it works.

Hello, Has anyone managed to enter coordinates using the polar method in the manual? Need - Say I have range and bearing to target, and want to provide coordinates to a10 for strike. I could give range and bearing from my position read straight out, but it would be nice if I could enter them into the Nadir. This would also give me a waypoint to fly around if I wanted to reposition for an attack. I can't seem to get any response at all from the Nadir when using "from a point to another point (polar)" instructions. Help?

Quite often when in Altitude hold I find it will keep pitching down slowly and picking up speed - right up to 260km/h or so when I start to get retreating blade stall and consequent sudden rolling moment. Level off, rinse and repeat. No change in torque as speed increases, but something isn't right when autopilot is engaged. Will try for a track. Edit: Altitude hold is correct - zero vertical speed, just continuous acceleration as pitch increases on its own. Disengaging altitude hold at this extreme speed sees a sudden drop in altitude and a return back to normal performance. Using a dual FFB2 with simFFB

Hello, sorry if this already recorded. I am seeing correct nose cone movement on highest LOD model, but as soon as you zoom out to next LOD it moves vertically.

Hi, I run 3x 1920x1080 with 144px bezel correction between each as one eyefinity. In standard "1 monitor" or "3 monitor" mode, DCS is fine. On my Eyefinity profile I get the main menu (including settings, etc, everything outside of an actual mission) squished into what looks like one 3rd monitor width starting on the centre monitor (ie x,y position is ok, but width appears 1920/3 instead of 1920). Mouse responds to button positions as if it was displayed at full centre screen width, which makes navigation hard. If I can click through into a mission everything in mission (GUI, radio menus etc) is all on the centre screen exactly as expected. eyefinity.lua: _ = function(p) return p; end; name = _('Eyefinity'); Description = 'One monitor configuration w Eyefinity' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } UIMainView = { x = 1920 + 144; y = 0; width = 1920; height = screen.height; } Attached: screenshot, zipped system.nfo system.zip

Really? I've had no problem using the Sa-8 on the Ustka range. A missile boat sits off the coast and you can set it to lob drones at you. They fly a zig-zag path and I had trouble recognising the first couple. My problem with the Sa-8 is that it works too damn well! After all the other units this one just works and has very little to tweak.