(06-03-2014, 12:19 AM)Wirenut48 Wrote: Still doesn't work 125% settings, but it does with the 100% just fine. Here is the .net error details.
System.NullReferenceException: Object reference not set to an instance of an object.
at ScpServer.ScpForm.Form_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at ScpServer.ScpForm.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I think I fixed the issue, but the UI turns into kind of a mess at 125% settings, so I'm going to fix that first then have you test it.
06-03-2014, 05:17 AM (This post was last modified: 06-03-2014, 05:18 AM by Wirenut48.)
OK thank you very much, after the latest update to the UI everything went bonkers. Yesterday I installed jhebbel's new self installer, also got a .net error on startup but I did manage to get it working and setup a profile just fine, like the auto profile feature. But I like yours better having the joystick deadzones, but as is, it wouldn't load the controller to be able to apply a profile.
(06-03-2014, 06:27 AM)Jays2Kings Wrote: Ok, so this version should be good I think, tested on a Windows 7 PC at 125% text size. and it doesn't crash anymore on it.
This version also has higher quality images for those with a higher dpi.
06-03-2014, 08:24 PM (This post was last modified: 06-03-2014, 08:25 PM by MangoTangoFox.)
If anyone wants to use PS3 controllers they have for local multiplayer, I can confirm that v9.12 of J2K's driver, and presumably many other versions do in fact support simultaneous usage with PS3 controllers running the SCP driver.
So if you are using bluetooth, instal the PS3 pad as normal with the SCP drivers, but only over USB. Then use J2Ks driver to use the PS4 controller over bluetooth. I'm assuming he branced off after I asked OP to change the xinput slots. So the SCP driver will use 1-4, while the DS4 drivers will use 11-14.
The only issue I've found is that the virtual xbox 360 controller from the SCP driver sticks around even after unplugging the PS3 controller for whatever reason. The DS4 counted as controller 1 in the two games I tried, so it wasn't an issue, but I believe stopping and restarting the SCP service would fix it.
06-04-2014, 12:40 AM (This post was last modified: 06-04-2014, 12:43 AM by Jays2Kings.)
(06-03-2014, 08:24 PM)MangoTangoFox Wrote: If anyone wants to use PS3 controllers they have for local multiplayer, I can confirm that v9.12 of J2K's driver, and presumably many other versions do in fact support simultaneous usage with PS3 controllers running the SCP driver.
So if you are using bluetooth, instal the PS3 pad as normal with the SCP drivers, but only over USB. Then use J2Ks driver to use the PS4 controller over bluetooth. I'm assuming he branced off after I asked OP to change the xinput slots. So the SCP driver will use 1-4, while the DS4 drivers will use 11-14.
The only issue I've found is that the virtual xbox 360 controller from the SCP driver sticks around even after unplugging the PS3 controller for whatever reason. The DS4 counted as controller 1 in the two games I tried, so it wasn't an issue, but I believe stopping and restarting the SCP service would fix it.
Yes other methods work for supported the DS3, whether the SCP driver or motioninjoy etc. however adding DS3 to DS4Windows itself isn't possible as of now (and honestly unless someone else does it, it might not ever happen, sorry about this). This is branched of electro's latest beta 10, so it is using ports 11-14.
Also this version is a beta build, this hopefully fixes the memory leak, I didn't add it into the update queue as nothing else has changed (aside from the duplicate spelling issue), and I'm not even sure if it works yet. eats, if you would be so kind to tell me if it's patched up, I'd appreciate it.
okay i'll try it out. get back to you tomorrow. I have 12 gigs of ram and i didnt notice until my pc started freezing; thats when i noticed it was at 6.3 gigs, which i know it shouldnt need that much haha...and the app just kept climbing so i killed it and everything returned to normal.