Resolution stretch

[Xxypher]

Okay, I am tired of the screen being changed to 640x480 just to play full screened. I want to be able to play soldat at 1024x768 at fullscreen, but when I try, the menu and HUD system is all at 640x480 while the screen is at 1024x768.
So maybe adding a diagonal edge detection feature within the setup so it could stretch it and keep the proportions?
If you know what I am trying to say.

What this would be good for?

• Unusual resolutions
• Larger resolutions
• Widescreen monitors
• Custom sized resolutions

There is no reason why not to have this. It would help a large percentage of people.

[frosty]

i agree it is quite annoying

[L[0ne]R]

If you know what I am trying to say.

Im afraid I don't. :/
What do you mean by "screen being changed to 640x480 just to play full screened"?
And what do you mean by HUD? The main menu? Because I think "HUD" really means the in-game interface, not the menus.

If you mean what I think you mean, then there already is a similar thread: http://forums.soldat.pl/index.php?topic=31055.0
But then I have to aggree, this needs to be fixed at some point. :/ The sooner - the better, and I doubt that it's that hard to do.

[frosty]

let me explain it better, when you turn off full screen and select a resolution to fit your screen, all the bars, ammo, health, jets, are squeezed into a corner representing a 640x480 resolution,
meaning, the bars arent in the right spot, and are quite distracting, what he is asking for is a part to the code that stretches the interface resolution (640x480) to match the resolution chosen
for me its 1280x1024

now, the interface is appearing at the top left of the screen, so the jet bar is like, right in the middle of my screen, when it should be to my bottom right, instead its in the centre, not bottom middle or top middle but middle middle

makes sense now?

[L[0ne]R]

makes sense now?

It does now, thanks. But I never experienced that problem, even though I play at higher resolutions (windowed). Maybe only certain types of interface skins cause that problem?

[frosty]

perhaps, that may just be it, i will try out the default interface, and will post my results

[frosty]

yes, the default had the correct stretch, whereas an alternate reg interface, the one i used was Cryo, came out with a 640x480 res

so parhaps the problem lies with how these alternate interfaces are set up

in each interface i have downloaded, i have found a setup.sif file

the next step i can think of is to make a program that allows you to edit this file so the interface fits like a charm

or a part of the code that automatically edits the file for the same result

[Xxypher]

I found out that this is called Diagonal Edge Detection.

[frosty]

wheres that?

[Xxypher]

In a few of my programs that I have. All from different companies, so it isn;t just something made up.

[-Major-]

turn off fullscreen and stretch it to 100%?

[L[0ne]R]

turn off fullscreen and stretch it to 100%?

That means that you gotta say bye to windowed mode, and not everyone wants to do that. For example me.
(though im lucky I'm not picky about interfaces - I use the standart ones anyway, but still)
So turning off fullscreen isn't an option.

[-Major-]

turn off fullscreen and stretch it to 100%?

That means that you gotta say bye to windowed mode, and not everyone wants to do that. For example me.
(though im lucky I'm not picky about interfaces - I use the standart ones anyway, but still)
So turning off fullscreen isn't an option.

didn't do much sense to me...

[L[0ne]R]

didn't do much sense to me...

Nevermind, I was being slow. Damn mornings D:

[a fool]

what you are stating here is purely because of the interface, if it's not made for higher resolution, you can't use it for higher resolution.
For this specific reason: The bars will move in correspondence to it's precedor (In this case the underlay of the bar, like what is around and all), and that is if the BMP is bigger then a certain size. If it's precedor is not bigger then a certain size, it will move on to another one before, until it has none and will take the top left corner of the screen as the point to relate it's position.
Now that my first point is made clear, here is my second one
Now people will use PNG's for interfaces (Like CRYO which was mention earlier) because it simply has alpha channels. But in order to do this, there still needs to be those BMP files and in most case, these will be small bmp files that will not make the bars be relative to it's correct position. And this causes misplacement in higher resolution...

My third point is this: I'm horribly sorry for the quality in the clarity of this post, if anyone can, please make this more clear. I have problem making general sense in English...

[frosty]

hmm actually that makes pretty good sense, the images made for the interfaces are all 50x6  (640x480 interfaces)
there is also an image in some mods where all of these bars fit which is a 640x480 image, so, Interfaces are based on design

whereas the default interface images are 157x27, where the bars go, and the bars themselves are 57x4, which seems to work with all resolutions, therefore i have come up with a formula to decide the best size for the right resolution

say we want to know the size of the bar with the icon next to it, divide 640 by 50, which is 12.8
so, if we multiply 157 with 12.8 we get 2010(rounded)

and if we divide 480 by 6, which is 80, and multiply 27 with 80, we get 2160, which means this interface would fit on a 2160x2010 resolution

therefore, the best size to use for the bars with the icons next to them are 157x27 and the actual bars 50x6, these would work on most resulotions

which brings back a point i saw on above post

if it's not made for higher resolution, you can't use it for higher resolution

which is entirely correct, according to the top size measurement i made

and to reply to your point about Cryo, the interface was structured on a 640x480 image, then had the bars and stuff as separate images

Now people will use PNG's for interfaces (Like CRYO which was mention earlier) because it simply has alpha channels. But in order to do this, there still needs to be those BMP files and in most case, these will be small bmp files that will not make the bars be relative to it's correct position. And this causes misplacement in higher resolution...

that is also correct, if the images are not designed properly it can cause problems

My third point is this: I'm horribly sorry for the quality in the clarity of this post, if anyone can, please make this more clear. I have problem making general sense in English...

my post may be a little confusing

but the main point is:
its all in the design people

[a fool]

at least you got around 50% of what I meant correct, and my points correct. What I meant about size is the byte, file size of the images.
I'm too lazy to explain what I really meant..  because it had nothing to do with width and height of the images, but that's alright because it basically ends up on the same end

[scarface09]

F12, seems complicated but it can be done...so it's a yes from me.

[frosty]

at least you got around 50% of what I meant correct, and my points correct. What I meant about size is the byte, file size of the images.
I'm too lazy to explain what I really meant..  because it had nothing to do with width and height of the images, but that's alright because it basically ends up on the same end

size and height do have impact on file size
the smaller the size and height the smaller the file
and if some images are too small they wont work, its exactly the same

[Xxypher]

It isn't just the interface that does this. The menu does it as well. And with Diagonal edge detection, you could run Soldat at any resolution without having to set anything.