Holton181

It would be a nice feature, but if complicated just let it be. Without knowing how these things are developed, I can understand it's more complicated than the static map. All content being dynamic in size with zoom levels and such, making it look good on the screen. I have noticed some clipping of text when using the WMS in Oruxmaps on my phone and I guess it has something to do with the DPI/PPI (text being really small too). But it's a minor thing and a very special case not part of the main functionality, so don't bother about it. I just mentioned it as an example of why it's more complicated.

To me it looks perfectly fine. The morse code as an underscore of that information would be nice...eventually ;-)

At least for the helicopters there is no channel numbering that correspond to the official channel numbers you propose, only some equipment with channels from say 1 to 10 wher the frequencies are set in ME. So to me it would be nice to have the frequencies avaliable for the other equipment with manual frequency settings.

Yes, have been like that for a long time now.

And to add a small thing to Rouge Trooper's comment. Full throttle is full TO THE RIGHT, opposite to the Huey and most western helicopters. Edit: Never mind, saw now Chic already mentioned that in the first answer.

New Version 1.4 New version!!! 1.4 * Enhanced the XATT sentence after some tips regarding OzRunways. Hopefully XATT is now fully implemented with 12 values * Possibility to send data to several Serial Ports (COM ports) at the same time See first post. /H

I believe Ramsey ment "on line numer two (2)". On that line change False to True.

Happy to help!

I don't think so. It might work just to copy the controls lua files in Saved Games over to same location but Beta, but if something changed controler wise you might get problems. What you can do, and save space at the same time is to update your stable 2.5.5 to 2.5.6. If you are not happy with the 2.5.6, you then downgrade it as easily back to 2.5.5. Follow these instructions: https://forums.eagle.ru/showthread.php?t=114030 Second post contains DCS versions to use. If you go through with this, now when you already have both versions installed, preform the 2.5.5-2.5.6 update before uninstalling the standalone Beta. That way the updater just grabs the files from that install instead of downloading everything again.

In helicopters they are not called rudder pedals, but anti-torque pedals, for a reason you discovered the hard way.

Isn't it another mission you are talking about? (if I remember correctly, nr 8?) Anyway, picking up cargo by landing and pressing that button, you need to be really close to the cargo.

And the user snap views option in settings are activated I guess. So there where no effect manually editing viewAngle in SnapViews.lua to above 140 and CameraViewAngleLimits in server.lua accordingly. Other than that I have no more ideas, sorry.

Did you also include the SnapViews.lua I provided? There is the parameter I believe you should play with: viewAngle Also read about the recommended setting for CameraViewAngleLimits as described last in my post. CameraViewAngleLimits and viewAngle are somewhat related.

Since you mentioned tinkering with the views.lua (or I assume that is what you meant) and hence display some experience with lua files, I give it a shot trying to at least point you in the right direction. Mind you, I'm no expert what so ever, don't expect my explanations to be without flaws! Most of my limited knowledge comes from THIS thread. Previously we were able to tinker with the views.lua lokated in each aircrafts main folder, in this case: ...\DCS World [2 [OpenBeta]]\Mods\aircraft\Uh-1H\views.luaThat's not possible anymore. But the same things can be done elsewhere, namely: ...\Saved Games\DCS[.openbeta]\Config\View\Server.lua and ...\Saved Games\DCS[.openbeta]\Config\View\SnapViews.lua If this folder and/or file does not exist, you have to create the \Config\View\ within ...\Saved Games\DCS[.openbeta] then copy the Server.lua in ...\DCS World [2 [OpenBeta]]\Config\View\ to that new folder. Now open ...\DCS World [2 [OpenBeta]]\Mods\aircraft\Uh-1H\views.lua in Notepad++ Copy the entire section ViewSettings = {...}Open ...\Saved Games\DCS[.openbeta]\Config\View\Server.luaPaste the previously copied ViewSettings to the end of that Server.lua. Add ["UH-1H"] directly behind ViewSetting, like this: ViewSettings["UH-1H"] = {...}Now you can do whatever settings you did in that section in views.lua, but in this Server.lua in appropriate section (repeat this procedure for each aircraft that is not already represented in the file). Download THIS SnapViews.lua, it's the one I use and the link is from another thread in these forums. Place it in ...\Saved Games\DCS[.openbeta]\Config\View\Mind you, it contains SnapView settings for all aircraft (I think). You can open the file and remove every SnapViews["xxx"] = {...}belonging to aircraft xxx you don't want to be affected by this tweaking. In this SnapViews.lua you have the parameter you want to play with, viewAngle. For all aircrafts this parameter has been adjusted for the MOD it was taken from, but if you don't use that particular MOD you can set it as you like. The last thing to do is to go to 'SETTINGS-MISC.' in the game and activate 'User Snap-Views Saving', otherwise your FOV setting won't have any effect. As a final thought, an extract from the Server.lua from the MOD linked to in the beginning, regarding the CameraViewAngleLimits parameter: Hope this is of any help.

One can always dream... (said with many years of "experience") ;-) Seriously, good luck!

The collective brake [F] have basically same functionality in regards of the altitude hold as the trim button on the cyclic towards the other channels (except no "recentering of the stick"). Before altitude changes, press and hold the button. When >stabilized< on the new altitude/height, release the button.

Just to give a short version of what was said above: The Viggen was developed for use within, and in the proximity outside, the Swedish borders and never intended for export.

Of course I agree with all here about taking it easy when doing it right. The reason I mention the possibility to slam the load down was purely for gaming reasons. OP wanted to finish the mission and go on. I know from DCS 1.5.7, that I still consider my main install (entire 2.x are by me considered BETA due to everything it broke that is still not corrected), the sling loads are over-sensitive and break no matter how careful you are. Activating automatic release (as usual, I never remember correct naming of things) was basically the only way to deliver the load. But it also made the load basically indestructible unless releasing it manually (or breaking the sling). I don't know if the over-sensitivity has been corrected, but I guess the over-sustainability when in automatic release is still there.

Thanks for the pic, I wasn't in a position to do it myself. Regarding the OFF position there is no axis control for that I'm afraid. The entire axis range is from idle to automatic throttle.

This sounds like you haven't found the axis settings page. When you go to the control settings the axis settup is not done there together with buttons, you have to do one of two possible things to go to axis setup. 1) in the drop down menu to the upper left, besides the aircraft selection drop down, you can choose categories of button assignments, but also "search..." and axis configuration (can't remember exactly how it's named). Select the last one mentioned. 2) down among the buttons on the bottom of the screen, about in the middle, you have a button named something like "Axis configuration". Press it. In the configuration window you now have, all axis can be configured. Remember, if you like to change an assignment you have to firs remove the active and then add the new.

OK, might be so. Reason for asking about the kneeboard is that I dont remember if it is treated as an MFD (getting exported) or not. But when I have done this I have exported to the secondary, smaller display to the right, so 0,0 have been located on my main display. The controls indicator have still been overlayed on one of the exported MFD's to the right. Sorry I can't help, hope you find a solution.

Did you select the "Axis configuration", "Axis setup" or whatever it's called in the control configuration window? And the collective isn't there to be found together with cyclic and pedals? You didn't accidentally configure the throttle instead of the collective (have happened before)?

Can't help with the lua, but from experience doing MFD exports previously I remember the control indicator used to appear as an overlay on one of the exported MFD's. Even though the Huey doesn't have MFD's to export, having DCS configured for it migt still cause this issue. Have you tried to open the kneeboard? Is the control indicator there?

Ah, that's a bummer. I cross my fingers...

Sounds familiar to ATC issues with FARPs. After takeoff, can you contact the same tower for azimuth and inbound?