Mad Catz Cyborg R.A.T and Keyboard v7 Auto-Profiler

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
D

Danny350

Honorable
Jun 10, 2012
27
0
10,530
Mad Catz Cyborg R.A.T and Keyboard v7 Auto-Profiler

Cyborg Auto-Profiler 3.1.7

http://cyborgautoprofiler.com/index.html

I recently bought the Cyborg M.M.O.7 mouse and love the product! But I noticed that they did

not include a feature to automatically swap profiles depending on the game or software

currently running! It isn't the most required feature but it just makes the operation of the

mouse and keyboard much smoother to not have to worry about changing profiles. So I decided to

go ahead and create a workaround for it and I present to you the Cyborg Auto-Profiler! The

features pretty much speaks for it self but here is some more info.




Cyborg Auto-Profiler is a lightweight, yet reliable utility designed to switch profiles for Cyborg input devices.

When the application detects that a set game or application is running, it will change the profile accordingly. or you can set HotKeys to switch to a specific profile. You can also set a default profile, which is activated when no set processes are detected. For R.A.T Mouse users it can change the DPI mode and Precision Aim Percentages with every individual profile allowing seamless transition and ultimate personalization. M.M.O.7 users can also change the LED colors with specific profiles.

Features Include:
-Supports all Saitek and Cyborg devices.
• Automatic switching of profiles when specific software are detected.
• Default Profile for devices when no set software is running.
• Hot Keys for swapping to specific profiles.
• You can choose from 2 types of Software detection.
• Change the DPI mode and Precision Aim settings for each profile for R.A.T devices.
• Change the LED colors of M.M.O.7 device for each profile.
• Launch profiles without ProfilerU Software running.
• Automatic Update option.

Supported Devices:
Cyborg Mouse R.A.T. 3.
Cyborg Mouse R.A.T. 5.
Cyborg Mouse M.M.O 7
Cyborg Mouse R.A.T. 7.
Cyborg Mouse R.A.T. 9.
Cyborg Mouse Contagion
Cyborg Keyboard V.7
Cyborg Keyboard S.T.R.I.K.E.7
Cyborg V.5 Rumble Pad for PC/Xbox 360
Cyborg F.L.Y.5
Cyborg Command Unit





Change Log:

Changes in 3.1.7
• Fixed: Error at software launch/settings.

Changes in 3.1.6
• Added: Support for RATm & MOUS9
• Added: Software now detects when a device has been plugged in or removed.
• Added: New Setting 'Clear Profile' This setting if enabled will clear the profiles on the devices if no process is detected. Default Profile will be disabled if used.
• Added: Software will now re-enable itself when exiting settings or profile settings menu if it was originally enabled.
• Added: Device Information Window in settings.
• Fixed: Issues in detecting some devices.
• Fixed: Start with Windows problem for some users.

Changes in 3.1.5
• Added: VBScript Scripting Support for when profiles are loaded or unloaded. For an example of its use. If you wanted to close 'uTorrent' when you was launching an online game you could use a script to do it with the 'Sub LoadProfile'. If you wanted to open 'uTorrent' after you exited the game just use a script on the 'Sub UnloadProfile'. I will include some sample scripts.
• Added: Preview option in M.M.O.7 LED Flow Settings.
• Added: Custom Color Dialog for LED Settings
• Changed: Improved 'Start with Windows' setting.
• Fixed: Graphics glitch with using enlarge setting with Windows.


Download:

https://hotfile.com/dl/159549266/f26dfbd/Cyborg_Auto_Profiler_1.0.1.zip.html


Please let me know any feedback, bugs, or request! Thanks! and I hope I helped make you enjoy

your Cyborg products a little more!
 
Solution
Painstouch
Yeap, thats looking pretty snazzy!

So far, its looking great as a small little program it is. There's really nothing drastically that has to change, so unless I find critical error, my feedback will be mostly of some small upgrades possible to the program.

Cheers!
Sort by date Sort by votes
EDIT:

Another warning showed up:

Auto.pr0 does not contain a profile for this device. The device has not been profiled.

Is this because we don't set actual process for the "default" profile?
 
Upvote 0 Downvote
Or is it because the actual process was running at the time of setting up profiles in Auto-Profiler?

I apologize for the post spam, but not having rights to edit my own posts sucks.
 
