funkyfranky

+1

Das bin ich, oder? :D 202 - Honkytonk

Tomcat AoA degrees to unit conversion. AoAunits=1.089*AoAdegrees+3.715 You can check the Moose source code how to get the correct AoA in degrees: --- Returns the Angle of Attack of a positionable. -- @param Wrapper.Positionable#POSITIONABLE self -- @return #number Angle of attack in degrees. function POSITIONABLE:GetAoA() -- Get position of the unit. local unitpos = self:GetPosition() if unitpos then -- Get velocity vector of the unit. local unitvel = self:GetVelocityVec3() if unitvel and UTILS.VecNorm(unitvel)~=0 then -- Get wind vector including turbulences. local wind=self:GetCoordinate():GetWindWithTurbulenceVec3() -- Include wind vector. unitvel.x=unitvel.x-wind.x unitvel.y=unitvel.y-wind.y unitvel.z=unitvel.z-wind.z -- Unit velocity transformed into aircraft axes directions. local AxialVel = {} -- Transform velocity components in direction of aircraft axes. AxialVel.x = UTILS.VecDot(unitpos.x, unitvel) AxialVel.y = UTILS.VecDot(unitpos.y, unitvel) AxialVel.z = UTILS.VecDot(unitpos.z, unitvel) -- AoA is angle between unitpos.x and the x and y velocities. local AoA = math.acos(UTILS.VecDot({x = 1, y = 0, z = 0}, {x = AxialVel.x, y = AxialVel.y, z = 0})/UTILS.VecNorm({x = AxialVel.x, y = AxialVel.y, z = 0})) --Set correct direction: if AxialVel.y > 0 then AoA = -AoA end -- Return AoA value in degrees. return math.deg(AoA) end end return nil end Function is essentially from Mist but the Moose function is also valid when wind is non-zero in the mission. There are some other Moose functions called for position/orientation of the AC but it should give you the general idea. It's been tested to work just fine for the Tomcat. Hope it helps :)

Me culpa, adjusted the first post :D

Alright, looks like I'm back in the game. I unplugged and re-plugged every connector I could get hold of. So far it's looking good. X-axis is smooth again. Hopefully, the issue is gone for good.

Thanks guys! I'll try to reconnect the plug - it looks exactly the same for me as in the post you quote, ams999. I'll report back. Good luck to you as well WindyTX!

Ladies and Gentleman, my VKB Gunfighter has a serious issue with the x-axis. Smooth physical deflections of the stick lead to heavy oscillations/jumping in the output which makes flying basically impossible. It is only the x-axis that is affected. The y-axis is fine. I found in the VKB forum a few threads of people with the very same issue. So far I tried a new firmware, currently running v1.960 (I'm using the TM Warthog stick) and re-calibrating several times. All to no avail unfortunately. Is there anything else I can do to fix this? Thanks!

Well done, mate :thumbup:

Just tested, working fine here, thanks. New mission, no problems to have ten (did not try more) ac starting from ramp.

Genau, daher wäre es super, wenn DCS ASW 2.0 unterstützte https://www.roadtovr.com/oculus-launches-asw-2-0-asynchronous-spacewarp/

Ah, good to know I'm not (completely) crazy :) You think it's a feature or a bug?

With the Tomcat, I observe something a bit strange. The cure works very well and AB turn on when I pass the detent. However, when I decrease the throttle and pass the detent in the inverse direction, the AB stays on. I have to move the throttle quite a bit further back than the position where the AB turned on :huh: It's a bit like there is a hysteresis effect. I don't have that in other aircraft and it's not my hardware as I monitor the position with the RCTRL+ENTER overlay. Do you guys observe that as well?

TexacoStennis:SetCallsign is correct. The dot is done by the autogenerated doc html file. Colon is syntax sugar in lua if you want to omit self as first parameter.

Endlich passt das mal zeitlich bei mir :D Dabei! Muster kann ich auch noch nicht sagen. Hängt davon ab, wieviel ich noch mit der F-14 üben kann...

50% increase in FPS is big :D Especially as the statement is kept very general, i.e. independent of GPU, CPU, HMD, map, number of units in the mission etc.

2019-04-03 20:52:40.846 ERROR WRADIO: CommandDialogsPanel: RadioCommandDialogsPanel.setShowMenu error [string "Scripts/UI/RadioCommandDialogPanel/RadioCommandDialogsPanel.lua"]:3015: attempt to index a nil value stack traceback: [C]: ? [string "Scripts/UI/RadioCommandDialogPanel/RadioCommandDialogsPanel.lua"]:3015: in function 'all' [string "Scripts/UI/RadioCommandDialogPanel/RadioCommandDialogsPanel.lua"]:2150: in function 'ProcessRemoteCommand' [string "Scripts/UI/RadioCommandDialogPanel/RadioCommandDialogsPanel.lua"]:2096: in function <[string "Scripts/UI/RadioCommandDialogPanel/RadioCommandDialogsPanel.lua"]:2093> Being in the observer slot. Guess there is a nil check missing base.vcprcp.state.bpos = data.initialized and base.Export.LoGetSelfData().Position

Not sure how the optimization of the terrain engine in meant. Will we see the improvements for one map at a time or is this more a core optimization which applies to all maps?

Thanks for effectively upgrading my 1080Ti to a 3080(Ti) :)

Laut Wags 50% bessere VR Performance aufgrund optimierter Terrain Engine https://forums.eagle.ru/showpost.php?p=3869786&postcount=2333

LOL, love it :D

Can anyone confirm that this has not been fixed in the latest update (DCS 2.5.4.29167)? As Top Jockey mentioned, it solution is straight forward!

:music_whistling:

Track File Please find the track file attached. FA18-TACAN-Bug.trk

Position of carrier is unstable and oscillating heavily in the HSI display. It stabilizes suddenly at the correct position (~33.5 DME) as shown briefly at the very end of the video. DCS version 2.5.4.29079 (but also observed in earlier versions). Track file available upon request.

Colon not dot.