I downloaded the newest version of "Nightly Builds". (Date: December 24, 2014). It loads, but when creating a new game, and change the camera brightness of the game (staying overnight), it stops working. What's this? what can I do to fix this problem? ???
and merry christmas to all !! :)
Tried using the same nightly version, build Windows SDL. I started a brand new pak128 game and adjusted brightness from maximum to minimum multiple times and everything worked as expected. I cannot recreate the hang you described.
Could you post details about what target build you are using (Mac? Linux? Windows?) and what pakset you are using? Also could you explain clearly how to recreate the error (such as from a save of the map?)?
I use Windows, my pak is 128. The game opens normal, start a new game and typically loads, the error only occurs when I go change the brightness. Displays a message '' Simutrans does not respond ''
detail: when opening the yes-winsdl with pak64, this problem does not occur!
How are you adjusting the game brightness? It works fine for me using the +/- keys.
both in video options, and +/- giving this this problem. I suspect that it must have something to do with the pak's in pak128 folder.
I will exclude some pak to see if that resolves the problem.
Tested with Simutrans 120.0.1 r7437 (Windows SDL) and pak128 2.5.2 r1515 : no problem at all.
Try with SDL version if you are using GDI version, otherwise try redownloading everything from scratch. You should also try launching Simutrans in debug mode (should be "NAME_OF_EXE -debug" in command line or something like that).
Do you give Simutrans some time, or just kill it when Windows complaints that it's not responding? It could be that it just takes a lot of time to darken all the images.
QuoteDo you give Simutrans some time, or just kill it when Windows complaints that it's not responding? It could be that it just takes a lot of time to darken all the images.
When I did it I noticed some initial performance issues. Specifically the building lights took a considerable time to appear (it darkened but no lights). They eventually did appear and there was not really visible stuttering but it was not immediate the first time (was afterwards). Still worked acceptably however (why I did not mentioned it before).
Quote from: DrSuperGood on December 26, 2014, 06:40:19 PM
Specifically the building lights took a considerable time to appear (it darkened but no lights).
That makes no sense. Recoloring is a single event.
QuoteThat makes no sense. Recoloring is a single event.
Yes I also thought that, maybe I just imagined it and it certainly is not reliably re-creatable.
hello !! I was all afternoon setting the pak folder on my game, and I think I found the problem.
Before you download and start the game by the Sim-winsdl, the game was having a known problem, the error 65534. I was given the suggestion you download the Yes-winsdl, compatible with my operating sitema, in a way, the error did not appear 65534 most, however, some errors occur, as the brightness problem I mentioned here and another one not mentioned, which is the replacement of the soil by a tourist attraction, or buildings. see the pictures:
(http://i.imgur.com/avqc1uR.png)
(http://i.imgur.com/Rc3ZZJG.png)
(http://i.imgur.com/VjIWkOQ.png)
If you are passing 65534 sprites then the graphic errors you are encountering could be due to buggy code. The migration to 32bit sprite index might not be complete with some developers reporting that parts of the graphic code still use 16bit indices (so will use the wrong sprite due to overflow behaviour).
You're right, when do I delete pak's in my pak128 briefcase (reducing the number of images) this bug soil, and the error in luminosity does not occur.
r7438 might fix...
Those might be the things Dwachs was referring to.
Quote from: TurfIt on December 27, 2014, 06:11:05 AM
r7438 might fix...
excuse me. I did not understand. ???
Go on the nightly builds site and download the release r7438 as soon as it is online (not yet now) for testing.
He has committed an update changing many internal types to be consistent with the new 32bit integers used for sprite indexing. This update will be applied to the next nightly and should hopefully fix the issue.
problem solved !! Downloaded the sim-winsdl r7439 and bugs no longer occurs. Thanks for helping me! Happy 2015 !! :D