itch.io

I ran out of steam in November last year so I'm a bit behind schedule unfortunately.
But I'm going to do my best to finish the early access build for v0.6 this month so the public release can go out at the end of march

Blessed rings don't do anything for now. They're technically one extra step removed from cursed, but since there isn't anything that can curse the player's items yet it's not very useful.

Recruit allies and encounter a succubus/incubus/nightmare/lava siren. The allies will get seduced and you'll get the cinematic.

Android export is extremely experimental for the .net branch of godot, and I haven't been able to get it to work. But if a future update adds android as a stable export option, then sure.

Seems to work fine, maybe the itch servers were struggling when you tried downloading the game.

I believe Android support for the dotnet version is still being worked on by the Godot developers. But I have no idea when it will be added and I also have no idea if the game will even work on Android yet since I can't test it.

I have no idea really.
Googling "godot hostfxr_get_runtime_delegate failed" returns that it has something to do with .NET though.

Sounds like there is an issue with shader compilation, did you try the dx12 version?

You can check the log for error messages at:
%appdata%\Godot\app_userdata\HardStuck\logs

It will probably be a while. Since the game uses C#, and Godot's Android export for C# projects is still considered highly experimental.

With the changes to itch payments for NSFW content the patreon is really the only way.

Don't click any links to patreon in the comments though.
There is a link to the real patreon in the description at the top of the page.

The game can run using opengl but it isn't really supported as the game relies on a bunch of the newer vulkan and dx12 features for some of the shaders. In opengl mode there are a lot of graphical issues but the game should be fully playable.

You can launch the game in opengl mode from the command line / terminal with the "--rendering-device opengl3" flag:
HardStuck.exe --rendering-flag opengl3

The windows versions require either vulkan 1.4 or dx12 support.

The native linux version only supports vulkan 1.4.

Not a whole lot, the entire game is 468 MB and uses around 600-800 MB when running.

Sorry, I completely forgot about that. I've added it to my todo list.

Kobold one is probably bringing an ally kobold through the TV and interacting with the bed. The only way to get two mimics is for the room with three chests to appear.

In the early access build? There's a hotfix for it on Patreon.

Thanks for letting me know about the typo.

Some statuses like the possessions are cleared when looping since there isn't a way to get rid of them through gameplay in the public build.

The Kobold scene might be the real world one, bring the ally kobold through the tv on the starter floor and interact with the bed.

If your pc can't play either version you could try running the game from the command line using the following command:
HardStuck.exe --rendering-driver opengl3

The opengl mode has a lot of issues with lighting and color but the game should be playable even on older hardware.

Altars let you test if an item is blessed or cursed before equipping/using it.

There was an old bug that I believed was fixed where if the game starts on a very low framerate the boobs would shoot off into space and stay there.

I'll take another look at it and see if I can find something that might be causing it.

The cum is rather demanding of hardware, if you're using the manual camera and zooming in on if then it would strain most mid range gpus.

The games animations are all 16 frames per second without any interpolation between frames.
The snapping between animation frames gets more noticeable the closer you are to the characters.

Or do you mean the games actual framerate?

There are cinematics for allied kobold/goblin/frank and the feminine monsters.
If you press z or left mouse button on a locked cinematic a text box will pop up describing the monsters that take part in it.

Try updating your gpu driver (adrenalin software).

One of the recent driver updates broke most godot games using vulkan, I believe it affected cards older than the 7000 series but I'm not entirely certain. Or you could try the dx12 version.

The update scheduled for next week will include a new feature for modding audio, so all cinematics will be unlocked in a new debug mode.

Sorry about that, I changed a bunch of stuff when implementing the lava siren and nightmares and forgot about the male on male tags.
I'll have it fixed in next weeks public release.

The unlocking of the female version is intended though, since it's essentially the same cinematic they now share the same id.

It seems that a lot of users with intel integrated graphics have a hard time getting the game to run.

You might have more luck with the dx12 build.

Which model? Laptops usually have a model name and number like "SuperBook15-ec8329".

It might be written on a label on the bottom of the laptop.

According to the spec sheet, it's from 2013. So I don't think you'll get the game running great on it.
It also looks like it has issues with DX12 and newer vulkan games.

If you really want to play the game, you might get it running in opengl mode. It's not really supported and has a lot of graphics issues, but it might be an improvement judging by your screenshot.

With the game folder open, type cmd in the address bar to open a command line prompt at that location. Then type the following in the command line window:

HardStuck.exe --rendering-driver opengl3

Might be a gpu driver issue. What gpu are you using?

Would need more information to help you.
Which version of the game are you having issues with?
What are your computers specs? cpu, gpu, operating system and so on.

The game lets you add boobs to the incubus and male lava siren / nightmare enemies at the customization mirror, which is kinda futa adjacent.
I don't think the current main character will get a penis option though, her animation rig wasn't made with it in mind. But another playable character might.

If it looks like Z-figthing it's something I'm looking into.

It's caused by the bounding spheres getting different lighting.

Those specs are fairly close to mine, and should be overkill for this game. Try starting from scratch by deleting the "shader_cache" and "vulkan" folders at the following path:

On windows: %appdata%\Godot\app_userdata\HardStuck\

On linux: ~/.local/share/godot/app_userdata/HardStuck/

Also delete the override.cfg file in the game folder, this file stores all the startup values for the settings menu.

The amd radeon drivers recently broke most Godot vulkan games, but they fixed it in a recent update.

I think your card might be among those that weren't affected but it wouldn't hurt to keep the drivers up to date.

Sorry, I deleted your comment for containing links.
As for your question, the game already has most of them.

According to the iris xe spec sheet it only has support for Vulkan 1. Which might be too low for the game, I'm not sure.

You could try running the game from the command line and see if any error messages show up.

What model gpu do you have?
You could also try to run the game from the command line, there might be an error message there that could help figure out what the problem is.

Deleting the "shader_cache" and "vulkan" folders might fix the vulkan build.

On windows the folders are at: %appdata%\Godot\app_userdata\HardStuck\

On linux the path is: ~/.local/share/godot/app_userdata/HardStuck/

Have you tried the vulkan version?
The dx12 build can be a bit hit or miss.

The third line in the generated template tells you to rename the text file to "Translation.txt".

As long as the file is in the same folder as the games' executable it will automatically load when starting the game.

Or you can reload it from the same menu that has the button to generate the template.

The RID leak things only happen when exiting the game. So everything looks normal.
The flickering screen might be a driver issue. Are you using the dx12 build by any chance?