Mubox (Legacy)

Currently, Mubox is distributed via a ClickOnce deployment. In the past this allowed me to rapidly deploy fixes and updates to users without having to go through the process of generating and uploading an installer for every version. To date, there ... [More] have been about 70 releases since going public with Mubox. I would like to move away from ClickOnce for two reasons: 1) To avoid the bug-hell that occurred with the 1.3.0.36 release, which left everyone unstable for at least 3 days.2) To give users the ability to pick-and-choose a specific version that works best for them. So my question to everyone is, what would you prefer? Should I continue with the auto-updating ClickOnce deployment? If you dislike the auto-updating ClickOnce model, and would prefer a versioned download, would you want an installer or a ZIP archive? Mubox doesn't require an installer, per-se, but some people find having to unpack a ZIP something undesired or like to see their installed programs appear in their regular places (Programs menu, Add/Remove Programs, etc) Personally I don't care, and if I don't get any response I will likely discontinue the ClickOnce deploys and instead begin providing ZIP archives with the version number in the filename. Downloads will remain the same, that is, you will have a single Download Page for 1.1, 1.2 and 1.3 series releases. Versioned downloads will appear on their respective pages, thus, on the 1.3 Download page you would find the latest release build, as well as a few historical builds for past releases for those who don't want to upgrade, or who find problems in the latest versions. Along with this change I will be publishing downloads for the following versions: 1.3.0.12 - Introduction of Junction-based Game Isolation, previous builds made a full copy of your game to isolate the files, I won't be providing an earlier build for 1.3. This release pre-dates the Latency indicator in the client tooltips in the server ui, and lacks fixes to many bugs. It is still very usable.1.3.0.35 - many bug fixes vs the .2x releases, this is the last-known-stable release prior to major refactors to the input handling in both client and server code.1.3.0.52 - (current) Includes major refactors to input handling to fix features which have been broken since 1.3.0.11, the focus on 1.3.0.36 to present has been to correct known bugs and misbehaviors for multiboxers that run all their toons on a single machine, with a single desktop. Thoughts?   [Less]

multiboxing with 2 clients on the same PC. I Use Ventrilo For Guild Speaking, but any hotkeys do not work while in game, also when using my mouse on the main screen, when clicking, its like the button is stuck in, as in the camera is always on free ... [More] rotate, also keys seem to stick, when pressing w to move forward, its like it is stuck pressedComments: ** Comment from web user: SEWilson ** I did not verify the mouse/keyboard "stuck" issues, I was only able to repro/confirm the issue with global hotkeys. I run 5 locks on a single machine, it pushes my hardware pretty hard, so I don't think the issue is performance related. There must be a sequence of events that I have to perform to reproduce the issue. [Less]

multiboxing with 2 clients on the same PC. I Use Ventrilo For Guild Speaking, but any hotkeys do not work while in game, also when using my mouse on the main screen, when clicking, its like the button is stuck in, as in the camera is always on free ... [More] rotate, also keys seem to stick, when pressing w to move forward, its like it is stuck pressedComments: ** Comment from web user: SEWilson ** I verified the issue last night, global hotkeys are non-functional. It looks like I will need to introduce a new keyboard configuration dialog that allows the user to "opt out" specific keys, this would allow the user to configure hotkeys which need to go to the OS instead of Mubox, to be handled by apps such as Ventrilo, WeGame, etc. [Less]

I posted this in another issue but it was marked fixed(mouse wheel works now)the 4 and 5 buttons still don't work, on the local machine or the remote machine.To use them locally, i have to hit Scroll Lock, to use them remotely, i have to hit a kvm ... [More] switch i have setup to switch the mouse to the second computerI do run 2 machines with 1 client per machineComments: ** Comment from web user: SEWilson ** Can someone suggest a good wireless mouse with 4th and 5th button? [Less]

