Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Goombert

Yeah I am getting kind of curious of the texture matrix as well Harri, the only thing is, trying to map those fuckers directly to pixels that are properly rounded.

Also, and I can't stress it enough, he's comparing the behavior of ENIGMA after updating his drivers ex post facto to old graphics demos he's run in the past without testing a single other application. Including Studio which has also demonstrated blurry text and odd rendering artifacts for him.

Also, no need to get emotional. We appreciate your testing and it is slowly getting us on the right track. It's just that we need to properly fix it, and doing it trough "magic" isn't something we want to do. And the fact that we cannot replicate the problem also hurts us. So we already determined that it's not just the AMD/NVIDIA issue, as I have Nvidia, Robert has ATI and none of us can replicate these problems.
Yes, but also, I have AMD, ATI is defunct.

Quote from: Darkstar2
Is this really related to a rounding issue, I don't think so, because the rounding alone or rounding + offset trick as suggested and tried (Yes I did do it and yes as shown) did not have ANY effect on anything.
But it was behaving as everyone expected before you updated your drivers. And yes the issue is ultimately rounding to get the pixels to transform to half-pixels, whether you do it in your game or in the source files, it is still a transformation.

I think you are fundamentally missing the real problem here.

We've also been following the suggestions by none other than, that's right, Microsoft who know more about OpenGL and their own graphics API Direct3D than all of us combined.

Slow down, you're getting yourself mixed up.

Take a closer look at the clear_view function, do you see anything wrong with what you are suggesting? clear_view only uses x and y one time, when calling the ortho function, so it should make no difference translating it there or in the ortho function.

For a better understanding of the issue, vector graphics which is what OpenGL and Direct3D are, like things to be half-pixel aligned to be sharp.

By offsetting our projection we offset every pixel by that much, it is a cheap way of solving the issue. The driver anomalies come into play because Nvidia drivers may round the pixel up or down, and AMD drivers may do the opposite.

Issues Help Desk / Re: Linux GMFormatException
« on: May 27, 2014, 11:50:04 PM »
Ok I have fixed it and now managed to successfully load the project on XLIB.

You can obtain the fixed LGM by downloading and replacing it manually from the extra packages page or by running python

This was the commit where I made the reader convert file paths to be UNIX compatible.

All I can say is I was lying, I can not tell you if I was being negligent or not. You have to keep your eyes focused quite a bit to notice the scrolling glitch.

At any rate no it has nothing to do with buffers of any sort, just tell me which of those values I just listed work.

Issues Help Desk / Re: Linux GMFormatException
« on: May 27, 2014, 10:56:59 PM »
Luckily for you I am able to reproduce it in my virtual machine, there appears to be some issue with loading GMX on Linux.

It is specifically occurring while loading Global Game Settings. More specifically when loading the ICO file because GMX does not use Unix compatible file paths. And I can not make LGM write them that way because Studio's IDE can't handle UNIX file paths. So I will need to make it convert the file paths to UNIX when reading binary files.

I never said it worked for me, you can quote me on it.

Quote from: RobertBColton
Try each of these combinations and report the behavior:
0.25,0.25 and 0.125,0.125
0.125,0.125 and 0.25,0.25
0.375,0.375 and 0.375,0.375
0.125,0.125 and 0.375,0.375
0.25,0.25 and 0.375,0.375
0.375,0.375 and 0.25,0.25
0.375,0.375 and 0.125,0.125

Once you tell me which ones work for you we can choose one of them that works for me too, and we'll go with it.

I said once you tell me which ones work for you, I would test those and pick one that works for me as well. In my next consecutive post I listed only the ones that worked for me.

No those do not work for me and exhibit the scrolling artifacts.

These work for me, please try these ones:
0.375,0.375 and 0.175,0.175
0.175,0.175 and 0.375,0.375
0.1875,0.1875 and 0.1875,0.1875

