Recent Posts

Pages: [1] 2 3 ... 10
1
WIP / Re: Waiting on my back burner
« Last post by Michael Lobko-Lobanovsky on Today at 04:54:20 pm »
... one of them ...

The topmost one? ;)

Quote
... more than 100 millions indices ...

 :o

In 32 bits, such a model would probably fail to load at all due to low memory at an early stage of geo re-triangulation. And it would probably take a pre-VBO ObjReader minutes to render a single frame on its artificially affined one-core-only CPU...

Quote
... and still playing in ObjReader ...

Might still fail on a cheaper video card with just 1GB of VRAM. Needs testing to prove or disprove my supposition though.

Quote
... 99% of the GPU ;)

This figure usually means that the total of geo data plus indices plus mipmapped textures plus compiled shaders exceeds the total available VRAM, and the GPU has to swap portions of it into conventional RAM.

How much VRAM is there on your video card BTW?
2
WIP / Waiting on my back burner
« Last post by Patrice Terrier on Today at 12:07:55 pm »
These are the models waiting.

BTW, one of them had more than 100 millions indices, and still playing in ObjReader while using 99% of the GPU ;)

...
3
WIP / Re: Migration to FBO
« Last post by Patrice Terrier on April 23, 2018, 08:57:58 am »
Going slowly better, i can now put again my right foot on the floor, thank you...
4
WIP / Re: Migration to FBO
« Last post by Michael Lobko-Lobanovsky on April 21, 2018, 11:27:16 am »
I'm sorry for your bad times ... How's your foot doing, my friend?
5
WIP / Re: Migration to FBO
« Last post by Patrice Terrier on April 12, 2018, 09:37:40 am »
Quote
How did you know it's going to be the wallpaper list box??
For the purpose of post-processing, we must provide specific materials, and of course avoid the changing of the wallpaper background, just like for my BassBox/MediaBox visual plugins  :)

I am stamped with a few new models, but because of my foot i have to spend several hours in my bed, far away from my keyboard  :'(

About the disabled window, we will probably need a specific one, to follow the moving of the main window, let me know when you need it, and i shall write it or perhaps make a change into WinLIFT (have to see the easiest one).
6
WIP / Re: Migration to FBO
« Last post by Michael Lobko-Lobanovsky on April 11, 2018, 09:33:25 pm »
... i have no way to check it anymore on W7.

I have both 64-bit Win 7 and 10 on two different boxes with nVidia geForce video adapters. You can rely on my reports in this regard. :)

Quote
Note: On W10 because of the border width used by the Windows theme, in full screen mode the displacement error is much more visible.

OK OK, your name stays in the list of fixes. 8)

Quote
Here is an example to disable the wallpaper listbox :

How did you know it's going to be the wallpaper list box?? :o  :D
7
WIP / Re: Migration to FBO
« Last post by Patrice Terrier on April 11, 2018, 06:21:29 pm »
OK, i followed your advice, because i have no way to check it anymore on W7.

Code: [Select]
    if (gP.openDialog) { // Center OpenDialog
        HWND hWnd = GetForegroundWindow();
        //if ((hWnd != gP.hMain) && IsWindowVisible(hWnd)) {
        if ((hWnd != gP.hMain) && (hWnd != gP.hGL) && IsWindowVisible(hWnd)) {  // MLL: 04-11-2018 (for W7 compatibility)
            RECT r; GetWindowRect(hWnd, &r);
            long w = r.right - r.left;
            long h = r.bottom - r.top;
            if (gP.nIsFullScreen) {          // PAT: 04-11-2018
                GetWindowRect(gP.hGL, &r);
            } else {
                GetWindowRect(gP.hMain, &r);
            }
            r.right = (r.right - r.left - w) / 2;
            r.bottom = (r.bottom - r.top - h) / 2;
            long x = r.left + r.right;
            long y = r.top + r.bottom;
            MoveWindow(hWnd, x, y, w, h, TRUE);
            gP.openDialog = 0;
        }
    }

Note: On W10 because of the border width used by the Windows theme, in full screen mode the displacement error is much more visible.

