Holton181

In addition you also need it due to the total rotor thrustvector is tilted relative to gravity, some of the thrust is used for the altering of direction (component pointing to the center of the turn arc) and hence less thrust fighting the gravity (component pointing straight up). W. J. Wagtendonk "Principles of Helicopter Flight" is basically the standard literature for civil helicopter students today.

And just to clarify, it's the values in limits_6DOF that should be tweaked for this.

I don't question your statement per se, but I think you misunderstood the question discussed a bit (or I did). My interpretation of the question is if there is at least a theoretical possibly to move the controls without hydraulics, even if it might be basically impossible in practice. My understanding is that it indeed is even for big Sykorsky ones, in theory, but not in practice. As you can see in msalama's last post above the underlying reason for his questions is to understand some aspects of flights with AP/stabilization ON in contrast to OFF.

Remember it's a Swedish jet, developed for the Swedish airforce and tactics only. Sweden doesn't use AWACS in the sense USA do for instance. Also with the Viggen you are supposed to know "everything" about your dedicated target, have a thorough plan before takeoff, focusing on that and when done, RTB. No room for improvised strikes on targets of opportunity. Swedish pilots where even highly skilled to deploy their plans in total radio silence, even in multi flight operations, basically talking to no-one during the entire flight. So basically you shouldn't need any radio at all ;-)

No, sorry. Can't help you with that.

What you can do if you like to have a flashlight available when it's dark is to use this MOD: https://forums.eagle.ru/showthread.php?p=3622861

At a first glance every thing seems okay. A few questions: You use the beta and it has the saved games folder DCS.openbeta located in the default location in your windows profile? It's actually not important if you use the beta or stable, but that the folder in Export.lua is the one you use. If you use the DCS folder or any othe than DCS.openbeta, you need to correct the path in Export.lua. I trust you that you already know this, but mention it just in case. The functionality to export the NMEA sentences to a file is disabled in the DCS_NMEA.lua. I guess you already tried it and disabled it again, but it has to be activated in the same manner as for the UDP export and it creates and export to the file NMEA_Test.txt. The default path is /Saved Games/DCS.openbeta/Scripts/NMEA_Test.txt and all folders need to exist before it works. Best is to make sure the path is the same as for Export.lus and DCS_NMEA.lua. As I mentioned to you earlier I will try to implement native Foreflight communication as per the link you gave me.

Can you please post your DCS_NMEA.lua and Export.lua (those you actually use)? If you prefer you can sen them as PM. The file export not showing any information indicate something isn't right with then. Skickat från min D6603 via Tapatalk

Ah, yes: https://r.tapatalk.com/shareLink?url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Fshowthread%2Ephp%3Ft%3D200219&share_tid=200219&share_fid=74365&share_type=t Skickat från min D6603 via Tapatalk

Ah, thanks. I thought since swiss_lipo mentioned he both fly helicopters and jets hes values also was a compromise, that's why I asked for low flying only. I will try it out. And of course, I highly appreciate your massive work on this! Skickat från min D6603 via Tapatalk

Since we discusses personal preferences... What values and in what direction would you recommend adjusting for us flying exclusively low AGL? If beneficial at all? (I'm happy with how it looks now, but I assume it involves some compromises altitude vice) Skickat från min D6603 via Tapatalk

By just a quick look, that Foreflight information might actually be usable! Thanks! I will try to implement it, but I have no possibility to test it myself. I will report back in my dedicated support thread. But I'm away from home a few weeks, so can't do it right away. Skickat från min D6603 via Tapatalk

I'm not familiar with Apple products, but I found the apps you mentioned and tried to understand what they are supposed to do. In my understanding (might be wrong) both of these apps has a limited list of specific external GPS devices that they are supported to receive NMEA from. NMEAgps only supports DUAL XGPS150 / 160. The NMEAconnect description is a little bit ambiguous, first saying "NMEAconnect can connect to any NMEA source like TCP/UDP...", but then giving a list of supported devices, hard to tell what they really mean. To make my MOD work the used app need to be able to receive NMEA from an arbitrary source. If I'm wrong, the user Ex_Machina eventually got it working by opening up a UDP (only) port on his/here router, not a UDP/TCP port as he/she tried first, if that might help. But he/she has an Android with an app I use myself though. See if you can find other NMEA client applications, maybe a Bluetooth based one to try the serial port method? Skickat från min D6603 via Tapatalk

Did you test my MOD in the post before yours? At least one guy except myself got it working eventually over UDP (haven't heard yet if anyone except myself got it working over serial port), look in the suport thread. Skickat från min D6603 via Tapatalk

I knew about it, an I have it un-ticked already, but still a deadzone. But it has happen before that a setting that seems to have a value after an update (also actually have had that value effectively before the update) doesn't effectively have it. One needs to change the value, save, restart DCS, change back, save and restart again to make it work. Haven't tried that with the FFB setting. Will do when I get back to the cockpit in a few weeks. Skickat från min D6603 via Tapatalk

Well, using sarcasm on an international forum can be a hit or (fatal) miss. Quite often the later, so don't be surprised (and offended) when it backfire. Skickat från min D6603 via Tapatalk

Also I think he knows exactly what kind of hype that kind of tiny details can cause... I bet it's only the icon, nothing more.

WHAT A RELIEF!!! :thumbup: I assume it's the "Just open in UDP only" that is the key here, I could use port 8080 myself. I share my phones internet connection to my PC so I don't use a router and has therefore not run into this issue. Thanks for reporting back, I might add this information to the instructions. Hopefully others can make it work with this info. Have fun!

I don't know how many people following this thread, but I am really curious if anyone got it working? Also if not. Feel free to share your experience.

Actually, if you live at or have been close to smooth mountains that get covered by snow occasionally (I do and it happens every late autumn), the even and abrupt snow line is pretty accurate. The other picture is from a much steeper angle, from much higher altitude relative to the mountains, and in addition less smooth shape of the hillsides, giving a more gouged appearance of the snow line. If the angle in the second image was the same as in the first, the snow line would most likely look equally straight.

Just bought the Gazelle, and I experience the same. Obviously I don't know by own experience how it has been. My remedy is to leave the curve sliders at default byt activate the user curves (tick-box below the slides) and increase the lowest (leftmost) vertical slide from 0 to 1. Don't seem much but made a significant difference, deadzone basically gone. 2 is too much. I have a PFT Lynx ("full length") with no mechanical nor firmware deadzone.

Juat a small note. There is also a trim setting in DCS for us with cyclics (joysticks) without FFB but with friction to hold it in place. I use it in all my helicopters with my PFT Lynx controller (possible to apply friction). It improved my trimming routines quite a bit when I started using it, especially in the Shark.

Strange. Any additional errors in the logg? Have you got GPSBrige to work with other applications than DCS? Like X-plane or P3D? And sorry for asking, don't mean to offend you, but the IP you have entered, 192.168.1.11, it's the IP of your Android device right? Not your PC? And they are on the same network? And I have asked before, and do it again. Can you please try to activate the "write to file" function (below the Bluetooth parts), just to see if the actual export of the information works. I will try to use my wifes phone. It's much newer than my own and has more recent Android version, if that might cause issues.

.

My understanding is that it will cause the Viggen to be not flyable. You should copy the mentioned files one folder level up.