0.175,0.175 and 0.175,0.175
0.275,0.275 and 0.175,0.175
0.175,0.175 and 0.275,0.275
0.6,0.6 and 0.4,0.4
0.4,0.4 and 0.6,0.6

Issues Help Desk / Re: >:( objects nowhere to be seen
« on: May 27, 2014, 10:19:26 AM »
Create a new empty game, 1 object, add a sprite and assign it to the object, add a create event with the code show_message("hello world"); place that object in a room then run the game.

Tell me if you a) see the object and b) see the message.

Or you can also provide me with an example GMK that doesn't work as you expect it to.

Issues Help Desk / Re: Linux GMFormatException
« on: May 27, 2014, 06:47:20 AM »
Wow, I am stumped honestly edsquare, you have the latest LGM and it opens fine for me. I will have to go over and test Linux when I can to make sure it loads for me there as well.

I've also double checked the hash on the packages repo is correct, and it is.

Thank you Harri.

The interpolation I was already aware of, having interpolation on for fonts may be desired in some cases as well, and can be simply solved by adding padding parameters to any font functions. However, yes, I wish we did have the texture paging implemented, but I am afraid to do it.

Issues Help Desk / Re: >:( objects nowhere to be seen
« on: May 27, 2014, 06:43:01 AM »
I don't understand, are you saying the objects in the room are simply not visible? Try placing one with a show_message.

1) Nothing wrong with my hardware. I never had this shit happen to me in any 2D game, 3D game, or whatever.
All I know is, you updated drivers which exacerbated the behavior in ENIGMA and you did not appear to have tested Studio or Unity or anything else, or even an empty OpenGL application. This obviously doesn't affect other 3D games because half pixel alignment is not relevant to anything except an orthographic projection, and you obviously haven't experienced it in any other 2D game because whatever game it was uses proper half pixel alignment as suggested by Microsoft or others, which is what we are trying to do for ENIGMA.

2) It has NOTHING to do with blurriness, everything is sharp that is not the issue. The issue is the fucking pixel vertical line on scrolling that I did not use to have and text that is displayed wrong, NOT BLURRY, but rendered wrong.  I already posted a screen shot in the past, you too, so it can't only be card related.
I'm sorry, but I simply can not deduct what you mean by wrong, other than that you now have the vertical line for the scrolling backgrounds, I do not know what you mean by wrong in the context of text rendering. Which is very easy for you to take a picture of.

3) It's no use testing gl model view and d3d projection ortho no combination works.  I tried all the combinations suggested even my own even sweeping through the entire possible range, no combination bloody works.  If I find a setting that works in fullscreen it won't in windows and etc. having swept all the combinations.
Ok, you told me that already, I wasn't telling you to test anymore combinations there, I was telling you test rounding in the ModelStruct.

what the fuck am I supposed to do with this ?
more offsets as in x+=0.5f; y+=0.5f ?
No, I told you to round x and y before they are pushed into the vector using cmath or w/e. And if that didn't work, I told you to then try offsetting the ROUNDED value starting with a full half pixel (0.5,0.5)

You mean to tell me that everything works fine on your end without any need for offsets in the glmatrix ?  I thought you said otherwise back when I reported it the first time.
Yes, if I remove all offsets in everything, my graphics driver displays everything in OpenGL perfect whether in FS or windowed, I only have problems with Direct3D.

what if the problem is in the font rendering or sprite/background handling or deeper in the graphic system ?
You're being dramatic, I gave you a solution as low-level in the engine as possible, rounding every 2D vertex to a full pixel.

If I have time I will make a video showing the display sweep through
That is not necessary, I simply asked for a screenshot of how text rendering is behaving since you updated drivers.

vertices.push_back(x+0.5f); vertices.push_back(y+0.5f);
Or you could try doing what it was that I actually suggested.
vertices.push_back(round(x)); vertices.push_back(round(y));
vertices.push_back(round(x)+0.5f); vertices.push_back(round(y)+0.5f);

That also works for me and makes vertices round consistently on all hardware.