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 - Forestidia86

Pages: [1] 2 3 ... 49
1
Lix Main / Re: 64-bit Windows build
« on: April 14, 2024, 07:13:04 AM »
The win-build.bat specifies the compiler to ldc. The question is if this is necessary or should at least mentioned in the file name since somebody could just have dmd set up and get an error.

2
Lix Levels / Re: geoo's Lix level pack
« on: April 08, 2024, 09:14:36 PM »
Solved some levels in the wrappy rank.

Spoiler (click to show/hide)

3
Lix Main / Re: Giant window size (> 10x screen res): Lix opens & closes repeatedly
« on: March 23, 2024, 09:39:07 AM »
Maybe there is a possibility to write the current desktop resolution next to the input fields to minimize user errror.

Maybe with get_desktop_resolution

4
Lix Main / Building with Allegro debug libs (Win)
« on: March 22, 2024, 07:08:51 PM »
Only a first draft:

Options to get the Allegro debugging libs and dlls are nuget package or (mingw) release from the github page of Allegro 5.
From my experience: Running after building with the nuget release ones would need as extra dependencies Microsoft building tools (debugging variants of standard dlls, not tested since no access to these tools). Whereas the github release needs mingw libraries (which have a better availability).

For the dlls just choose the ones with 'debug' in the name.
For libs I know no other way than to rename them. (This means you can't have non-debug and debug libs at the same time in your toolchain.)
For nuget you already have lib-files and you have to choose the ones with 'debug' in the name. But for using them I had to remove the '-debug' part of the name, so that they look like the non-debug ones.
For the github release there are no libs. (For build with optlink you can use implib to create some.) As one way to get files that work like libs, you can rename the liballegro_....dll.a to lib files. Again you have to choose the ones with debug in their name but rename them without the '-debug' so that they look like the regular lib files, e.g. 'liballegro-debug.dll.a' to 'allegro.lib' or 'liballegro_acodec-debug.dll.a' to 'allegro_acodec.lib'.
There are maybe/probably more elegant ways to achieve this but this is how it worked for me.

Building is as usual.

If building with Allegro debug libraries was successful there should be an allegro.log (gets huge fast) created after starting the game.

5
Site Discussion / Re: Global Mod Color is hard to read
« on: March 11, 2024, 06:32:46 PM »
It's better readable but still not ideal. Thanks for dealing with it though.

6
Site Discussion / Global Mod Color is hard to read
« on: March 10, 2024, 09:14:52 PM »
The color for Global Moderators is hardly readable with default forum style. Example is attached.

7
NeoLemmix Main / Re: Replay on restart: Confuses/annoys new players, they don't click air
« on: February 17, 2024, 03:05:33 PM »
Quote from: geoo on February 17, 2024, 02:09:51 PM
I remember having that issue back in the day when I first played Cheapo (which may have even introduced this behavior? Or was it in WinLemm too?)

WinLemm has an extra Action Replay button. It even repeats the screen movements and could sometimes desynch.

8
Lix Main / Re: Hardware fullscreen not working
« on: January 30, 2024, 12:21:23 AM »
You can find out your resolution by right click on desktop - choose Display Settings - Display Resolution should be written there.

9
Lix Main / Re: Irregular screen size closes Lix immediately after opening
« on: January 29, 2024, 11:54:28 PM »
Have run 20000x20000 resolution with allegro debugging libararies and this problem appears in the allegro.log (excerpt):

Code: [Select]
d3d      D         d3d_disp.cpp:1677 d3d_create_display_internals     [   0.05236] Trying format 0.
d3d      I         d3d_disp.cpp:1353 d3d_display_thread_proc          [   0.05263] Chose a display format: 23
d3d      I         d3d_disp.cpp:1422 d3d_display_thread_proc          [   0.05270] Normal window.
d3d      I         d3d_disp.cpp:786  d3d_create_device                [   0.07843] Using no depth stencil buffer
d3d      D         d3d_disp.cpp:815  d3d_create_device                [   0.10418] trying D3DCREATE_SOFTWARE_VERTEXPROCESSING
d3d      D         d3d_disp.cpp:820  d3d_create_device                [   0.12004] trying D3DDEVTYPE_REF
d3d      D         d3d_disp.cpp:825  d3d_create_device                [   0.15057] trying D3DDEVTYPE_REF|D3DCREATE_SOFTWARE_VERTEXPROCESSING
d3d      E         d3d_disp.cpp:831  d3d_create_device                [   0.17016] CreateDevice failed: UNKNOWN
d3d      I         d3d_disp.cpp:910  d3d_destroy_display              [   0.17025] destroying display 000001428170afd0 (current 0000000000000000)
d3d      D         d3d_disp.cpp:894  d3d_destroy_display_internals    [   0.17030] waiting for display 000001428170afd0's thread to end
d3d      D         d3d_disp.cpp:1703 d3d_create_display_internals     [   0.17034] Resumed after wait.
d3d      I         d3d_disp.cpp:1711 d3d_create_display_internals     [   0.17038] Format 0 failed.
d3d      D         d3d_disp.cpp:1719 d3d_create_display_internals     [   0.17160] d3d_display = 000001428170afd0
d3d      D         d3d_disp.cpp:1720 d3d_create_display_internals     [   0.17165] win_display = 000001428170afd0
d3d      D         d3d_disp.cpp:1721 d3d_create_display_internals     [   0.17166] al_display  = 000001428170afd0
d3d      D         d3d_disp.cpp:1677 d3d_create_display_internals     [   0.17168] Trying format 1.
d3d      I         d3d_disp.cpp:1353 d3d_display_thread_proc          [   0.17195] Chose a display format: 23
d3d      I         d3d_disp.cpp:1422 d3d_display_thread_proc          [   0.17200] Normal window.
d3d      I         d3d_disp.cpp:786  d3d_create_device                [   0.19104] Using no depth stencil buffer
d3d      D         d3d_disp.cpp:815  d3d_create_device                [   0.21447] trying D3DCREATE_SOFTWARE_VERTEXPROCESSING
d3d      D         d3d_disp.cpp:820  d3d_create_device                [   0.22966] trying D3DDEVTYPE_REF
d3d      D         d3d_disp.cpp:825  d3d_create_device                [   0.25002] trying D3DDEVTYPE_REF|D3DCREATE_SOFTWARE_VERTEXPROCESSING
d3d      E         d3d_disp.cpp:831  d3d_create_device                [   0.27007] CreateDevice failed: UNKNOWN
d3d      I         d3d_disp.cpp:910  d3d_destroy_display              [   0.27016] destroying display 000001428170afd0 (current 0000000000000000)
d3d      D         d3d_disp.cpp:894  d3d_destroy_display_internals    [   0.27020] waiting for display 000001428170afd0's thread to end
d3d      D         d3d_disp.cpp:1703 d3d_create_display_internals     [   0.27022] Resumed after wait.
d3d      I         d3d_disp.cpp:1711 d3d_create_display_internals     [   0.27026] Format 1 failed.
....
d3d      I         d3d_disp.cpp:1711 d3d_create_display_internals     [  18.39248] Format 287 failed.
d3d      D         d3d_disp.cpp:1719 d3d_create_display_internals     [  18.39369] d3d_display = 00000142817965c0
d3d      D         d3d_disp.cpp:1720 d3d_create_display_internals     [  18.39378] win_display = 00000142817965c0
d3d      D         d3d_disp.cpp:1721 d3d_create_display_internals     [  18.39380] al_display  = 00000142817965c0
d3d      W         d3d_disp.cpp:1729 d3d_create_display_internals     [  18.39384] All 288 formats failed.
d3d      E         d3d_disp.cpp:1787 d3d_create_display_locked        [  18.39385] d3d_create_display failed.
display  E            display.c:55   al_create_display                [  18.39387] Failed to create display (NULL)
....

10
Lix Main / Re: Irregular screen size closes Lix immediately after opening
« on: January 29, 2024, 10:37:47 PM »
I have tried some big resolutions:

10000x10000 resulted in having no visible window at all. But when looking at tile view it shows a white window.
20000x20000 had it flickering on the task bar (no window visible) and after a while it gave up and defaulted to 640x480 window.

Lix 0.10.18 (binary distro via github), Win 10, native resolution 1920x1080

11
Lix Main / Re: Hardware fullscreen not working
« on: January 29, 2024, 05:20:55 PM »
Quote from: Silken Healer on January 29, 2024, 03:19:19 PM
How do I get that different music for Lix?

You can add custom music: https://www.lemmingsforums.net/index.php?topic=3481.msg67515#msg67515
There should be in the meantime mp3 format support in Win as well.

12
Lix Main / Fixed choice of common resolutions in the options menu
« on: January 29, 2024, 04:16:55 PM »
It might be more convenient to have a fixed choice of common resolutions for hardware fullscreen and windowed instead of having to type it oneself.
I would suggest: 640x480, 800x600, 1024x768, 1280x720, 1280x1024, 1600x900, 1680x1050, 1920x1080 (and maybe 1366x768)

1366x768 is a common resolution for old non-hd laptops. Windowed is fine for me but it doesn't work in hardware fullscreen (defaults to 640x480 window). My standard resolution is 1920x1080.

The option to put in custom values could be left to editing the options.sdl.

Maybe add a confirmation window for changing the resolution, that you have to confirm within x secs or it resets to the previous value and add an information when it defaults to 640x480 window for nonviable resolutions.

13
Lix Main / Re: Hardware fullscreen not working
« on: January 28, 2024, 08:51:40 PM »
Quote from: Dullstar on January 28, 2024, 07:01:51 PM
Lix doesn't appear to show the currently installed version of Allegro. It might be useful to insert that somewhere, maybe under where the Lix version is currently shown? https://liballeg.org/a5docs/trunk/system.html#al_get_allegro_version

With lix --allegro-version you can get the version of Allegro currently used. On Win you have to pipe it, e.g. lix --allegro-version >a.txt, to get the result since stdout is closed for Lix.

14
Lix Main / Re: [BUG] Hardware fullscreen not working
« on: January 27, 2024, 09:17:34 PM »
In your attempt, where you changed the value, did you make sure, that the hardware fullscreen had the dot for being selected? I could reproduce with resolution 1920x1000 (Lix v. 0.10.10). A higher resolution that worked with hardware fullscreen for me was 1600x900.
Only changing the resolution doesn't automatically move the dot to select hardware fullscreen, which I find confusing.

Can you tell the version of Lix and the resolutions you tried and the resolution of your monitor?


15
Lix Main / Re: Lix 32bit build
« on: January 06, 2024, 08:00:24 PM »
Since the argument --arch=x86 builds now 32bitmscoff, the libs for the x86 dmd build have to go in the lib32mscoff folder to be recognized instead of the lib folder.

Pages: [1] 2 3 ... 49