May 21 2025 build: Difference between revisions

From Skyscraper Wiki
Jump to navigation Jump to search
Created page with "{{legit}}{{db}} This build finishes more of the Texture Manager window, where in-memory textures such as text-to-textures can now be displayed. It does this by saving the in-memory texture to the file "temp.jpg", and then loading that into the image dialog. I've also made more fixes to the new native frontend. In the Skyscraper 2.1 code (master branch), I'm looking into using a serializer or database to export all of the simulator data to, in order to support saved ga..."
 
m Text replacement - " " to " "
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{legit}}{{db}}
{{OB}}{{db}}
This build finishes more of the Texture Manager window, where in-memory textures such as text-to-textures can now be displayed. It does this by saving the in-memory texture to the file "temp.jpg", and then loading that into the image dialog. I've also made more fixes to the new native frontend.
This build finishes more of the Texture Manager window, where in-memory textures such as text-to-textures can now be displayed. It does this by saving the in-memory texture to the file "temp.jpg", and then loading that into the image dialog. I've also made more fixes to the new native frontend.


In the Skyscraper 2.1 code (master branch), I'm looking into using a serializer or database to export all of the simulator data to, in order to support saved games and also network/multiplayer communication in the future. So far I've been working with the library Cereal, and it works very well, but requires smart pointers in order to do dependency tracking, which we don't use in Skyscraper yet at least. Cereal supports outputting the simulator data into binary, XML and JSON formats, with binary being the fastest. Cereal so far has been easy to use, but if it requires smart pointers, that kind of a change won't make it into Skyscraper 2.0 since the changes would touch nearly everything in the simulator. Let me know if you have any ideas for this, or if you want to help with the code.
In the Skyscraper 2.1 code (master branch), I'm looking into using a serializer or database to export all of the simulator data to, in order to support saved games and also network/multiplayer communication in the future. So far I've been working with the library Cereal, and it works very well, but requires smart pointers in order to do dependency tracking, which we don't use in Skyscraper yet at least. Cereal supports outputting the simulator data into binary, XML and JSON formats, with binary being the fastest. Cereal so far has been easy to use, but if it requires smart pointers, that kind of a change won't make it into Skyscraper 2.0 since the changes would touch nearly everything in the simulator. Let me know if you have any ideas for this, or if you want to help with the code.


'''Changelog for 2.0:'''
'''Changelog for 2.0:'''
Line 17: Line 17:
== See also ==
== See also ==
*[[May 11 2025 build|Previous build]]  
*[[May 11 2025 build|Previous build]]  
*Next build
*[[June 9 2025 build|Next build]]
*[[Development Builds]]
*[[Development Builds]]


== External links ==
== External links ==
*[https://skyscrapersimulatorforum.createaforum.com/download-skyscraper-simulator/new-build-52125-build/ New build: 5/21/25 build]
*[https://skyscrapersimulatorforum.createaforum.com/download-skyscraper-simulator/new-build-52125-build/ Build: 5/21/25 build]
[[Category:Development Builds]]
[[Category:Development Builds]]
[[Category:2025 Builds]]
[[Category:2025 Builds]]
[[Category:Beta Builds]]
[[Category:Beta Builds]]

Latest revision as of 17:04, 7 July 2025

This is an official build of Skyscraper, made by eventhorizon.
It contains only the files in SVN, and can be safely downloaded to your computer.
This article describes a development build of Skyscraper Simulator.
It contains good information related to Skyscraper Simulator.

This build finishes more of the Texture Manager window, where in-memory textures such as text-to-textures can now be displayed. It does this by saving the in-memory texture to the file "temp.jpg", and then loading that into the image dialog. I've also made more fixes to the new native frontend.

In the Skyscraper 2.1 code (master branch), I'm looking into using a serializer or database to export all of the simulator data to, in order to support saved games and also network/multiplayer communication in the future. So far I've been working with the library Cereal, and it works very well, but requires smart pointers in order to do dependency tracking, which we don't use in Skyscraper yet at least. Cereal supports outputting the simulator data into binary, XML and JSON formats, with binary being the fastest. Cereal so far has been easy to use, but if it requires smart pointers, that kind of a change won't make it into Skyscraper 2.0 since the changes would touch nearly everything in the simulator. Let me know if you have any ideas for this, or if you want to help with the code.

Changelog for 2.0:

  1. Added support for displaying in-memory textures, by saving the texture as "temp.jpg" and loading
  2. (Guide) Fixed elevator cars section
  3. Native frontend build fixes
  4. Native frontend runtime fixes
  5. Disable sleep function on main loop, for native frontend
  6. Don't use GUI console when GUI is disabled

Changelog for 2.1:

  1. started Serializer object (the change was reverted, but is active in a local branch for the time being)

See also[edit | edit source]

External links[edit | edit source]