Report #15šŸ“±This is something new...

A few months have passed since the last report, which means it’s time to sit down and write a new one ;)
My arm has already healed, the cast has been removed, now I wear an orthosis and do exercises. Yes, it still hurts, it’s hard to lean on it or lift weights, but I can already hold the mouse and stylus as before.
To be honest, after that fracture it turned out that there were also problems with my left arm. I pulled some tendons and muscles, so I couldn’t lift my arm above shoulder level. So basically, I injured both my hands🄲 But I went to physical therapy, did exercises, and now I can move it more or less normally. Soon I’ll need to return to the gym and start working out my muscles with a trainer.

And now about the main thing // what about the progress?
Due to problems with my hand, it was difficult for me to hold the mouse and make scenes during the first weeks, so I decided not to waste time and work on the code, since my left hand could work with the keyboard... And to some extent I’m glad that I did, because the progress is simply incredible.

In-game phone // and all related mechanics
How do you remember the old phone from OBD? And from other games?
Something like this probably comes to your mind:
Like a carbon copy, right? What if I say that the updated phone in OBD is something that you’ve never seen before on Ren’Py? Will you believe me?

Okay, I won’t delay, because I recorded a whole presentation for you:
https://youtu.be/UW1I0FTH_AE

I'll pretend that you watched the video šŸ˜…. And I’ll continue with standard questions that you might have.

Why does the game need a phone at all?
Initially, when I first started making the game, I followed other developers. I copied their mechanics, took ideas and tweaked the code. At some point I decided to add a phone, although there was no need for it. Now this mechanic no longer feels unnecessary, and on the contrary, it is necessary and, in my opinion, adds more variety to the game.

Why did you decide to rework your old phone?
In short, not long ago I decided to play BaDIK for the first time (I played very few AVNs), and I was confused that the phone interface in all games was somehow the same, bland and inconvenient.

What did the old versions of the phones look like?
Differently. I’ll start with the very first version, when I didn’t have any skills yet... Yeah, I make backups and store all the old versions of the game on hard drives. As a keepsake.
6th century BC, KPhone 1. The image was created based on drawings on birch bark.
I was just getting used to the engine, trying to look for ready-made code on the Internet, racking my brains over why everything wasn’t working...
November 18, 1963. KPhone 2. Photo after restoration.
From time to time, I took a break from rendering and occupied myself with the phone, doing something in it, experimenting...
April 3, 1973. KPhone 3. The photo was won from a homeless man in a fair fight.
It even seemed to me that I was succeeding: the music player was playing, the buttons were working... At some point there was an idea to add an investment mechanic to the game.
February, 18, 1999. KPhone 4. «First appearance to the people». The photo was taken by eyewitnesses.
Here I already began to think about stickers and the beauty of the interface. Now I can’t actually call it beauty, but then I wasn’t capable of more. By the way, this version appeared in OBD.
January 9, 2007. KPhone 5. «Second appearance to the people». The photo is in the Clairton National Museum of Game Makers, as a symbol of perseverance and stubbornness.

Aaand, I think this is how you remember this phone now. Even like this it looks quite nice... But the time has come to bury it.
For those who for some reason didn't watch my video 😤, I'm posting screenshots of the final version of the phone! 
Well, that's it. This version will remain in the game until the end. I’m very pleased with the result, and I almost don’t regret the time spent.

The experience gained from older versions was very useful to me. All the skills I learned and a broken arm allowed me to make a very complex, but at the same time structured and stable system. Each application is a separate module, each account is part of the social network, and each device in the game is independent. Technically, the game has the ability to open absolutely any phone and show what’s in it! But I'm unlikely to reveal the secret of how to do this >:)


How was all this done?
Now, it’s time to tell you how this phone was designed, and what problems and limitations I encountered.

Well... I started by designing it in Photoshop, and it only took two days. At first, I just wanted to remove everything unnecessary from the game interface so that there were no stupid, inconvenient buttons, and when I started working on the phone itself, my friend Gallant Trombe came to my aid. He suggested one idea: remove all the frames and leave only the working screen... Damn, why not?

From that moment on, absolutely everything changed! If earlier the procedure was clear: you make a phone frame and fit pictures in it, as it’s done in all the other games, but now there is enormous freedom for improvisation.
Timelapse of design and transfer to code.
I wrote the shaders that create rounded edges a long time ago, and if I didn’t know how to write them, I would never have achieved such a result.

During my work, I encountered a huge number of problems. How to open and close apps? What to do with screens that overlap each other? How to remove these stupid pages and make news feeds and messages endless? AND HOW THE DAMN SHOULD I OPTIMIZE ALL OF THIS SO AS NOT TO BURN YOUR DEVICES?
Ren’Py can’t render a huge number of objects at once, and it doesn’t have optimization tools, so I had to write them myself.

And now, here are a lot of boring text...

When an application opens, the screen behind it automatically disappears and appears back when needed. Separate optimizers were written for the news feed and messages. They calculate the size of the panels, the position of the current window, and based on this they give the Ren’Py command to hide or render the object. This made it possible to get rid of the "pages" and make the FPS as stable as possible. Yes, there will be drawdowns on weak phones, but for this there is a ā€œGraphicsā€ item in the game settings.

The next problem was how Ren’Py renders. Many things affect how an object is rendered, which can cause text to appear blurry. I had to experiment and find out experimentally which tricks would lead to the result I wanted. Well, I also had to switch from WebP images to SVG icons so that they would be displayed clearly on all monitors.

After solving these problems, I encountered another one - animated pictures. This is the biggest problem of the engine, since it is generally designed for static images, so animation for it is like a side quest. I had to create my own classes of audio channels that would simplify working with audio (this is directly related to animation playback), and also create a class that would store the animation itself, prepare the necessary audio channels for playing, or simply return a static picture, if there was one necessity. This way it turned out that any objects from the gallery can become wallpaper on your phone.

There was also a need to create a database of all social network content. Information about songwriters, tracks, pictures, stickers, emojis and accounts is now obtained by ID, rather than written down directly. Thanks to this, it will be much more difficult for me to break something on my phone in future updates.

End of boring text.


Small but very important bugfix
While working on the phone, I accidentally discovered the reason why the game was not resetting variables when starting a new game and when loading saves, necessitating a full restart. The nature of this was not known to me from the very release... I had to abandon the way I worked with variables before and switch to more ā€œadvancedā€ code. Well, now everything works perfectly :3

iOS support // let’s play on all platforms!
No, this is not an AppStore release. But it will be possible to play the game on an iPhone with a fairly stable FPS! Instructions for launching, setting up and everything else will be available at release and in the game itself :)

I tried very hard to optimize the mechanics for weaker devices and tried to take into account the features of playing on touch screens to make the design more convenient and universal. And if something slows down, you can always lower the game’s "graphics" level in the settings. This will reduce the detail of some animations, but make the game smoother.


So, what now?
Now that I'm done with the phone, I can go back to my regular life as a content creator. Yes, I planned to release it at the end of summer, but, as you can see, force majeure happened and I had to visit many doctors... I would even say that it was not a very pleasant incident, but it prompted very pleasant changes.

As usual, I’m not on radio silence and I’m always here or on Discord. The release is just a stone's throw away.


And many thanks to those who believe in this project and support it! Without your help the game would not be what it is now ā¤ļø