alt+enter didnt work but ctrl+enter does i do have to have the mouse over what i want to click. a restart lets me use the mouse now.
Unreal Engine Cock Hero [v0.02.1] [CockHeroDev]
- Thread starter Cock Hero Dev
- Start date
Sylith
Newbie
- Jul 1, 2018
- 26
- 33
This game is great and really enjoy the base content in it already. The game is fun and I really like the art and UI style. The demo packs were easy to install too.
One thing I'd like to ask, can you add a way to change resolution in the settings? I have an ultrawide monitor and the game by default tried doing a 32:9 scaling and everything gets messed up looking (images are super zoomed in trying to fill the screen). To fix this I pressed ~ to open the console, and entered "r.SetRes 1920x1080w" (without quotes) to force it to a standard 1920x1080 windowed mode. Then press ~ key 1 or 2 more times to close the console.
Hopefully this helps anyone else that has a similar issue or wants to freely change the window size/scale exactly.
One thing I'd like to ask, can you add a way to change resolution in the settings? I have an ultrawide monitor and the game by default tried doing a 32:9 scaling and everything gets messed up looking (images are super zoomed in trying to fill the screen). To fix this I pressed ~ to open the console, and entered "r.SetRes 1920x1080w" (without quotes) to force it to a standard 1920x1080 windowed mode. Then press ~ key 1 or 2 more times to close the console.
Hopefully this helps anyone else that has a similar issue or wants to freely change the window size/scale exactly.
Oh, maybe Intiface will do the thing, I remember there was a way to connect OSR to intiface via serial.
Fair enough. I know Unreal is a bitch to get to run without making PCs into nuclear reactors.
Hope it works out!
Venca
New Member
- Aug 10, 2017
- 4
- 18
For anyone else having their GPU broken in by this game, limit the FPS to something reasonable, like 60, then the the game will show your graphics card some mercy.
Really enjoy the game you've made here, dev, but man, you're not going to do yourself any favors in debunking the malware allegations by immediately loading 80% of 3D and 40% of async compute queues (what is it even using these resources on?) The discrepancy between what resources this type of game should use and actually uses is jarring even to a layman like me.
Really enjoy the game you've made here, dev, but man, you're not going to do yourself any favors in debunking the malware allegations by immediately loading 80% of 3D and 40% of async compute queues (what is it even using these resources on?) The discrepancy between what resources this type of game should use and actually uses is jarring even to a layman like me.
- Aug 31, 2018
- 171
- 479
working on getting this figured out < 3 - I agree the performance is a bit heavy for a 2D game
- Aug 31, 2018
- 171
- 479
- Sep 26, 2018
- 3,343
- 3,288
emothive
New Member
- Oct 28, 2022
- 13
- 17
bro really thinks he is smart by saying this lolNope why shut i switch to a bad system like 10 or 11?
Hope game get on linux soon then.
By the way why shut i install a virus on my system like win 10 or 11.
emothive
New Member
- Oct 28, 2022
- 13
- 17
Cock Hero Dev Amazing update! Better than I expected. I guess this game is one of the few that I don't mind having CG AI.
Since there's some talk about intiface and lovense devices being unresponsive:
Direct bluetooth connections via intiface should be far more responsive, however it's also important to note that while in theory most bluetooth devices should be able to handle a lot of commands per second they for some reason don't. It all depends on the quality of bluetooth modules they are using and a lot of toys use cheaper ones. And even 2 of the same toy can differ regarding bluetooth quality.
The most important thing to keep in mind in the dev side of things is to not overwhelm the device with commands, otherwise it will struggle to keep up. This means limiting the rate at which commands are sent and optimizing them, aka skip the command to vibrate at 70% when the device is already doing that.
For vibrating devices I have found that a minimum time of 0.2secs between requests is fine for most toys. In another beat based game I modded I used the following approach when triggering a beat:
- get the time until the next beat and calculate an intensity based on that. I used an exponential function that gave me 100% at 0.2s, 50% at 0.5s and 20% at 0.8s.
- skip if the intensity is the same as the last one I sent to the device
- if the next beat is in less than 0.25 secs just send the command, otherwise spice it up a little. instead of sending the calculated intensity I increase it by a third of the missing intensity and hold it for 0.2secs before returning to the regular intensity. in simple terms, if the original is 10% then 90% are missing. a third of that is 30%, so I send 40% and reduce it to the original amount of 10% after 0.2 seconds. It creates a noticable bump when beats hit for better tactile feedback.
Direct bluetooth connections via intiface should be far more responsive, however it's also important to note that while in theory most bluetooth devices should be able to handle a lot of commands per second they for some reason don't. It all depends on the quality of bluetooth modules they are using and a lot of toys use cheaper ones. And even 2 of the same toy can differ regarding bluetooth quality.
The most important thing to keep in mind in the dev side of things is to not overwhelm the device with commands, otherwise it will struggle to keep up. This means limiting the rate at which commands are sent and optimizing them, aka skip the command to vibrate at 70% when the device is already doing that.
For vibrating devices I have found that a minimum time of 0.2secs between requests is fine for most toys. In another beat based game I modded I used the following approach when triggering a beat:
- get the time until the next beat and calculate an intensity based on that. I used an exponential function that gave me 100% at 0.2s, 50% at 0.5s and 20% at 0.8s.
- skip if the intensity is the same as the last one I sent to the device
- if the next beat is in less than 0.25 secs just send the command, otherwise spice it up a little. instead of sending the calculated intensity I increase it by a third of the missing intensity and hold it for 0.2secs before returning to the regular intensity. in simple terms, if the original is 10% then 90% are missing. a third of that is 30%, so I send 40% and reduce it to the original amount of 10% after 0.2 seconds. It creates a noticable bump when beats hit for better tactile feedback.
- Aug 31, 2018
- 171
- 479
Really and your comment is of course very intelligent, which is probably more to be ashamed of foreign. But I get together more like an X Post. xD
- Aug 31, 2018
- 171
- 479
Read his Post then you maybe know what i mean.
Some people who mock others people and mean they are funny.
Why should I leave this standing like this?
Current download procs windows defender noting:
Trojan:Win32/Yomal!rfn
Any ideas?
Trojan:Win32/Yomal!rfn
Any ideas?
If i already created a pack but want to add images to it, how do I go about doing it?
- Aug 31, 2018
- 171
- 479
- Aug 31, 2018
- 171
- 479