Sorry, I was asleep. The signal issue doesn’t affect gameplay and has since been resolved. I have no idea why you can’t walk on Windows. I work on Linux, but I have Windows as a dual-boot and have tested many times; it works for me. Can you send me a video of the walking not working and how you hit enemies? Clicking shouldn’t do anything.
1 Like
OK, just tested and couldn’t repro. My steps:
- Export the new build
- Run it with wine
- Try to move around (I could).
I also tested the old build from Itch. You are correct; I can’t move in that one.
Fix will be released next update (1-2 weeks, sorry!)
2 Likes
We all have to sleep, you dont have to say sorry. 
I will wait, 
you once tested my game “go to bed bat” and I will test yours.
You are one of the reasons I develop it further.
2 Likes
Oh… i thouhgt i hitted them bc i got stars while clicking.
Enormous optimizations today. Combo cards were not performant enough with all the new shaders and effects, and the build menu lagged with just 8-10 of them. Now we can render every card in the game TWICE (for testing) all at once at 60fps! The shop menu hits 150-160 fps, and the build menu hits 140-130 fps.
3 Likes
Well done, what caused those spikes?
Could be a good learning case what to avoid.
There wasn’t really a spike, but the cards use a subviewport to render the textures into something that can then be tilted via shaders. Here’s the scene structure:
However, these are EXTREMELY costly. They force the GPU to render a 600x900 area, and 85 cards totals 45.9 million extra pixels. It’s like rendering the whole screen 25 times. To fix this, we just tell the viewport to stop rendering after it renders the card once, and then we reuse it. This means we can’t have any effects like rainbow or wavy text, but it’s a small price to pay. The deck menu with 85 cards was getting 20 fps, now it gets 120. With 2x the cards, we get 60. In the shop, we got 110 fps, now we get 160 (three cards weren’t so bad anyway). In the build menu, we got 30 fps with 10-12 cards, now we get 140.
3 Likes
Happy to report that all the code for the next update is finished. Now it’s just about locking in and drawing the remaining 56 assets.
Nice, i like more fps.
1 Like
Haha, don’t we all?
1 Like
Probably yes!
What are those assats for (sorry if i missed something)?
It’s the cards. Remember the mona lisa you mentioned a while back? Each card needs a picture, and there’s 85 of them. I’m done with 32 (just finished another three), so there’s 53 left to draw.
2 Likes
Maybe you could release rest with placeholder so guys can play on 
On windows? Haha. I would’ve done it, but it’s a bit too late for that decision. I’ve got lots of work this week, and I’ll be busy till this weekend. I’ll release by then, though. Also, it’s not just the assets; I’m still testing and balancing the new multi-weapon system.
1 Like
I’ve adjusted my artstyle. It now takes 30% less time per asset, and quality is near identical. The update should hopefully be out this week (by this Friday?) All the green items are done.
Examples:
This took 8-10 min
This took 3-5 min
5 Likes
Looks like you’ve successfully improved your workflow! I see no downgrades in the new art
1 Like
Happy to hear it. Extrapolating from my new speed, I’ve saved days in the overall art creation. ETA on v4.0.0 is 5 days for art, 2 days for final polishes. To be fair, extrapolation isn’t logical given I’ve just had two weekends rather than workdays, so to be conservative I’ll say two weeks.
1 Like
As I go through the cards to do art, I’m noticing that many of them are ones that I’d never pick in a build. For those who’ve played a few runs, questions:
- What cards are your go-to choices?
- What cards do you never pick?
- Out of the cards you never pick, which ones are bad, and which ones clearly have a build in mind, but you just don’t want to play that build?
Also, progress continues on texturing. Halfway through the pink cards.
1 Like
