Markoz wrote on Jul 19^th, 2011 at 2:34am:

but it is still stuck on an endless sound loop - still playing the gun sound. There is a fix for the sound problem (not just the one I copied from your post, but all of them). Submit a ticket and you will be able to get the fix for that.

If you have a fix, why can't you give it to me? So, I have to somehow figure out how to enter a support ticket to fix a problem with a piece of software I just bought - but you can't just tell me how to fix it? Are we really going to play "I've got a secret"? Why isn't there anything in the documentation? Why isn't there a link to a patch? Why is it the first time I hear of this problem is here - and even then the answer is nebulous at best?


Quote:

Panel comes up blank. I pressed Shift+1 to bring up main panel, shift+2 to bring up HUD gauge, and shift+3 to bring up HUD background. I clicked the Master on the panel. Do a complete uninstall and registry clean (remove the CS Weapon entry from the windows registry). See KB #685 for details.

Ok, I don't like playing with the registry, but I'll give that a shot.


Quote:

If you still having the missing panels issue - A further problem that can occur is that the downloaded installer is faulty. Click on the link in the email to re-download the file and install it with the new installer.

Been there, done that.


Quote:

Is there any way to get a refund? Apparently, there's no support and no documentation. You can get the manuals from here: http://www.captainsim.com/products/w001/manuals.html

Yes, I received that. If only it worked like the manual said. Nothing to aid in trouble shooting, such as where files should go or what should you do if, say, the HUD doesn't appear or the sound gets stuck. Guess that's how software companies like this make money; making customers pay for support for buggy products.


Quote:

I didn't know I was paying $22 to be a Beta tester. It works perfectly for me (it always has) and many others. I have never had any of the problems that you are having.

Interesting, just above you referenced that there is a fix for the sound problem (sounds like someone else has had that issue at some point) and that there is this mysterious KB #685 that apparently someone else has had this problem as well.

Of course, it would still be helpful to actually point me to the answers instead of telling me there's fixes and I need to look for them (what do you think I've been doing for the past two days) and then saying "You're the only one with the problem."