E3 Demo Bug/Glitch Reports

I managed to get in the game by watching a youtube video to see what the settings menu looked like and blindly moved it into Windowed mode and applied it. Now I can see!
Oddly enough though, does the 1280x720 setting not make it truly 1280x720 when entering full screen? I can switch my computer's resolution to 1280x720 just fine but trying to play the game fullscreen in that resolution gives me that same Input Signal Out of Range error.

Either way, Windowed mode will suffice for now.

I hope this is teh right place to say this : Just did the demo (great gameplay, swift movement, the game lagged only at one point ; in the room (not the boss room) where the boss monster blows the side of the ship and 3 tentacles squid demons attack... it lagged from the moment I entered the room to when I left it.)

Only bug I really had : I could not hit enemies (objects I could) until the first armored guy with a flail... and after that I went backward and could hit enemies with my attacks. This made the game feel WEIRD at first because I was wondering when I could face enemies I could wound/defeat... would there be a scene were Myriam wakes an ability to hit those demons? was I supposed to die and then I would be raised back as a "half cursed demon slayer"? Then I remembered it was a demo to test the game, so I realized it was a stupid bug! And then it was gone!

I can confirm this also happens with the final retail version of the Oculus Rift (DK1). It might have something to do with the way the Unity engine is initialised.

I still can't seem to get the game to even start. Is it my computer? Please let me know. Here's my comp specs:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 3 Build 2600
System Manufacturer TOSHIBA
System Model Satellite U205
System Type X86-based PC
Processor x86 Family 6 Model 15 Stepping 6 GenuineIntel ~1596 Mhz
BIOS Version/Date TOSHIBA Version 3.70, 6/4/2007
SMBIOS Version 2.4
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"
Time Zone Tokyo Standard Time
Total Physical Memory 4,096.00 MB
Available Physical Memory 1.62 GB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB

The error I get is that it's not a valid win32 application.bloodstained error.bmp (1.05 MB)

Thanks.

     No thanks, I'd rather not kill a perfectly good computer with upgrading it's OS. Better if I can to just save for a new laptop with a new upgraded OS.

Anyway, thanks for the input.

I was trying to see if they had it set to work with XP like other steam games. But I guess they didn't consider that when they did the demo.

When Miriam has her back to a wall and uses backdash, she will clip into the wall almost entirely:

Greetings,

So I've found that with the rapier particularily from time to time the attack hitboxes don't seem to register. this is more frequent with the Seama. I have to get fairly close, like distance with the kung fu boots (can't remember it's name), till it fully registers the hitbox and deals damage to the enemies. I haven't found anything in particular wrong with the boots hitbox registration though, but I did happen to get hit by the boss while attacking at a good enough distance with the boots. I'm not sure if it had a hick up but I figure it be worth mentioning.

I'm currently on my laptop Asus Zenbook
(here are it's specs)
Intel Core i5-5200
Ram 8.00GB
Windows 10 (64-bit)
The model is UX305LA Signature Edition


Edit (1)
So I do recall some buttons on the keyboard that probably aren't supposed to be active. The key 'I' pulls up the inventory/menu but I can't close it after that, I have to press 'B' (can open and close with 'B'). The key 'O' opens the map but I can't close it at all for some time. I'd have to press 'N' and 'B' a few times and it either closes the map or opens inventory and which allows me to resume the game. Pressing 'N' allows me to open and close the map but not when I press 'O'.

One time the demo went to a black screen and froze, when I was backing out of the inventory screen, after unequipping my sword. It never did it again though, so might've just been a fluke.