Upvote 0 Downvote
Last but not least, does Auto-Profiler catch up process names that end up with: "ProcessName.exe *32", aka, if they run in 32 bit mode on a 64 bit system? Would that explain the above error?


FINAL EDIT: Found out my problem; if you rename your own profiles inside the Explorer (F2 - new name), the profile itself will NOT be renamed ore recognized for either Saitek Software or your program. Solution is to open the said profile in the Saitek Profiler Editor and RE-save it with new name. This should do the trick.

Tedious, I know.
 
Upvote 0 Downvote
Dunno if it's just me, but the Auto.pr0 is not created automatically anymore in Auto-Profiler v2.0.
EDIT: Somehow, it appeared. But it did throw an error before the "Creating Auto.pr0 profile for you, make sure you make it Auto-Load" notification. Strange.


I also have a small suggestion, would it be possible to display somewhere currently loaded profile? Pop-up ballon, or inside your program, on the first window, below Enabled maybe? It's just that handy dandy stuff, nothing major.
Click to expand...

I messed up on the creation of the Auto.pr0 file. It is fixed now just redownload from the main post! Thanks for letting me know and sorry about that! and as you would mention I also though about that currently loaded profile and added it last night so it will be in the fixed version that you download.

Another warning showed up:

Auto.pr0 does not contain a profile for this device. The device has not been profiled.

Is this because we don't set actual process for the "default" profile?
Click to expand...


That was an issue with the first bug.

Last but not least, does Auto-Profiler catch up process names that end up with: "ProcessName.exe *32", aka, if they run in 32 bit mode on a 64 bit system? Would that explain the above error?


FINAL EDIT: Found out my problem; if you rename your own profiles inside the Explorer (F2 - new name), the profile itself will NOT be renamed ore recognized for either Saitek Software or your program. Solution is to open the said profile in the Saitek Profiler Editor and RE-save it with new name. This should do the trick.
Click to expand...

Renaming the profile will cause an issue with my software. It is possible I could make it so you can rename it inside of it if you would want that feature.

All the process name needs to be is the name you see, anything at '.exe' and past is not needed or worried about. As it states in the Read me do not be concerned about '.exe' or '*32'.

This patch should fix the issues! But again Thanks for working with me and letting me know!
 
Upvote 0 Downvote
This website is fukin retarded, it made me rewrite my message 3 times. IM SO PISSED>

Hello. I'm tryin to use this app, but it gives a Microsoft .Net framework error just as i double click it.
How can i check my .Net status? if its on or off, its installed correctly ....
I have .net 4 recently updated with the install of microsoft visual studio 2010.

Actually ive realized that the app does not automatically create auto.pro in my documents folder. First of all the path it searches on is in the Public user folder, not My user folder, so i changed it to mine, but it still doesnt create the auto.pro.
How can i change this?


Ok, i've got the hang of this program. I had to change the directory your program was searching in, C:\Users\Public\Documents\Saitek SD6 Profiles, maibe RAT9 has different from RAT7mmo, dunno. Also i had to create the Auto.pr0, which apparently is case sensitive, as in not Auto.PR0, but Auto.pr0.
It's really great, just what my RAT 9 needed. However, here is a problem i really think u should take into account.

First off, this program reads the task manager if i'm not mistaken, and if a process that u created a profile for is identified, then AutoProfiler loads that profile. BUT the problem is, that if 2 or more processes are identified, the AutoProfiler uses as 'Current Profile' only the last opened process. If u switch between profiles, the 'Current Profile' stays the same.

Ex:I have profiles for music, web browsing and game. If i open the programs in this order, music>web>game, then the last one being the game, the 'current profile' is the game on. IF i ALT+TAB out of the game(not closing it) and go to web browser, the 'Current Profile' is the same(game profile)
I think u understand where im going at, and if u said u created a program that "swaps profiles depending on the process that is currently running", you have to do it both ways :). I know its a lot of work to do this, but if u wanna do a good job, do it till the end.
I believe this can be done by using a code that reads the active window on the task bar.


Another problem, is if i open music program, then web browser, the current active profile is the one of the web browser.
If i open browser then music, the current active profile is still the one of the browser.

Same thing with the game. No matter which order i open the programs in, the current active profile is the one of the game. If i exit the game, its the browser profile, the if i exit the browser its the music profile.
This is retarded. May have some relevance to it in the task manager, but still is retarded.