Here is an example to disable the wallpaper listbox :
HWND hGFI = skCreateDW(GetDlgItem(gP.hMain, IDC_LISTBOX));
it must be done AFTER the skin theme has been applied to the main window

8
WIP / Re: Migration to FBO
« Last post by Michael Lobko-Lobanovsky on April 11, 2018, 05:44:07 pm »
Patrice,

I am unable to reproduce this behavior on W10.

That's correct, the glitch isn't observed under Win 10 but it is seen Under Win 7 on both nVidia and ATi.

Quote
Does this occures only when you are in full screen mode?

Yes, only when in full screen.

Quote
Here is what to do:

Sorry but your fix doesn't help under Win 7: although the hGL window doesn't drift away any more but the SaveAs dialog stays off-center in the top left corner of the screen. My fix works under both OSes and doesn't seem to care whether the mode is windowed or full screen, as the full screen size is large enough to make the differences in hMain and hGL, and hence the dialog displacement error relative to the screen center, imperceptible.

Occam's razor, my friend; please follow my earlier suggestion.

Quote
To create a disabled window use this couple of API:

Thank you very much for those! The About dialog example didn't help because the actual APIs were hidden in the info box implementation, and re-writing the entire blob of PB code just for one tiny disabled window was too much pain in the back.

Quote
BTW, i have added the extra pixel for the full screen mode ;)

Excellent! :)
9
WIP / Re: Migration to FBO
« Last post by Patrice Terrier on April 11, 2018, 12:24:12 pm »
Quote
2.When trying to save a screenshot, centering the SaveFile dialog on the screen causes hGL displacement that can't be corrected other than by exiting the full screen mode. (see image 2 below) To fix this, goto gl_TimerView() in Main.cpp and add as follows:

I am unable to reproduce this behavior on W10.

Does this occures only when you are in full screen mode?

In full screen mode we should consider the size of the gP.hGL window rather than the size of gP.hMain.
Here is what to do:

void gl_TimerView() {
    static DWORD AnimDelay, ReportDelay;
    //DWORD AniCount = GetTickCount();
    gP.AniTick = GetTickCount();
    if (gP.openDialog) { // Center OpenDialog
        HWND hWnd = GetForegroundWindow();
        if ((hWnd != gP.hMain) && IsWindowVisible(hWnd)) {
            RECT r; GetWindowRect(hWnd, &r);
            long w = r.right - r.left;
            long h = r.bottom - r.top;
            if (gP.nIsFullScreen) {          // PAT: 04-11-2018
                GetWindowRect(gP.hGL, &r);
            } else {
                GetWindowRect(gP.hMain, &r);
            }

            r.right = (r.right - r.left - w) / 2;
            r.bottom = (r.bottom - r.top - h) / 2;
            long x = r.left + r.right;
            long y = r.top + r.bottom;
            MoveWindow(hWnd, x, y, w, h, TRUE);
            gP.openDialog = 0;
        }
    }


To create a disabled window use this couple of API:
HWND hGFI = skCreateDW (hWndToDisable);
skDestroyDW (hGFI);
To learn more about it, read this
https://forum.powerbasic.com/forum/user-to-user-discussions/sdk-programming/59770-dim-the-disabled-windows

BTW, i have added the extra pixel for the full screen mode ;)
10
WIP / Re: Migration to FBO
« Last post by Michael Lobko-Lobanovsky on April 11, 2018, 01:04:19 am »
This seems to occure only with some specific wallpapers.

For example, if you select a white background into Windows, and the Black.png for wallpaper in OR, then in fullscreen mode, you won't see any white line at the bottom, at least by me. Also try using a full HD wallpaper rather than 1024x512.

Please look at the image below. Anyway, why not just fix that glitch if we can? I'm not seeing any adverse effects of that extra pixel added to the height on my monitors. Do you see any on yours?

In that case, the best solution would be to paint a disabled window hover the control, this is what i am doing to simulate a popup modal dialog (to see the effect in action, just display the About dialog box, then you won't be able to click outside of the dialog).

Got it, thanks for the tip.
Pages: [1] 2 3 ... 10