bullettime.set via Controller?

Hey guys,
I'm having trouble with the keymap of my Controller. I try to map the function bullettime.set('-20') to the left dpad-Button and the function bullettime.set('+20') to the right dpad button (The config file is attached). But when I now press the Buttons on my Controller, it doesn't do stuff. It just does nothing... When I use the Keybord for this (alt+up / alt+down) it works just fine, but not on the Controller...

My setup:
PS3-Controller mapped as a XBox 360 Controller via Motionjoy...

Had somebody the same problem and could solve it? I couldn't find any solution

MFG,
note

 

I have the same problem with my wired xbox360 controller.

 

So, it seems to be a bug?

 

Nope, don't think so. A lot of people don't have these problems.^^

 

Okay... I will then test this on my PC... (The game runs there a lot less buggy)

 

Okay good luck. If it works please post it here.

 

Well... Like the Idiot I am, I installed Windows 8.1 on it yesterday... Motionjoy is not working on it :/
Does somebody knew how to get it to work? (Google couldn't help me...)


EDIT:
Got it Working... The bullettime-function isn't doing stuff... Like on my laptop...

 

Can nobody help us?!

 

you have a failure there:

These lines in your file:
moveMap.bindCmd(%device, dpadr, "bullettime.set(100)", "");
moveMap.bindCmd(%device, lpov, "bullettime.set(5)", "");

have to be:
%mm.bindVLuaCmd(%device, dpadr, "bullettime.set(100)", "");
%mm.bindVLuaCmd(%device, lpov, "bullettime.set(5)", "");

or:

moveMap.bindVLuaCmd(%device, dpadr, "bullettime.set(100)", "");
moveMap.bindVLuaCmd(%device, lpov, "bullettime.set(5)", "");

if im not messing up with the last one...
but "%mm.bindVLuaCmd..." is how it looks in my inputmap and it works.

 

Still don't work for me. That's my file. (XBOX360 Controller)

// Product Name: Controller (Xbox 360 Wired Controller for Windows)
// GUID: {028E045E-0000-0000-0000-504944564944}
// axes: 5^Y^X^U^R^Z


// 15% deadzone for the camera things
$gp_deadzone = "-0.15 0.15";


// camera
moveMap.bind(%device, thumbrx, "D", $gp_deadzone, gamepadYaw);
moveMap.bind(%device, thumbry, "D", $gp_deadzone, gamepadPitch);


// movement : deadzones and such are in lua for these
moveMap.bind(%device, thumblx, "D", $gp_deadzone, joy_steer);


moveMap.bind(%device, triggerl, "D", $gp_deadzone, brake);
moveMap.bind(%device, triggerr, "D", $gp_deadzone, accelerate);


%mm.bindVLuaCmd(%device, btn_a, "bullettime.set(100)", "");
%mm.bindVLuaCmd(%device, btn_x, "bullettime.set(5)", "");
moveMap.bindCmd(%device, btn_r, "beamNGReloadCurrentVehicle();", "");


moveMap.bindCmd(%device, dpadd, "beamNGResetPhysics();", "");
moveMap.bindCmd(%device, dpadr, "beamNGTogglePhysics();", "");
moveMap.bind(%device, btn_l, parkingbrake_toggle);
moveMap.bindCmd(%device, lpov, "beamNGSwitchVehicle();", "");
moveMap.bindCmd(%device, btn_y, "gamepadZoom(-0.1);", "gamepadZoom(0);");
moveMap.bindCmd(%device, btn_b, "gamepadZoom(0.1);", "gamepadZoom(0);");
moveMap.bindCmd(%device, btn_rt, "beamNGResetCamera();", "");


moveMap.bindCmd(%device, btn_back, "beamNGCameraToggle();", "");
//moveMap.bind(%device, btn_back, beamNGControl);
//moveMap.bind(%device, btn_x, toggleFirstPerson);

 

well, as all of your other binds start with: "moveMap.bind" instead of "%mm.bind" try the other way.

moveMap.bindVLuaCmd(%device, btn_a, "bullettime.set(100)", "");
moveMap.bindVLuaCmd(%device, btn_x, "bullettime.set(5)", "");

 

Nope don't work. (

 

are you sure you edit the right inputmap file ?
if not, get sure by editing some of the standart functions.
also use the debug window for the input, so you can see which button you press, maybe its name is different than btn_x, even when i doubt it.

 

How can I start the Debug Window? Have I to start the Game via CMD or something?

 

I don't have anything to add in terms of fixing the issue, but it sounds more like a bad command than a bug, I don't see why the game would not work when it receives a command via controller. I have to say that I'd too like my 360 pad setup like that though, L/R D-Pad for slow motion/time control.

Though those of you using a PS3 controller such as myself, I also use my PS3 controllers as well as my Xbox controllers I really have to recommend Scarlet Crush's DS3 Xinput Wrapper: http://forums.pcsx2.net/Thread-XInput-Wrapper-for-DS3-and-Play-com-USB-Dual-DS2-Controller

Lot less problems and it just works, MotionJoy caused a lot of issues for me, including blue screens rarely seemingly when my Xbox controller would sometimes use MotionJoy's drivers when plugged in.

Keep in mind you do have to get rid of MotionJoy and it's drivers, but it's for the better, plus when you plug a PS3 pad in it automatically gets detected as an Xbox controller and assigns it a Xbox controller slot 1-4, no more fiddling with DS3_Tool/MotionJoy. It has fully working rumble as well and no deadzones.


EDIT: Are you talking about the dev console or the actual debug modes? Like SHIFT+F1?

 

Doesn't that bind it to one of the analog sticks? If I remember right ZX and ZY were for the triggers so I assume that's for the right stick if memory serves? But that means that whatever direction is hit along that axis it slows down the engines timescale dynamically? Like 20% depression of the stick in so direction means 20% slower timescale?

EDIT: Whoops, didn't see the part where he said it binds it to an analog key.

 

MAN you're awesome ! i always get the freaking blue screen! everytime my controller get's disconnected even for a second than i'd have to restart my pc. i play with my ps3 controller with ( better DS3 ) it's shit because it uses the same motionjoy drivers. you just saved my pc from blue screening and occasionally crashing because of it. i'm downloading Scarelt Crush DS3 right now.

 

Never install motioninjoy, it is actually malware sending data back to some chinese site. It also overwrites part of the windows USB and bluetooth device driver descriptors which no driver should ever have to do (and should be a huge red flag to antivirus software), this is the cause of the blue screen problem

 

How do you know this? I use it and my anti virus doesn't pick it up and Ive had no bluescreen problems?