It's still a long way until it all happens, but already I feel it's time to improve both graphics in the application and its user interface.įirst of all, DF Remote application will get most of the remaining TWBT features it doesn't yet have. So a new tileset will have to be created specifically for DF Remote. I won't be able to use the official tileset as it will only be in and for the paid Steam/itch.io version, and I don't expect there to be as many community tilesets as there are now if the official one will be good enough. But also all the same graphics features will have to be added to DF Remote application so that it does not look any worse than what people get on desktop (which so far was a simple thing to do). Obviously, it will need to be updated for all the internal graphics-related changes in DF code. Hopefully the game will have all of the TWBT features out of the box so the latter won't be required anymore, which is good as I lately didn't have enough time to work on in anyway.įor DF Remote it's a bit more complicated. This means big changes both for TWBT and for DF Remote. As everyone probably heard by now, Dwarf Fortress is coming to Steam with enhanced graphics and professionally made tileset. And lastly, it fixes a problem on iPads where the game is not paused when you navigate away from the map screen to other screens (this could have caused random issues because of the game state changing when it's not expected to). Also you can now configure how many announcements are visible at the bottom of the screen at once and how fast they scroll.
This update fixes a crash when trying to change settings of a siege engine building. Now the work is done, and miRack will soon be available on the App Store.ĭwarf Fortress Remote for iOS version 2.12 has been released. Only recently I fixed the error, redone the tests and started porting miRack to iOS. Unfortunately, due to a mistake during early performance tests (which made them show performance on iPad worse than on Tinker Board), I abandoned that idea. However it was clear that a touch screen is much better suited for dragging virtual cables between modules and for using knobs and other controls than a mouse, and also that there's no need to build hardware when there are iPads with big screens and fast CPUs. I even tried prototyping some hardware that would be based on Tinker Board, have a touch screen and some number of encoder knobs to be mapped to virtual knobs on screen, but that project didn't go very well. This version is available at mi-rack/Rack GitHub repo, along with a web version that was made available later using Emscripten technology. The goal was to fix the performance issues, add multithreaded audio processing (which VCV Rack didn't have at that time), and ultimately to make it usable on single-board computers like Raspberry Pi and ASUS Tinker Board.
MiRack started as a fork of VCV Rack - a Eurorack-style modular software synthesiser.