ldnz

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.

Version History v.928 (2013.04.30) Current version. 9K33M2 OSA-AK (SA-8B Gecko) released. Finally! Very excited and downloading now.

Just had another thought - could combine this with angle of attack and optimise speed for most efficient cruise..

Yep thats another option, but a simple PI controller seems to work fine for steady state flight. To take this further a set of specifications need to be settled on ie: 1) maintain steady speed within 5kn of target 2) achieve the above with climb/dive angles of +/-10 degrees 3) handle a step change of set speed with a settling time of 20 seconds and a maximum overshoot of 5% Obviously these are all made up but if a meaningful specification can be described (and is within the capabilities of the engines/airframe) there are many controller types to be tailored including state/space, fuzzy logic, PID with feed forward, various adaptive control algorithms etc.

Challenge... it's tempting to have a go, but as mentioned with the A10 its an energy battle and you just don't have enough!

Well the beauty of PID is that it can be P/I/D or any combination. In this case I've got it working well enough as a reasonably high gain proportional controller with very limited integral action to lower the steady state error. Still working on some tweaking to the saturation limits of the integral that will hopefully allow more integral action to be applied to achieve a quicker steady state. The next problem is where this is actually useful. At the moment the code runs continuously locking the plane to a fixed speed (in level flight). I've not dug into the scripting possibilities too much yet but I see a use for this if it can be triggered only when the autopilot is engaged as an extra speed hold (as opposed to speed set and achieve) feature. This also allows better control optimisation as it only needs to stabilise for steady state conditions and not worry so much about step response (ie suddenly telling it you want to be 30 kn faster and leaving it to handle the acceleration).

Code is fine - changed KP to 100, KI and KD to 0 and it works nicely as a basic proportional controller. Stable and fast. Now digging out MATLAB to get some charts and tune it properly.

I've used what is basically the same code (optimised for fixed point math) to implement a cruise control on a motorbike - similar problems including a widely variable throttle/torque map.

Adaptive control algorithms generally over complicate the coding problem (and stability if done badly!) for what would probably be limited gains in this system. I would be very surprised if PID was not sufficient for the job. Once the basic loop is stable in both steady state and step response I would consider adding in feed forward terms (for faster step response) - good point about considering altitude as well. The altitude and speed terms can be very broad brush - they would only be used as starting throttle positions for PID to then correct. The basic code given above looks like a correct implementation of the PID algorithm though you may have to play with the integral saturation value. Unfortunately I've not played with LUA in DCS yet! If you could send me the file and a quick guide on where to put it and how to trigger it I'd be happy to play around with fine tuning it. Day off work today! Note: yes outside of physics experiment land nothing is linear - but PID is still the most widely used algorithm out there because a) its well understood and b) its easy to use and c) it works well enough in most situations.

Have a look at the Zeigler-Nichols method of PID tuning - its very effective for systems that are either already in place or too complex to practically model. The short version is that you set the integral and deriv gains to zero, then slowly increase proportional gain until you get the system to a stable oscillation. Once you have that, you use this gain and the frequency of the oscillation to give you starting values for all three gains. This will give you a stable (but not ideal) system with a little overshoot. Its not too hard from there to trim it in perfectly. I see no reason why PID based auto throttle could not be effective in both maintaining a set speed and responding to a change in speed (step response). Once the basic principles are in place additional things such as a bit of feed-forward (ie setting a base throttle amount for a given speed - gets you in the ball park quicker) can be added. I see that wiki page has some notes on Z-N tuning - that should give you the basics.