Hi everyone,
I hope this hasn't been posted before:
When I change the light level of a region from the default 100 to 50 percent it works ok. I can compile the game from the editor and it works. I can save the game and continue editing ... and it still works.
However: if I CLOSE the editor ... and open it again, load my saved game ... the value has been resetted to 100 percent.
I tried this a few times and with different regions ... but always after closing the editor it seems to forget the setting.
Any ideas?
Stefan
Which AGS version you use?
Did you save the room as well as the game?
Does the same problem happen if you load in a different room, then load back the old one (rather than quitting the editor and loading it again)?
I use the newest full AGS version avalable (not the new beta).
Right know I can't get to my comp but as far as I remeber I saved the room first.
And changing rooms doesn't reset the value.
That's rather bizarre, since changing rooms should have exactly the same effect as quitting the editor and loading it again.
Are you sure you haven't somehow saved two copies of the room file in different locations, and are sometimes loading the wrong one? Do a search on your hard drive for the room file, and see if it comes up more than once.
Hi CJ,
I am back on my project now and did some more testing.
There is a bug with the area light settings.
Start a new game, create two rooms. In room 1 make a new area (number 1) and change it's light level to 50. Now go to room two and do whatever you want, just to save room 1. Now go back to room one: area 1 is still at 50 percent. However, if you move up and down in the areas (let's say up to 5) and then move back down to one a couple of times without changing any value ... at some point the area one light level is back at 100 pecent.
Can you reproduce that? And it sometimes get's reset magically if you save your room and enter it again.
I hope I don't bother you.
I haven't been able to replicate the problem.
What version of AGS are you using? There was a bug like this in an early version of 2.56, but it was fixed for 2.56d.
I am sorry.
As I just realized I was really using AGS 2.56a and of course the bug is solved with AGS 2.56d.
Thanks for your patience. That shows me how frequently this program is being updated :-)
END