Ultimate Fullscreen Unable to Save Resolution Settings

I'm messing around with my first ever Options screen, and it's 90% functional. The only problem I have is that while Ultimate Full Screen does change the resolution on the Options screen itself, when you leave Options, if you are still in Fullscreen, everything defaults back to normal resolution settings.

The way I am storing options is via the Named Variable Object, Global Values, and Global Events. Basically, a global event loads a Settings INI from the named variable object, and distributes those numbers into global variables to load into different frames of the game. For instance, if you're playing the game in Windowed, this looks like:

Code:

---

Options Frame:

• FullscreenBox: If Flag 0 is On
  
  • NVO: Set key "windowed" to 1
• If Apply Button is Pressed: NVO: Save INI as Appdrive$ + "\" + Appdir$ + "\" + "gamesettings"
  
  • If NVO is Done Saving: Set (global variable) loadSettings to 1

Global Event:

• loadSettings = 1: Set (global variable) Windowed to GetValue(NVO, "windowed")
• If (global variable) Windowed = 1
  
  • Ultimate Fullscreen: Go Windowed, Apply Fullscreen settings to windowed size.

---

For those unfamiliar with NVO, the reason I am transferring values from the ini file into global values is because specific numbers cannot be pulled from NVO in conditions, only generic "key has a value" (without defining that value), or "key exists" conditions are included.

Windowed works great. The problem I am having specifically comes when Fullscreen settings are applied. I have 6 resolution options, including 1920x1080, 1600x900, 1366x768, 1280x720, 1024x576, and 960x540. Upon applying a fullscreen resolution in the Options screen, the UFO manually sets the size to the designated resolution, zooms in at the proper ratio, and centers the screen's position, all in a Global Event. For instance, for 1920, this looks like:

Code:

---

• Rez = 1920
• UFO is Fullscreen
  
  • ​UFO: Set Manual Fullscreen Size to (1920,1080), Set game scale to 1, Set manual fullscreen position to 0,0.

---

While 1600x900 looks like:

Code:

---

• Rez = 1600
• UFO is Fullscreen
  
  • ​UFO: Set Manual Fullscreen Size to (1600,900), Set game scale to 1.2, Set manual fullscreen position to 160,90.

---

Game Scale and fullscreen position assume a native resolution of 1920x1080, although I should probably swap these with UFO's "Game Rectangle Width" function in case anybody decides to run the game at 4K native (unnecessary but it will happen). That aside, while the numbers are saved in global values/events, and the Ultimate Fullscreen Object does exist in every frame, the only frame that accepts the resolution change is on the Options frame itself. The only thing I can think is that having added the UFO from the Options frame before pasting it into every other frame is what's caused this, however I did not have this problem with the NVO. I have tried copying the resolution code into other frames and haven't seen any effect. This is my first time using UFO and the example MFA doesn't really go into much detail for this.

TLDR: Anyone got any ideas how I can get the Ultimate Fullscreen Object's resolution and zoom settings to work across frames?

For the sake of my full understanding :D:
you reload the same settings/instructions (loaded from NVO to global values) in the UFO,
at the start/in a given moment of any other frames, but that settings don't factually apply?

Correct. At the moment I load those settings into a Global Event, and while they work on the screen where the settings themselves are applied, they aren't kept in the rest of the game (strangely they stay applied if I leave the Options screen and go back). I tried copying the global value resolution code into the other frames themselves, but this also had no effect.

At the moment I've just gone with the resolution options only changing windowed resolution and not doing anything on Fullscreen. The game is set to "Resize Display to Fill Window Size" already, and I've tested the game on my potato laptop and get a smooth 60fps at 1366x768 despite the game being set to 1920x1080. Although there are a couple one-pixel lines on the left and right side when the colors are set to invert (night mode) that I need to look into.

I'd be happy to dig in and test, but I'm on time shortage now.
It would save much time to have an already setted .mfa, representing the issues that arise with your method applied,
but I guess it would be time-consuming for you to setup the example, cleaning up unneeded/"private" code... :(

So, if .mfa available, I'd dedicate my humble brain on the matter,
otherwise I fear I can't help
(and, obviously, maybe I couldn't either even if dedicating! X))

Quote:

---

Use Compare Two General Values under the "Key exists"/"Key has value" condition.

---

D'oh. *Facepalm*

The resolution is changing in the options screen, but then doesn't hold in any other screens. The resolution itself is changed in a global event. I also suspect it's something to do with the store/load cycle.

I've uploaded an MFA that includes the main menu and the options screen. These two have been enough to see the problem at work. And yes, if the main menu comes in pixelated or upside-down, that's coded in (though I am cutting the upsidedown menu, fun as I thought it was, testers haven't thought the same). Ideally I would love to have the resolution changes take effect in fullscreen and in windowed, but right now the only thing I've barely gotten to work (and even then with some problems) is to only allow resolution changes to apply in windowed.

Mmmm don't know if this is good news for you...
but your example seems working to me!
I've only added a "next frame" on keypress since I miss redcolorizer.fx and can't see the full working start menu,
but when I change resolution, apply and go back, resolution is correctly retained in the menu frame
(although, only in windowed mode)

Yeah Windowed mode is fine, but fullscreen has some problems. After the latest bug report, these include:

• Unable to maintain fullscreen width, height, or zoom settings outside of options screen. (Which is when I temporarily cut fullscreen resolution and made only windowed resolution change anything).
• Changing from Windowed back to Fullscreen is supposed to set everything back to 1920x1080 (scaled based on screen rez) but instead keeps the windowed resolution and makes it tiny in the middle of the screen.
  
  • This is nearly okay, but I would prefer at least for pixels to stretch out to the right size. I did play around with the Zoom function in UFO but resolutions under 1280x720 start clipping when they get zoomed in to the technically correct ratio.

The colorizing shaders are part of Looki's FX pack and are a treat to work with! I use them to great lengths in this game, making elements turn random colors. If things aren't showing up for you I would just set all shaders to None and make sure their RGB Coefficient is set to black (0,0,0).

OMG can we please turn this into a Star Wars conversation? I want a BB8 to call my own!

I'll give Game Scale to 1 + Fullscreen Type to 0 a shot. I had had it where Game Scale would go up to 1.2 for 1600x900, 1.4 for 1366x768, 1.6 for 1280x720, etc. but everything started getting too big too quickly. Preferably I'd even like players to scale down to 960x540 in fullscreen, despite even a 4K native resolution, if they choose to do so. Just have everything stretched way out, but without the game clipping outside of the player's screen. At the very least, setting fullscreen to 1920x1080 no matter what, and resizing the display to fit the window in fullscreen, is okay. There may be some questions and I may have to gray out resolution selection in fullscreen, but it's okay.

Take advantage of this thread to add another question,
since I haven't played much with UFO object but plan to implement fullscreen in my application(s),
which are its advantages over "builtin" fullscreen mode?
Is it "smoother" or "faster" during runtime (never had slowdowns though with builtin mode)
or advantages comes from its additional resolution features and/or maybe commutation speed..?

I wonder, since it's not supported in the extensions manager,
if this could have been considered already covered by the fusion engine.

Oh, and my +1 for C3PO, and R2D2 naturally XD

Oh, now I got it, thank you!
Since I'm pretty chained by a fixed window ratio, that I think I could change no more,
I will definitely give this object a try to see how it would affect screen appearance :)