|
IL-2 Sturmovik: Cliffs of Dover Latest instalment in the acclaimed IL-2 Sturmovik series from award-winning developer Maddox Games. |
|
Thread Tools | Display Modes |
#1
|
||||
|
||||
anyway to use the mouse wheel to control prop pitch?
is there any software that makes my mouse wheel a slider?
__________________
2.4ghz dual core cpu 3gb ram ASUS Radeon EAH4650 DI - 1 GB GDDR2 I PREFER TO LOVE WITHOUT BEING LOVED THAT NOT LOVE AT ALL |
#2
|
||||
|
||||
Yeah I want to use my mouse wheel for elevator trim.
__________________
Flights of Fancy The Real Deal Battle Over Britain Two Little DUCs , Battle Over Britain Redux |
#3
|
|||
|
|||
yes. first...did u try to map it in game yet? I would be surprised if you couldn't do it directly. go to controls/aircraft/axis, find prop pitch axis...etc.
If that doesn't work you can follow this thread http://forum.1cpublishing.eu/showthr...200#post271200, then write a script to do it, or I will give you one to do it. but u will have to do all that stuff in the thread (i.e. get glovpie, ppjoy...etc). the script would be something like this (not tested): //proppitch for mousewheel if mouse.wheelup=true then var.proppitch=var.proppitch+.2 elseif mouse.wheeldown=true then var.proppitch-.2 endif if var.proppitch>1 then var.proppitch=1 elseif var.proppitch<-1 then var.proppitch=-1 endif //.2 will give you 10% change on the axis. //map the variable "var.proppitch" to a PPJOY virtual axis. like below ppjoy1.analog0=var.proppitch //happy days |
#4
|
|||
|
|||
I would rather use mouse wheel for zoom/fov!!
__________________
“Violent, irrational, intolerant, allied to racism and tribalism and bigotry, invested in ignorance and hostile to free inquiry, contemptuous of women and coercive toward children: organized religion ought to have a great deal on its conscience.” ― Christopher Hitchens |
#5
|
|||
|
|||
hi again.
yes, that script up there should work for elevator trim on mouse wheel too. the variable name is just that, a name. so if you want to call it var.elevatortrim or var.et or whatever, that will work. also, somwhere around here I posted a fov/zoom script-- because the cLOD took away the past IL-2 keyboard functionality where you could zoom in/out incrementally. instead, clod uses the mouse to do that now anyway you could substitute mouse.wheelup=true or mouse.wheeldown=true in that script for joystick1.pov1=90 and joystick1.pov1=270 and it should work. it is clunky because there is a "gate" at 30 fov. in other words, you have to enter the gate by tapping delete button, then you can zoom further. so there is a few microsecond delay in that script. i think at some point, they will probably patch back old il-2 functionality for the keyboard to make it smooth and can dump this script (fingers crossed). here it is again, you have to measure your monitor in the vertical in mickeys to make it work (i.e.,where I have 870). you do that in glovepie.: *GLOBAL var.mcx=640/2 //game resolutions var.mcy=480/2//game resolutions if var.mcy=480/2 then //changes zoom variable when game resolution changes var.mckmstr=480 elseif var.mcy=600/2 then var.mckmstr=600 elseif var.mcy=768/2 then var.mckmstr=768 elseif var.mcy=864/2 then var.mckmstr=864 endif *ZOOM [HotKey viewset] if (joystick1.pov1=90.00 and var.a=0) then key.PageDown=true //FOV to 90 key.PageDown=false mouse.cursorposx=var.mcx //initilze cursor, var.mcx and var.mcy equal to game resolution divided by 2 so that mouse cursor is centered. mouse.cursorposy=var.mcy mouse.cursorposy=0 //intialize mickey count var.mick=mouse.DirectInputY //initialize mickey count var.a=1 //start action endif if (joystick1.pov1=90.00 and var.a=1) or (joystick1.pov1=90.00 and var.a=2) then //action key.Alt=true //"hold to adjust field of view" mapped to Alt-Z key.Z=true mouse.DirectInputY=mouse.DirectInputY+20 //cursor moves -y direction, sensitivity set here endif if (abs(mouse.DirectInputY)-abs(var.mick) > var.mckmstr) and var.a=1 then //first stage ends key.Delete=true //opens the door to further zoom key.Delete=false mouse.cursorposx=var.mcx //initilze cursor, var.mcx and var.mcy equal to game resolution divided by 2 so that mouse cursor is centered. mouse.cursorposy=var.mcy mouse.cursorposy=0 //initialize mickey count var.mick=mouse.DirectInputY //initialize mickey count var.a=2 //kick back to action endif if (abs(mouse.DirectInputY)-abs(var.mick) > var.mckmstr) and var.a=2 then //second stage ends var.a=3 key.Alt=false //job done, turn off now key.Z=false endif if released(joystick1.pov1=90.00) then var.a=0 //reinitialize variables to do it again var.mick=0 mouse.DirectInputY=0 key.Alt=false key.Z=false mouse.cursorposx=var.mcx //initilze cursor, var.mcx and var.mcy equal to game resolution divided by 2 so that mouse cursor is centered. mouse.cursorposy=var.mcy endif if (joystick1.pov1=270.00) then //snap back to FOV 90 key.PageDown=true key.PageDown=false endif Last edited by MadBlaster; 04-25-2011 at 12:08 AM. Reason: Updated for bug and improved for when you want to change resolutions, change global variables. |
#6
|
|||
|
|||
mickey measurement
paste this into glovepie and run it, then move your mouse cursor to the bottom of the screen to measure you monitor vertical distance in mickeys. the reading is in the box next to the run button.
debug = mouse.CursorPosY mickeys Edit: I seems mickeys and pixels are the same thing. Who knew??? So, you don't really need this tool. Just whatever our vert. resolution. Last edited by MadBlaster; 04-25-2011 at 12:10 AM. |
|
|