Author Topic: OR code change  (Read 2823 times)

Patrice Terrier

  • Administrator
  • *****
  • Posts: 1790
    • zapsolution
Re: OR code change
« Reply #30 on: December 07, 2019, 07:09:19 pm »
Here is the sync for FPS and TURBO.

Warning, there is a new void SetTurboMode() in overlay.h, to avoid code duplication.

New version number #2.83

PS: There is a problem with the straylight computation now that the slider orientation has been changed

Added:
Here is the fix

void Mobj_resetLighting() { // PAT: 01-09-2018
    long nStrayLight = Mobj_strayLight(0, FALSE); // PAT: 01-10-2018
    SendMessage(GetDlgItem(gP.hMain, IDC_BRIGHT_CONTROL), TBM_SETPOS, TRUE, nStrayLight); // this also sets gP.rIllumFactor = 1.0f
    // zizi SendMessage(gP.hMain, WM_VSCROLL, MAKELONG(SB_THUMBPOSITION, nStrayLight), (LPARAM)GetDlgItem(gP.hMain, IDC_BRIGHT_CONTROL));
    SendMessage(gP.hMain, WM_HSCROLL, MAKELONG(SB_THUMBPOSITION, nStrayLight), (LPARAM)GetDlgItem(gP.hMain, IDC_BRIGHT_CONTROL));
    gP.nLightFlags = 1; // bin 0001
    gP.bIsLight0_On = TRUE;
    gP.bIsLight1_On = gP.bIsLight2_On = gP.bIsLight3_On = gP.bMultiLight = FALSE;
    CheckMenuItem(gP.hSubMenu, MENU_BRIGHT_LIGHT, MF_UNCHECKED);
    //gP.light0ColorAll = gP.light1ColorAll = gP.light2ColorAll = gP.light3ColorAll = true; // MLL: unused
    SetSwitch(ID_ONOFF0, gP.bIsLight0_On);
    SetSwitch(ID_ONOFF1, gP.bIsLight1_On);
    SetSwitch(ID_ONOFF2, gP.bIsLight2_On);
    SetSwitch(ID_ONOFF3, gP.bIsLight3_On);
    Mobj_lightInit();
    Mobj_assignColor();
}
« Last Edit: December 07, 2019, 08:29:58 pm by Patrice Terrier »
Patrice
(Always working with the latest Windows version available...)

Michael Lobko-Lobanovsky

  • Administrator
  • *****
  • Posts: 1481
Re: OR code change
« Reply #31 on: December 07, 2019, 08:52:18 pm »
Thank you Patrice!

Oh yes, of course it should've been WM_HSCROLL. It was the only fix I overlooked to send you, sorry! :-[


P.S. Both FPS and Turbo are working perfectly. Just make the Turbo mode checkbox 98 pxs wide rather than 88 because otherwise the trailing e letter gets truncated.
« Last Edit: December 07, 2019, 09:11:01 pm by Michael Lobko-Lobanovsky »
Mike
(3.6GHz Intel Core i5 Quad w/ 16GB RAM, nVidia GTX 1060Ti w/ 6GB VRAM, Windows 7 Ultimate Sp1)

Patrice Terrier

  • Administrator
  • *****
  • Posts: 1790
    • zapsolution
Re: OR code change
« Reply #32 on: December 09, 2019, 09:21:09 am »
Mike

I plan to release the new official version, does there is anything else to fix first?
Patrice
(Always working with the latest Windows version available...)

Michael Lobko-Lobanovsky

  • Administrator
  • *****
  • Posts: 1481
Re: OR code change
« Reply #33 on: December 09, 2019, 09:43:23 am »
Does the current code have sufficient new features for a new version release, do you think?
Mike
(3.6GHz Intel Core i5 Quad w/ 16GB RAM, nVidia GTX 1060Ti w/ 6GB VRAM, Windows 7 Ultimate Sp1)

Patrice Terrier

  • Administrator
  • *****
  • Posts: 1790
    • zapsolution
Re: OR code change
« Reply #34 on: December 09, 2019, 10:10:20 am »
Not that much, except for the GUI that is now very different.

The help file needs also to be updated  :(
fortunatly i wrote a tutorial to reminds me what to do there:
http://www.objreader.com/index.php?topic=205.msg4396#msg4396

Added:
Please check the attached file for the new features:
- Animate background
- Audio support
- Demo mode
« Last Edit: December 09, 2019, 03:31:02 pm by Patrice Terrier »
Patrice
(Always working with the latest Windows version available...)

Michael Lobko-Lobanovsky

  • Administrator
  • *****
  • Posts: 1481
Re: OR code change
« Reply #35 on: December 09, 2019, 12:50:34 pm »
The Demo mode section has been merged with the topmost Rotate model section because they are essentially about one and the same effect.

The text in the other sections has also been updated to reflect the titles and behavior of new checkboxes at the bottom of right side panel.
« Last Edit: December 09, 2019, 03:31:16 pm by Patrice Terrier »
Mike
(3.6GHz Intel Core i5 Quad w/ 16GB RAM, nVidia GTX 1060Ti w/ 6GB VRAM, Windows 7 Ultimate Sp1)

Patrice Terrier

  • Administrator
  • *****
  • Posts: 1790
    • zapsolution
Re: OR code change
« Reply #36 on: December 09, 2019, 01:42:41 pm »
Ok, thank you!

Here are 2 new TruePNG files to update the help folder ;)

Now i shall build the new official release version...
Patrice
(Always working with the latest Windows version available...)

Michael Lobko-Lobanovsky

  • Administrator
  • *****
  • Posts: 1481
Re: OR code change
« Reply #37 on: December 09, 2019, 03:50:54 pm »
Patrice,

The animation image file should be named 007Animation.png (with a capital A) for the Contents entries to be consistent with each other!
Mike
(3.6GHz Intel Core i5 Quad w/ 16GB RAM, nVidia GTX 1060Ti w/ 6GB VRAM, Windows 7 Ultimate Sp1)

Patrice Terrier

  • Administrator
  • *****
  • Posts: 1790
    • zapsolution
Re: OR code change
« Reply #38 on: December 09, 2019, 04:27:17 pm »
Mike,

I just checked the one from the binary official release, and it has already a capital A, thank you!
Patrice
(Always working with the latest Windows version available...)

Patrice Terrier

  • Administrator
  • *****
  • Posts: 1790
    • zapsolution
Re: OR code change
« Reply #39 on: December 30, 2019, 10:13:06 am »
Saving a screenshot while a shader animation i running is a real pain, especially when the common Windows file selector dialog pops up, do you have any suggestion to fix this?
Patrice
(Always working with the latest Windows version available...)

Michael Lobko-Lobanovsky

  • Administrator
  • *****
  • Posts: 1481
Re: OR code change
« Reply #40 on: December 30, 2019, 11:38:22 am »
It seems to me it happens only at the maximum screen size when practically 100% of GPU are consumed by rendering and Windows Explorer is beginning to generally lag.

Save your screen shots in a windowed mode or uncheck Turbo and possibly Demo prior to saving the snapshot to disk.
Mike
(3.6GHz Intel Core i5 Quad w/ 16GB RAM, nVidia GTX 1060Ti w/ 6GB VRAM, Windows 7 Ultimate Sp1)