May 21 2025 build - Revision history

MelvinMan10 at 05:51, 11 August 2025

2025-08-11T05:51:18Z

← Older revision		Revision as of 00:51, 11 August 2025
Line 1:		Line 1:
	{{OB}}{{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 [[Data#Textures\|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:'''
	#Added support for displaying in-memory textures, by saving the texture as "temp.jpg" and loading		#Added support for displaying in-memory [[Data#Textures\|textures]], by saving the texture as "temp.jpg" and loading
	#(Guide) Fixed elevator cars section		#(Guide) Fixed elevator cars section
	#Native frontend build fixes		#Native frontend build fixes

Elevator1512: Text replacement - " " to " "

2025-07-07T22:04:24Z

Text replacement - " " to " "

← Older revision		Revision as of 17:04, 7 July 2025
Line 1:		Line 1:
	{{OB}}{{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:'''

Lighthouse Friesland at 10:15, 10 June 2025

2025-06-10T10:15:07Z

← Older revision		Revision as of 05:15, 10 June 2025
Line 21:		Line 21:

	== 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]]

Lighthouse Friesland at 10:14, 10 June 2025

2025-06-10T10:14:58Z

← Older revision		Revision as of 05:14, 10 June 2025
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]]

MelvinMan10 at 05:13, 22 May 2025

2025-05-22T05:13:48Z

← Older revision		Revision as of 00:13, 22 May 2025
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.

Lighthouse Friesland: 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..."

2025-05-21T12:24:34Z

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..."

New page

{{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 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:'''
#Added support for displaying in-memory textures, by saving the texture as "temp.jpg" and loading
#(Guide) Fixed elevator cars section
#Native frontend build fixes
#Native frontend runtime fixes
#Disable sleep function on main loop, for native frontend
#Don't use GUI console when GUI is disabled

'''Changelog for 2.1:'''
#started Serializer object (the change was reverted, but is active in a local branch for the time being)

== See also ==
*[[May 11 2025 build|Previous build]]
*Next build
*[[Development Builds]]

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