I just installed the game and tried to run it. The game opens with the OPTIONS window popped up, and the rest of the window behind it is fogged-over. I cannot exit this dialog! I can press the "X" button with the mouse, but nothing happens. I've tried the ESC key, Enter key, spacebar, but nothing dismisses this window.

I can select RESET ARCADE RUN or RESET CAMPAIGN and it warns me that I already have a "saved game" that this will remove, but I say OK. The screen clears, a little rotating gear displays a cute little message, and then... The OPTIONS window pops back up again! HELP!!!

UPDATE: just installed this on a totally different computer, and have EXACTLY the same problem! The computer above was Windows XP SP3, the other computer is Windows 7. When I press the "X" at the bottom of the OPTIONS panel, I can hear a sound effect like a metallic "clank", and I can see that "through" the hazy grey background that there are now new options on the "desktop", such as Arcade and Campaign. I can click those... BUT THE OPTIONS WINDOW IS STILL OBSCURING most of the game window! I thought for sure this would go away if I installed on a different computer. Is no one else seeing this? Is there a "secret" to dismissing popup dialogs?

Sure, here you go. Same exact thing on both computers. Notice this is not the "opening" screen in the background, which demonstrates that I was able to click the "Arcade" button through the hazy background, but the Option window and grey covering obscures absolutely everything. Thanks! By the way, I added a bunch of OS-specific info for my computers, including an Application Event Error from Win 7, in my other topic... https://www.gog.com/forum/general/release_skyshines_bedlam_redux_685e9/post71

... but you probably saw that by now. Thanks for looking!

BY THE WAY... there are two replies on there, with different info, so be sure to look at the next reply (from me) as well.

Judas, I just figured out what the problem is on my computer. But it's not pretty.

The two computers I have? They're connected via a KVM switch, an ExtremeX miniview 4-port switch. Thus my mouse is shared between these two computers. On a total wild hunch, I tried connecting a different mouse directly into the 2nd computer (Windows 7) and that works! Well, I'm able to dismiss the Option window, and get to the main game screens!

But does that mean I need THREE MICE to run this game on two computers? I can say I have never EVER heard of this problem before, but that seems to be it. I don't know what "mouse codes" are being delivered by the KVM switch, but every other game/utility/app seems to run fine with it. I see that Bedlam is using both Flash and AIR... maybe they could somehow "widen" their event hit list to look for several different LMB button click events?

I have a third computer, a laptop running Win7, that I could try it on... but I don't use it for gaming, but I could try it. I hope Bedlam will put this in a patch and do an update sometime. It just seems weird that I need to reach for a different mouse just to play this one game. :(

Maybe you could pass this info along to them as well? I wonder if there's a utility that would show "mouse click events" so I could test the different mice and show Bedlam what the differences are?

One last comment... why is this ONE WINDOW (Option) the only one that doesn't respond to the LMB click on its X button? All the other windows I can click (through the grey background) work, including the buttons on the Option window itself!!

Thanks.

SOLVED!!! see Update #2 below for the final details.

For the record... I figured out WHY this is happening.

These two computers are sharing a KVM 4-port switch, so I use the same mouse and keyboard for both computers. Using the KVM'd mouse, I can click all the buttons on Bedlam that I can see so far (some are very hazy through the grey background while the Option box is open). But it doesn't trigger a full event for the Option "X" button to close down the window.

To test this hunch, I connected a separate wireless Logitech mouse to my Windows 7 box, disconnected the USB cable with the mouse/keyboard connection from my KVM, and with just this standalone mouse as the ONLY mouse on this system, the game works! Well, I can dismiss the Options window and see the rest of the game!

GOG replied to my issues and sent me to the developer forum for Bedlam... this isn't something GOG could/should be able to fix. It could be a simple oversight in the event handler for this single "X" button, since all the other buttons trigger events properly, so I'm hoping that's the case.

Weird, huh? :)

UPDATE: turns out, this isn't quite the whole picture. The real culprit seems to be the actual mouse I'm using with the KVM switch... a ROCCAT Tyon mouse. No matter whether I connect this mouse directly to either computer, or using the KVM switch, the game refuses to allow me to close the Options window. It is a configurable mouse, but you can't reconfigure the LMB or RMB! Those functions are "fixed", which makes sense. So I have no idea why Bedlam doesn't like this mouse.

UPDATE #2: but now I do! :) It turns out, the ROCCAT Tyon Mouse has a "hidden gamepad mode" that I did not know existed! If you turn off this gamepad mode in the Windows Device Manager, it will not interfere with Bedlam and I can play the game!

You can right-click the Windows Computer icon from the Start Menu and select Manage to bring up a console. This works in either OS. Find the Device Manager and click it. Now on the list of computer resources on the right find "Human Interface Devices" and expand the list (click the little "+" sign). Find the "HID-compliant game controller" on the list, right-click on it and select Disable. That's it! Now if you have an actual gamepad, you might have several entries of HID-compliant game controllers, like I also have an XBOX controller. Don't disable that one. It won't hurt to disable one, try Bedlam and see if you disabled the correct one, and if not, re-enable the one you disabled, and disable the other one! I did that to find the one belonging to my ROCCAT Tyon Black mouse, and immediately I could play Bedlam with no problems!

Thank you sir, this proved to be the solution for me as well.

It's strange that the Tyon was the issue, but now after disabeling the gamepad mode, Bedlam does work.

Wow, I'm surprised anyone on Earth had this problem besides myself, but I'm really glad to help! It took me several days of going down the "wrong path", as you could tell from some of my entries. I hopefully left out a lot of other things I tried that didn't work. :)

In my Googling, I eventually ran across a totally unrelated website about the Tyon that gave me a "clue" that it was actually two controllers in one (mouse + joystick). I wonder what Bedlam is really complaining about? I have another USB joystick connected to my computer, but Bedlam doesn't complain about that one?

I wondered if it's because the Tyon's "joystick implementation" is really incomplete. For example, the paddle above your left thumb is EITHER the X axis OR the Y axis, but not both at the same time. Then there's the matter of missing joystick buttons. I found that I could assign some of the buttons on the mouse to DirectX inputs (using the ROCCAT Talk program), in fact all 12 DX inputs can be assigned to different buttons on the mouse. I wondered if I did that, would Bedlam quit complaining, you know, if it thought the Tyon was a "complete DX joystick"?

Because there may be people out there that don't want to totally disable the flappy joystick paddle on their Tyon just because Bedlam doesn't like it. But I don't care... I didn't even know it had this feature! :) Maybe some other person will stumble along with a less "drastic" solution than totally disabling the joystick, but I'm happy with it, and glad it worked for you!

I'm not sure about the implementation that Roccat uses with the paddle, but it doesn't make sense at the moment.
The paddle overhere is assigned to "Alt" and "Ctrl", so it should be a digital signal, that mightbe interpreted as analog.
Looking in the settings, the paddle has an option for D-input and X-input, of witch none are activated at the moment.

After I disabled the "gamepad" in the device manager, the functionality didn't change (flap still does the Ctrl/Alt function).

I've had no issues in other games or programs, but I might try a bit with The Banner Saga, because that uses the same engine.

*edit:

After enabling the gamepad mode I started Bedlam again, and indeed it did stop responding in the options menu, just as before.

The Banner Saga goes nuts in the start screen because it tries to select a game controller and can't find a proper one that responds.

Disabling the gamepad mode in the device manager causes the games to behave properly.

Mightbe it's an issue that lies with the game engine, or the gamepad implementation Roccat uses for the Tyon (Race the Sun also behaved bad, but I didn't test it now.)

I have the exact same issue. Will try your solution now :)
Thanks