Fonts updates and sound

By Siver. T

I n the previous entry I mentioned the how font support was implemented. But after some testing it's just not finished yet. The one problem is, that AssetJa2Font class represents just one concrete font, like 10 pt Arial bold. What is also needed is a class that will group various font assets like normal, bold and italic. Therefor new class was created, AssetFontClass. This has also another benefit - if in future I would like to replace for instance font10arial.sti with some other open-source alternative, it would be no problem. I would just create the AssetFontClass asset with another font and it will work. The default font classes (from JA2 assets) are generated using menu option.


There was also another change regarding the fonts and it was metrics computation. When I initially implemented font support, I didn't bother using right values for various properties of the font metrics (like ascentline, descentline, ...) which resulted in wrong rendering of the text, like for instance alignment wasn't working properly. This was fixed and new importer options were added to be able to specify it per font basis. Because of those changes, the TextWithShadow component was replaced by the generic TextComponent which is now using AssetFontClass directly.

The next new thing that I was working on was SoundManager. It is based on ScriptableObjectManager class. At first I wasn't sure if there should be global sound manager or it should be per-scene basis, but it's same as with the camera. There need to be a "singleton" that will handle sound and music whole time. Default mixer and audio group was also created. The SoundManager is now used in main menu scene, where the background music is playing. Because this background music should also play in for instance credits, the audio source couldn't be in main menu scene as it would be destroyed, when the credits scene would be loaded. Therefor SoundManager has special method for attaching the audio source to it and it would be played till it isn't destroyed.

The work for the credits scene has also began. The parsing of .edt file is working. They are just blobs which are encrypted by primitive algorithm.

Finally, quite a bugs were fixed, as always (like preventing adding duplicitous asset ref mocker values for the same component).

Comments

Post a Comment

Popular posts from this blog

Main menu updates

By
Image
W ell, another "long time no see". I'm still working on the project as much as I can. But it's not a steady work. During summer I was doing some other things (like bike touring) and mostly work. So, what's new? Well the main menu is working. While working on it the need arise for some sort of "mockups" components for various asset and mockup manager. Let me explain why. Because the assets of JA2 are proprietary, it means that you need to extract and build the asset bundles by yourself. Therefor all the assets in the GameObjects needs to be referenced indirectly (because they may not exist yet). This is where mockup come on scene. The mockups are just references to the real assets (like pointers in C++). And when the scene is loaded, the mockup manager primary role is to load the real assets from the mockups. Also, the main menu is implemented using Aspid.MVVM package (MIT licensed). Some other minor changes is custom Script edImporter for .pcx and .st...
Read more

Project reborn

By
W ell, after a long time of inactivity I started to work on this project again. It's been a long time since I touched the project. I've got a lot of other work to do, and also other "spare time" projects to work on. This time, I'll be using Unity engine. So, the basic infrastructure is almost done. At moment I'm working on the UI stuff. The project would be using uGUI (Unity GUI) with some MVVM library. The one big difference from the previous project is, that original JA2 data would be needed only in build time, not in a runtime. There would be editor utils, that will convert the original JA2 data to the format Unity could work with. This means, that every user would need to do this step manually as I don't think it would be legal to distribute it. After the working main menu I would post a github link to the project as I need to also update readme.md so anyone would know where to start.
Read more

Changes to string handling - UTF-8

By Siver. T
So after some time here are some minor updates on project. As first, std::wstring was replaced by std::string (as UTF-8 as default) as it somehow wrong approach to use std::wstring anywhere. For more details see [1], [2], [3]. All std::string now by default hold UTF-8 valid string. As next I will change all projects to use unicode by default and use wide WinApi functions (with help of core::ConvertClass). As second some changes were made in whole game state/screen/handling management. There was added some new classes for init screen handling and so. As usual you could see changes in google code project site. For the near future I'm planning to implement MouseRegion class and the go to GameManager::run(). And happy new year :) [1] - boost.devel thread about strings, UTF-8, ... [2] - boost.devel tread about strings and future [3] - stackoverflow question about UTF-16
Read more