So, if u will implement a code that will make all this go away, if i will be able to alt+tab out of my game and go online and the profile will change from the game's to the browser's, the u sir will have created a real full name auto-profiler and the guys from madcatz should consider hiring you :)
 
Upvote 0 Downvote
If you have .Net 4 framework installed you shouldn't be getting that message. Kinda odd...

So you want a feature to swap profiles for the current window in focus? I think I can add that, I have to go to work soon, but I'll get right on it when I get home.

As of now if you want your browser to be a higher priority than the game make the Game Profile lower on the list in Auto-Profilers Profiles. If your running a game then open the browser it will detect the browser is a higher priority and swap to it. I know thats not exactly what you want but it may help you in the mean time.

If I can ask what is the folder for your profiles if it isn't "C:\Users\Public\Documents\Saitek SD6 Profiles" or "C:\Users\Public\Documents\SmartTechnology Profiles"

But I look forward to more feedback and I hope to get your feature implemented very soon! Just check back and hopefully I'll have you version 2.3.
 
Upvote 0 Downvote
Not just for me man :)) everybody will be relieved.
My folder is as i said C:\Users\Public\Documents\Saitek SD6 Profiles.
I have a new problem. every time i reboot win, i have to recreate the auto.pro, somehow it keeps getting deleted. Probably because autoclicker never created it on its own in the first place. If u could look into that, that'd be great.
 
Upvote 0 Downvote
Thats all very confusing! Thats the default location it should be looking for so it shouldn't have any problems.. The program will delete Auto.pro often to change the profiles but it shouldn't stay deleted for longer than a second. I need to understand why the program isn't creating the Auto.pr0 file for you itself. Do you get the message that says it is creating the 'Auto.pr0' file? and it just doesn't appear? If you help me I'll get to the bottom of this. Is there any messaging software you use so we can talk more quickly?
 
Upvote 0 Downvote
Well I've added the new 'Active Window Mode' So far it's working pretty well! I would prefer if you could test it for me first before I make it an actual release. You know to make sure the kinks are out of it. I'm going to PM you a private download link after we talk more about this 'Auto.pr0' file issue you are having, I really want to crush that bug before an actual public release.
 
Upvote 0 Downvote
y.mess if u want, . No, i dont get any message telling me it wants to create smthing. just doubleclick and str8 to the first window of the program.

Aside from that, it keeps giving me an error that it cant find itunes.pro which i created just to test your program, but then deleted it completely from everywhere, but apparently it still asks for it.

u gotta send me a different kit.
 
Upvote 0 Downvote
Thats extremely odd. I think this might have something to do with the Profiles Directory having an issue. If the folder doesn't have the 'Auto.pr0' that message should come up every time it starts. If you deleted the profile itunes.pr0 outside of the Auto-Profiler when it launched it should have given you a message saying it couldn't find it and it has been removed from your list. You are using version 2.2 correct? Anyways I've added you on Yahoo and I hope I can catch you on there. I'm going through the code to see if I can find any of the bugs on my own. Also you said that it was searching for your public folder and not your user folder and said your actual path is 'C:\Users\Public\Documents\Saitek SD6 Profiles.' That folder is the public folder, the user folder would be like 'C:\Users\YOURNAMEHERE\Documents\Saitek SD6 Profiles.' Just trying to get some clarity.
 
Upvote 0 Downvote
Updated to 2.3.1 with new Active window mode! Active window mode changes profiles depending on what program you are using. Now supports multiple processes for one profile. Also you no longer need the 'Auto.pro' file it changes profiles without it now!
 
Upvote 0 Downvote
I just got a mmo7 mouse and love it. I would love it more if I can get your auto profiler working 😉

When I enable the auto profiler. It correctly detects the process and displays the correct profile name in the UI. It also launches the cyborg profiler correctly. But it won't actually make the profile active.

I'm using the latest mmo7 driver, cyborg profiler, and auto profiler 2.3.1. Do you have any idea why it's not working?
 
Upvote 0 Downvote
I think I may know the problem. Someone recently had the same problem because I forgot to add this into the Read Me! It was my bad but try it out and let me know if it helps you.

"You must select a startup profile for the device you are using! Just right click the cyborg system tray icon like you would normally swap a profile and right click any of them and select 'Set as Startup profile' If you do not it will not work!"

Be sure to restart the Cyborg Auto-Profiler before trying again.
 