Keyboard Auto-Repeat was disabled to correct an issue with high-latency (and high-load) scenarios, the problem was that the key-repeat events from Windows would broadcast to all clients. For classic-multiboxing this was not so much an issue, however ... [More] , users attempting to run 5+ clients on a single machine were reporting "key loss" and "input lag". The cause was a backlog of "repeat events" from Windows down to the client.In a future release, the auto-repeat functionality will be re-enabled.Comments: ** Comment from web user: SEWilson ** If someone "needs" this behavior, I can implement a workaround that will let users enable/disable key-repeat. Otherwise, I would prefer to defer this issue until I can streamline the networking code further. [Less]

Keyboard Auto-Repeat was disabled to correct an issue with high-latency (and high-load) scenarios, the problem was that the key-repeat events from Windows would broadcast to all clients. For classic-multiboxing this was not so much an issue, however ... [More] , users attempting to run 5+ clients on a single machine were reporting "key loss" and "input lag". The cause was a backlog of "repeat events" from Windows down to the client.In a future release, the auto-repeat functionality will be re-enabled. [Less]

The 1.2.0.6 client no longer behaves properly when connected with the 1.3.052 serverAlt tab Switches both the window and the clientKeys are sent twiceAlso with the "Enable Input Captured", keys don't repeat, ie i have to press backspace for each ... [More] char, i can't hold it down.Comments: ** Comment from web user: SEWilson ** Opening separate ticket for the Auto-Repeat issue, I intend to bring this back in the 1.4 release. [Less]

Need to profile the lock times fo inputQueueLock and figure out what is holding the lock for so long. 1.3.0.51 contains a work-around that will result in input lag, but should function correctly.Comments: ** Comment from web user: SEWilson ** It's ... [More] worth noting that although the switch fails, input is still directed to the desired window. Thus, this is only really a problem for users that multibox a single machine and rely on alt-tab and the mouse for general gameplay. [Less]

Need to profile the lock times fo inputQueueLock and figure out what is holding the lock for so long. 1.3.0.51 contains a work-around that will result in input lag, but should function correctly.Comments: ** Comment from web user: SEWilson ** I've ... [More] noticed that this issue mostly occurs when my CPU use is at or close to 100%. I pulled up a hi-res process monitor (ticks 10 times a sec) and see that Mubox is spiking the CPU when switching clients. When this happens, the switch appears to succeed. When the switch fails I noticed that Mubox does NOT spike the CPU. Users with high-end hardware, or users who are not running enough clients to load their system, should not experience a problem switching clients. If you are experiencing problems switching clients and it doesn't appear load-related, please provide some information so I can look into it. [Less]

after much work just trying to get it to compile, i got toError 1 Metadata file 'C:\Mubox.Client\bin\Debug\Mubox.Client.dll' could not be found Mubox.QuickLaunchError 2 Metadata file 'C:\Mubox\bin\Debug\Mubox.dll' could not be found ... [More] Mubox.QuickLaunchError 3 Unable to get MD5 checksum for the key file "..\..\..\mubox_private.pfx". Could not find file 'C:\mubox_private.pfx'. Mubox.ClientError 4 Unable to get MD5 checksum for the key file "..\..\..\mubox_private.pfx". Could not find file 'C:\mubox_private.pfx'. Mubox.Serveri know i don't have your key, but i have been through every file, every csproj, the sln, even the .resx and .settings files. There are no refrences to a "..\..\..\mubox_private.pfx"am i missing something in removing the key from the project?i guess i could just create new projects and copy/paste the cs and xaml filesComments: ** Comment from web user: SEWilson ** I checked in changes yesterday which may resolve this issue, if you get-latest on the source tree the manifest signing has been removed from all but the QuickLaunch assembly. I also removed all the assembly-signing settings.As for the QL app, you should be able to create your own "Test" cert, there is a button in the UI to do it.My primary workstation crashed over the weekend, lost everything (HDD won't recognize) and I ran into the same problem as you. Surprisingly this hasn't ever happened before. It looks like it was caused by converting the Server and Client assemblies into DLL projects instead of EXE projects when work on the 1.3 series began. I had to convert the project and then reset them, then convert them back. Appears to compile without much complaint now. [Less]