05-20-2024, 03:43 PM
(This post was last modified: 05-20-2024, 03:48 PM by DerVVulfman.)
Almost there with the Sprite class
I can confirm the following:
Unfortunately, the x and y coordinates are not working and all images are positioned in the top left corner regardless of setting. Likely and hopefully, the problem is related to the issue the innate Sprite class had with opacity values passed.
On a personal basis, I think adding both Fullscreen and Debug options into the Game.Ini file as unnecessary. And for Debug to be in the Game.Ini, the chance for cheating.
The current editor is indeed passing the required command string into the Game.ini file that triggers debug mode. When working upon a project that has HiddenChest's executable renamed Game.Exe, I am able to access all of the Debug features within the script code... walk through walls when using [Ctrl] and access the debug menu with [F9]. And only then from the editor. IF it was possible to engage Debug mode by way of Game.Ini, anyone could set any switch, increase any variable, or go into map areas that the game developers may have as off-limits for storyline reasons.
And your inclusion of the Graphics.fullscreen method and parameter makes it possible to craft a game that begins fullscreen at the game developer's leisure. By merely including Graphics.fullscreen = true into the Main script worked just the same as the Game.ini
However, there is a matter of a 2-second screen-refresh delay with the fullscreen/windowed options, and it makes no difference if switching is performed by Graphics.fullscreen, the Game.Ini command, or just using [Alt]+[Enter]. When switching modes, the entire screen goes black and remains black for 2 seconds. Action does not halt, I was able to move the player character in the field map while the screen was black.
In a related issue though accidentally found and expected to be quite uncommon, the screen goes black for 2 seconds if generating a pop-up using Ruby's standard p or print commands while in fullscreen. There is no delay nor blackout when displayed in windowed-mode, but only in fullscreen. Like I say, it is something that would be uncommon as this would be more for bug-testing and system alerts more than an actual game option.
I can confirm the following:
- Blend functions correctly
- Opacity functions correctly
- Origin (Top-Left vs Center) functions correctly
- Zoom functions correctly
- Rotate functions correctly
Unfortunately, the x and y coordinates are not working and all images are positioned in the top left corner regardless of setting. Likely and hopefully, the problem is related to the issue the innate Sprite class had with opacity values passed.
On a personal basis, I think adding both Fullscreen and Debug options into the Game.Ini file as unnecessary. And for Debug to be in the Game.Ini, the chance for cheating.
The current editor is indeed passing the required command string into the Game.ini file that triggers debug mode. When working upon a project that has HiddenChest's executable renamed Game.Exe, I am able to access all of the Debug features within the script code... walk through walls when using [Ctrl] and access the debug menu with [F9]. And only then from the editor. IF it was possible to engage Debug mode by way of Game.Ini, anyone could set any switch, increase any variable, or go into map areas that the game developers may have as off-limits for storyline reasons.
And your inclusion of the Graphics.fullscreen method and parameter makes it possible to craft a game that begins fullscreen at the game developer's leisure. By merely including Graphics.fullscreen = true into the Main script worked just the same as the Game.ini
However, there is a matter of a 2-second screen-refresh delay with the fullscreen/windowed options, and it makes no difference if switching is performed by Graphics.fullscreen, the Game.Ini command, or just using [Alt]+[Enter]. When switching modes, the entire screen goes black and remains black for 2 seconds. Action does not halt, I was able to move the player character in the field map while the screen was black.
In a related issue though accidentally found and expected to be quite uncommon, the screen goes black for 2 seconds if generating a pop-up using Ruby's standard p or print commands while in fullscreen. There is no delay nor blackout when displayed in windowed-mode, but only in fullscreen. Like I say, it is something that would be uncommon as this would be more for bug-testing and system alerts more than an actual game option.