Upvote 0 Downvote
Hello I just found your tool (Cyborg Auto-Profiler 2.3.5) and am really forward to using it.
But when I start it I get the following error message:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at eval_b.eval_h()
at eval_b.eval_v()
at CyborgAutoProfiler.frmAutoProfiler.eval_q(Object A_0, EventArgs A_1)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
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.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.544 (RTMLDR.030319-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Cyborg Auto-Profiler
Assembly Version: 2.3.5.0
Win32 Version: 2.3.5.0
CodeBase: file:///F:/Appz/Cyborggaming/MMO7/Cyborg%20Auto-Profiler%202.3.5/Cyborg%20Auto-Profiler/Cyborg%20Auto-Profiler.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.544 built by: RTMLDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.450 built by: RTMLDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.560 built by: RTMLDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.568 built by: RTMLDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.450 built by: RTMLDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.468 (RTMLDR.030319-4600)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Saitek.Devices
Assembly Version: 7.0.17.2
Win32 Version: 7.0.17.2
CodeBase: file:///F:/Appz/Cyborggaming/MMO7/Cyborg%20Auto-Profiler%202.3.5/Cyborg%20Auto-Profiler/Saitek.Devices.DLL
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------

************** 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.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

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.
 
Upvote 0 Downvote


Well I have a few questions. What device are you using? Does it create the default settings before crashing? Have you tried running as administrator? Could we continue this conversation in my e-mail? If you would send me the reply to this message to CyborgAutoProfiler@gmail.com

Thanks we will get this resolved.
 
Upvote 0 Downvote
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Saitek.Devices.Device..ctor(String link)
at Saitek.Devices.HidDevice..ctor(String linkName)
at Saitek.Devices.DpiDevice..ctor(String linkName)
at CyborgAutoProfiler.frmAutoProfiler.eval_h(Object A_0, EventArgs A_1)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Cyborg Auto-Profiler
Assembly Version: 3.0.0.0
Win32 Version: 3.0.0.0
CodeBase: file:///D:/Programs/Cyborg%20Auto-Profiler/Cyborg%20Auto-Profiler.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.269 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.278 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.282 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.237 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Saitek.Devices
Assembly Version: 7.0.17.2
Win32 Version: 7.0.17.2
CodeBase: file:///D:/Programs/Cyborg%20Auto-Profiler/Saitek.Devices.DLL
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------

************** 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.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

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.
Click to expand...

Cyborg RAT 7
 
Upvote 0 Downvote
Hello Foekie. Could you please tell me if it detects your device at all? Like in the main menu does it show a R.A.T.7 Icon? or is it just blank? I may need to send you a copy that would give me a more exact location of the error. If you could reply to this message with the info I asked about to my support email at CyborgAutoProfiler@gmail.com

Thanks and I will do my best to get this working for you!

EDIT: The issue was discovered for anyone else who may get this issue. The problem was the drivers. Do not have windows install your Saitek/Cyborg device drivers. Please only use the driver installation software provided by Saitek or Cyborg themselves.
Click to expand...
 
Upvote 0 Downvote
I keep getting this randomly in v 3.0


ee the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OverflowException: Arithmetic operation resulted in an overflow.
at CyborgAutoProfiler.frmAutoProfiler.eval_h(Object A_0, EventArgs A_1)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
Upvote 0 Downvote



May I ask what device you are using? Does the software work normally if you press continue? When the error occurs does the DPI meter beside the device icon change if you change your mouses DPI mode manually? If you could please respond to this post at my support email CyborgAutoProfiler@gmail.com

Thanks!
 
Upvote 0 Downvote
Running Cyborg Auto-Profiler 3.1.1 on Windows 8 Pro with the latest Cyborg drivers and software (Driver Version 7.0.20.0; Software Version 7.0.23.0) and a MMO 7 mouse. The program works, detects the right processes and displays the right profile changes, but it will not register the change with the Cyborg software. I have set a startup profile and the icon turns green, however as soon a I run the Auto-Profiler the icon changes to deactivated (the same as clear profile) and it will not activate to green on changes for different processes. I've also noticed that selecting a profile in the Profiles menu of the Auto-Profiler will set the icon in the Cyborg software to green, activating that profile, but as soon as the Auto-Profiler is Enabled the icon is set to clear again. In not quite sure what other details I could provide since there is no error shown so hopefully I made some sense and you could figure out what might be causing this.

Also, but this is quite a minor thing, the Start with windows option does not work in Windows 8.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom