McVittees Posted April 2, 2009 Posted April 2, 2009 Now, here's a thing that has been bugging me from day one with BS but I've just lived with it: I currently have the zoom view action mapped to a rotary axis on my x-52 and often find I get a zoom-in / zoom-out 'juddering' that requires me to fiddle with the rotary until I find a sweet spot and it stops. I used to have zoom mapped to the slide control where it would also do the same thing. Has anyone experienced a similar problem and did they come up with a solution? I have mapped the zoom to the rotary from within the game itself. [sIGPIC][/sIGPIC] "Great minds think alike; idiots seldom differ.":pilotfly: i5 3750K@4.3Ghz, MSI Z77A GD55, 8GB DDR3, Palit GTX 670, 24" Benq@1920*1080, X52 Pro, Win 7 64bit.
Skypat Posted April 2, 2009 Posted April 2, 2009 yes you will have these 'Juddering' (in middle position, not in full position) due to the X-52 sensor quality i fixed the problem by capping à 70% the slider curve so now when i'am at low position (Zoom out) i'am in the default Zoom (like ENTER key) so my slider is never in a middle position. hope it's help best regards Skypat 1
McVittees Posted April 2, 2009 Author Posted April 2, 2009 Thanks for that Skypat - you seem to have the answers to all my questions lately! I take it you did your adustment in the BS axis mapping panel, not via the saitek software? Could you post a screen shot? [sIGPIC][/sIGPIC] "Great minds think alike; idiots seldom differ.":pilotfly: i5 3750K@4.3Ghz, MSI Z77A GD55, 8GB DDR3, Palit GTX 670, 24" Benq@1920*1080, X52 Pro, Win 7 64bit.
twobells Posted April 4, 2009 Posted April 4, 2009 It's not limited to the Saitek, the Cougar [i know unbelievable] has the same issue. It may be connected to the middle mouse wheel is by default set to zoom, perhaps deleting that setting my resolve the issue? tb [sIGPIC][/sIGPIC] Rig: W10 PRO 64 bit, Intel 7700K, Asus Maximus IX Code, 32GB G-Skill Ripjaw DDR4, EVGA RTX 2080 TI, Samsung 1TB M.2 970PRO SSD Primary HDD, 4TB Storage, TH Warthog, Oculus Rift, 27" Samsung 4k Display. 2x Wheel Stand Pro v2 (Hotas & Stick) + Warthog Stick Adaptor
CQB4Me Posted April 4, 2009 Posted April 4, 2009 I have mine slaved to the "Z" slider and was getting the same "juddering". I fixed it a bit by opening up a bit wider "dead zone" in the Joystick config program. Now, as long as I get the slider pretty close to center, it stays rock solid.
pbsmgm Posted April 4, 2009 Posted April 4, 2009 (edited) I use the slider. And to prevent the judders on the slider, I created a rather large dead zone so that there are basically three stable settings to minimize the amount of judders. But I went through this rigorously with the X52 Pro and determined the zoom should NOT be done with the X52 profile. It needs to be configured in the slider axis in DCS to zoom. Notice the dead zones at the max zoom in and out. They are there so when you slide all the way in one direction, the judders are gone while you hold that zoom position. I also inverted the axis from its default to match zoom in and out with the slider. Of course, you can adjust it to your liking but here is the base settings. Attached Thumbnails Edited April 4, 2009 by pbsmgm Asus X99 II, i7-6850k, GTX 1080, 32GB RAM, M.2/SSD Drives, Win10-64
Lav69 Posted April 4, 2009 Posted April 4, 2009 This is not unique to BS either. I had the same issues in Lock On.
Reticuli Posted April 4, 2009 Posted April 4, 2009 My newest GlovePIE script (not uploaded yet) greatly improves this: var.0 = PPJoy1.Analog0 var.1 = PPJoy1.Analog1 var.2 = PPJoy1.Analog2 var.3 = PPJoy1.Analog3 var.4 = PPJoy1.Analog4 var.5 = PPJoy1.Analog5 var.6 = PPJoy1.Analog6 PPJoy1.Analog2 = Joystick1.z PPJoy1.Analog3 = Smooth(Joystick1.xrot, 2, .03) PPJoy1.Analog4 = Joystick1.yrot PPJoy1.Analog5 = Joystick1.zrot + (Joystick1.yrot * .5) PPJoy1.Analog6 = Smooth(Joystick1.slider, 2, .03) if doubleclicked(joystick1.button6) then begin { var.m = var.m + 1 if var.m = 1 then begin { say("Standard Dynamic Trim") press(leftctrl) press(t) release(t) release(leftctrl) } end if var.m = 2 then begin { say("Flight Director Dynamic Trim") press(leftctrl) press(t) release(t) release(leftctrl) } end if var.m > 2 then var.m = 0 if var.m = 0 then begin { say("Manual Trim") } end } end if var.m = 0 then begin { t = joystick1.button6 PPJoy1.Analog0 = Joystick1.x PPJoy1.Analog1 = Joystick1.y var.y = 0 var.x = 0 var.c = 0 var.l = 0 var.r = 0 var.p = 0 var.s = 0 } end if var.m = 1 then begin { var.c = 45 var.l = -0.575 var.r = 0.275 var.p = -0.900 var.s = 0.0 var.y = EnsureRange(Joystick1.y / var.c + var.y, var.p, var.s) PPJoy1.Analog1 = var.y + Joystick1.y var.x = EnsureRange(Joystick1.x / var.c + var.x, var.l, var.r) PPJoy1.Analog0 = var.x + Joystick1.x } end if var.m = 2 then begin { var.c = 70 var.l = -0.50 var.r = 0.0020 var.p = -0.775 var.s = 0.0 var.y = EnsureRange(Joystick1.y / var.c + var.y, var.p, var.s) PPJoy1.Analog1 = var.y + Joystick1.y var.x = EnsureRange(Joystick1.x / var.c + var.x, var.l, var.r) PPJoy1.Analog0 = var.x + Joystick1.x } end X65 and X52, Glide, Winx3D, and GlovePIE Profiles http://library.avsim.net/search.php?SearchTerm=reticuli&CatID=miscmisc http://library.avsim.net/register.php X52 + Silicone Grease = JOY stick
McVittees Posted April 6, 2009 Author Posted April 6, 2009 Notice the dead zones at the max zoom in and out. They are there so when you slide all the way in one direction, the judders are gone while you hold that zoom position. I also inverted the axis from its default to match zoom in and out with the slider. Does doing this mean you only have three different levels of zoom - min, normal and max? I was considering trying to map the view zoom to the mouse wheel on the Saitek - that works well you press the esc key and you get the mouse look activated because it zooms in discrete stops. [sIGPIC][/sIGPIC] "Great minds think alike; idiots seldom differ.":pilotfly: i5 3750K@4.3Ghz, MSI Z77A GD55, 8GB DDR3, Palit GTX 670, 24" Benq@1920*1080, X52 Pro, Win 7 64bit.
McVittees Posted April 6, 2009 Author Posted April 6, 2009 My newest GlovePIE script (not uploaded yet) greatly improves this: var.0 = PPJoy1.Analog0 var.1 = PPJoy1.Analog1 var.2 = PPJoy1.Analog2 var.3 = PPJoy1.Analog3 var.4 = PPJoy1.Analog4 var.5 = PPJoy1.Analog5 var.6 = PPJoy1.Analog6 PPJoy1.Analog2 = Joystick1.z PPJoy1.Analog3 = Smooth(Joystick1.xrot, 2, .03) PPJoy1.Analog4 = Joystick1.yrot PPJoy1.Analog5 = Joystick1.zrot + (Joystick1.yrot * .5) PPJoy1.Analog6 = Smooth(Joystick1.slider, 2, .03) if doubleclicked(joystick1.button6) then begin { var.m = var.m + 1 if var.m = 1 then begin { say("Standard Dynamic Trim") press(leftctrl) press(t) release(t) release(leftctrl) } end if var.m = 2 then begin { say("Flight Director Dynamic Trim") press(leftctrl) press(t) release(t) release(leftctrl) } end if var.m > 2 then var.m = 0 if var.m = 0 then begin { say("Manual Trim") } end } end if var.m = 0 then begin { t = joystick1.button6 PPJoy1.Analog0 = Joystick1.x PPJoy1.Analog1 = Joystick1.y var.y = 0 var.x = 0 var.c = 0 var.l = 0 var.r = 0 var.p = 0 var.s = 0 } end if var.m = 1 then begin { var.c = 45 var.l = -0.575 var.r = 0.275 var.p = -0.900 var.s = 0.0 var.y = EnsureRange(Joystick1.y / var.c + var.y, var.p, var.s) PPJoy1.Analog1 = var.y + Joystick1.y var.x = EnsureRange(Joystick1.x / var.c + var.x, var.l, var.r) PPJoy1.Analog0 = var.x + Joystick1.x } end if var.m = 2 then begin { var.c = 70 var.l = -0.50 var.r = 0.0020 var.p = -0.775 var.s = 0.0 var.y = EnsureRange(Joystick1.y / var.c + var.y, var.p, var.s) PPJoy1.Analog1 = var.y + Joystick1.y var.x = EnsureRange(Joystick1.x / var.c + var.x, var.l, var.r) PPJoy1.Analog0 = var.x + Joystick1.x } end This looks very promising, even though i can't understand any of it. I'll have a look at the links in your sig when I get home. [sIGPIC][/sIGPIC] "Great minds think alike; idiots seldom differ.":pilotfly: i5 3750K@4.3Ghz, MSI Z77A GD55, 8GB DDR3, Palit GTX 670, 24" Benq@1920*1080, X52 Pro, Win 7 64bit.
Recommended Posts