dsda-launcher [v1.3] + dsda-doom for MacOS

[Never_Again]

1 hour ago, PBeGood4 said:

the problem with it is that the PWADS need to be stored in the DOOMWADPATH, which is something I and probably many other people don't do.

 

This must be a misunderstanding. Unlike %DOOMWADDIR%, %DOOMWADPATH% doesn't have to be limited to a single dir; and most ppl, I imagine, don't store every PWAD in a dir of its own.

 

1 hour ago, PBeGood4 said:

This feels like a more user friendly approach than having them mess with Terminal commands. 

 

No need for that. The environment vars can be set permanently through the Windows Control Panel.

Of course, in your launcher you could copy the list of the user's "PWAD Folders" to %DOOMWADPATH% and declare that var just for the current session. That should work with most other ports.

[PBeGood]

Hmm, copying the "PWAD folders" to DOOMWADPATH might be a better approach.

 

Thanks for the tips. I definitely need to take a closer look at these PATHs.

[s4f3s3x]

Whenever I choose a .wad file from the launcher (no drag'n'drop, 'cause it doesn't recognize .deh files this way) and browse through my folders, an icon pops up asking me permissions to access. Now, I granted both DSDA and the launcher complete access to hard-drive and documents and apps through System Preferencies, but it doesn't solve anything. What should I do?

[PBeGood]

Drag n drop should work for .deh files.

Did you give the launcher “Full Disk Access”? 

Im away from home without my pc, so I wont be able to test it for a few days

[PBeGood]

On 7/20/2022 at 12:00 AM, s4f3s3x said:

Whenever I choose a .wad file from the launcher (no drag'n'drop, 'cause it doesn't recognize .deh files this way)

Fixed this. Now both .deh and .bex can now be dropped into the launcher

 

On 7/20/2022 at 12:00 AM, s4f3s3x said:

Now, I granted both DSDA and the launcher complete access to hard-drive and documents and apps through System Preferencies, but it doesn't solve anything. What should I do?

Go to System Preferences -> Security and Privacy -> Full Disk Access,  remove dsda-launcher from the list (if it is there), then add it again. This worked for me. (I'll see if I can make the launcher ask for Full Disk Access on the first time you open it)

 

Im waiting until the release of dsda-doom v0.25 before I release a new version of the launcher, because there are a few features that require v0.25

[s4f3s3x]

Cool! I'll be waiting for the new release then : )

[s4f3s3x]

DSDA v0.25.0 is out! I've been waiting more than Jesus' second coming

@PBeGood4 ...but I'll hold my breath a lil bit more for the MacOs release : ))

[Xaser]

 

Could we get an option to select which folder(s) the IWADs are in, rather than require they be moved or copied to a specific place? This is a bit spooky for an official launcher (the instructions as written may break other sourceports if someone moves their IWADs by dragging them) and doesn't play well with those of us that already have things set up a certain way. Additionally, dsda-doom itself (and virtually all other modern sourceports) will search for IWADS in the DOOMWADDIR and DOOMWADPATH environment variables, so auto-populating from those would be good too.

Edited December 24, 2022 by Xaser
editing my post to be less grumpy; sorry there, I was posting while half-asleep :P

[PBeGood]

@s4f3s3x It will still take me a few days to release the new version. In the meanwhile, if you have brew installed, you can use it to install 0.25

@Xaser Since there are only a few IWADs, I didnt bother to make the IWADs folder customizable. Thanks for the suggestion, I will try to add that for this next release.

[s4f3s3x]

2 hours ago, PBeGood4 said:

@s4f3s3x It will still take me a few days to release the new version. In the meanwhile, if you have brew installed, you can use it to install 0.25

 

Great : ) yes, I'll try that. 

Edited December 25, 2022 by s4f3s3x

[s4f3s3x]

Okay, I did and... well, I think I'll wait for the "official" MacOs release.

Too many weird things going on here... for one, the program seems to not use my display's color space, everything looks so washed out - or, I suppose it simply uses the Windows RGB gamma.

There are also other things I'm not convinced about at all, but as I said I'll wait for @PBeGood4 to finish its own before addressing them 'cause they might just be part of v0.25.0. 

Until then I'll stick with v0.24.3 ( >:-3 )

 

Edited December 25, 2022 by s4f3s3x
yea

[s4f3s3x]

Uh, so homebrew install of v0.25.0 also affected my previously installed Crispy Doom 5.12.0 - same problem: muted color space. Every other source port I have displays color correctly (GZD, Eternity, Chocolate, Nugget).

I don't understand what's going on?

 

[GarrettChan]

Have to switch to the new launcher for 0.25, and I like it overall, but I'm kinda missing one feature from the old launcher is the history.

 

With the history, I don't need to select iwad/complevel/pwad to play things I recently played. Is there any chance that this could be something in the future?

 

Thanks.

[Dagazur]

having trouble running dsdadoom from the launcher, it runs fine on its own but this comes up when trying with the launcher

 

windows 10 64bit, tried with and without pwads, having fullscreen ticked and unticked, no matter what resolution I try it still won't work (1680x1050 is my native)

 

hopefully I'm not missing something!

Edited December 27, 2022 by Dagazur

[PBeGood]

@GarrettChan That feature is already implemented in the latest master.

 

@s4f3s3x That might have happened because of a SDL2 update. When you installed 0.25, brew might have updated SDL2

[PBeGood]

@Dagazur -geom should only take one argument like widthxheight

could you press the ? Button in the bottom right, then press copy and paste it here?

[s4f3s3x]

@PBeGood4 Yeah that seems the case. Is there any way to "fix" that? Is it something that's going to carry over with you new release?

[PBeGood]

If it is a known bug with SDL2, I will try to compile dsda-doom using an older version of SDL2. If it is the new correct behaiviour, I will probably use the new version.

[GarrettChan]

On 12/27/2022 at 4:04 AM, PBeGood4 said:

@GarrettChan That feature is already implemented in the latest master.

Thanks

[PBeGood]

v1.2 has been released

 

Here are binaries for Windows 64-bit and MacOS arm64 and x64

https://github.com/Pedro-Beirao/dsda-launcher/releases/tag/v1.2

 

Some of the new features:

- New Windows Dark mode

- History (Lets you launch and load commands you launched before)

- Support for --help, -hud and -config parameters

- Restructured the toggless customization

- You can customize the folders where the launcher will search IWADs in (DOOMWADDIR is there by default)
- DOOMWADPATH is by default on the "PWAD Folders"

 

Please use dsda-doom v0.25 with this release. Some features need it.

[PBeGood]

@s4f3s3x Let me know if the colors problem you had is present in this build 👍

[s4f3s3x]

17 minutes ago, PBeGood4 said:

@s4f3s3x Let me know if the colors problem you had is present in this build 👍

 

Okay, I downloaded it immediately.

As of now... I can start the launcher, I can see it's the updated version, but when I press "Launch"... it does nothing!

My IWAD folder is still the same, but I did set it again for good measure. I don't know if this is relevant.

 

If I try to launch DSDA from the exec, same, doesn't start. I got this report from the terminal:

 

Spoiler

 

Last login: Thu Dec 29 23:48:21 on console

/Applications/dsda-launcher.app/Contents/Resources/dsda-doom ; exit;

xxx@xxxs-MBP ~ % /Applications/dsda-launcher.app/Contents/Resources/dsda-doom ; exit;

dsda-doom v0.25.2 (https://github.com/kraflab/dsda-doom/)

dsda-doom is released under the GNU General Public license v2.0.

You are welcome to redistribute it under certain conditions.

It comes with ABSOLUTELY NO WARRANTY. See the file COPYING for details.

 

Playing: DOOM 2: Hell on Earth

adding /Users/xxx/.dsda-doom/doom2.wad

adding /Users/xxx/.dsda-doom/dsda-doom.wad

adding /Users/xxx/.dsda-doom/autoload/all-all/doom_wide.wad

 

portmidiplayer: No output devices available

W_GetNumForName: SNDCURVE not found

 

Saving session...

...copying shared history...

...saving history...truncating history files...

...completed.

Deleting expired sessions...none found.

 

 

Never had a similar issue with the previous version :\

On top of that, the problem with infinite permission request when I want to select PWADs from the launcher it's still there - even if I granted complete access to disk again as soon as I downloaded v1.2. I'll try to capture a video of it, it's just bollocks!

[PBeGood]

@s4f3s3x You need to replace the old dsda-doom.wad.

Right click dsda-launcher.exe, Show package contents, Contents, Resources 

 

Copy dsda-doom.wad and paste it on ~/.dsda-doom

 

the launcher should do that automatically. I will try to figure out why it didnt

 

[s4f3s3x]

26 minutes ago, PBeGood4 said:

@s4f3s3x You need to replace the old dsda-doom.wad.

Right click dsda-launcher.exe, Show package contents, Contents, Resources 

 

Copy dsda-doom.wad and paste it on ~/.dsda-doom

 

the launcher should do that automatically. I will try to figure out why it didnt

 

Right. It worked, thanks : )

The colours still look muted. Since it's a display thing, posting a screenshot here would be useless as it would probably be compressed in a sRGB space, but if you want I can send you a PM with the images so you can see for yourself the difference on your Mac.

 

Also, in v0.25.2 there's something wrong with the way OpenGL mode resize images now. It's subtle but very annoying detail that bothers me a lot. Of course I will report it on the other thread or on Discord being an issue with the port itself. But for example, if I set a 3024 × 1964 res, the image should go above the notch and be covered by it as it's normal in a total fullscreen mode on M1 Macs, and go below in a proper 16:10 if I set it 3024x1890 . This happened with v0.24.3 and now it doesn't.

Plus, seems like the menu doesn't actually take into consideration the Exclusive Fullscreen mode, because even if I select that I can still swipe between desktops on Mac, which shouldn't I be able to to in that mode.

[PBeGood]

10 minutes ago, s4f3s3x said:

Right. It worked, thanks : )

The colours still look muted. Since it's a display thing, posting a screenshot here would be useless as it would probably be compressed in a sRGB space, but if you want I can send you a PM with the images so you can see for yourself the difference on your Mac.

Yes please send me a screenshot.

 

As for the other issue, I dont have a mac with a notch, so I cannot test that out

[s4f3s3x]

Yeah, it's difficult to explain in words the problems I'm encountering. I should just screen-capturing and speak, it needs to be seen best

[s4f3s3x]

Here's a screen capture of permission request issue
 

Registrazione_schermo_2022-12-30_alle_09_24.11.zip

[tmorrow]

On 4/7/2022 at 6:16 PM, PBeGood4 said:

So I though it was better for the launcher to read the demo footer

 

There are a large number of demos out there that don't have this footer. Anything not recorded on prboom+ or dsdadoom for example. This includes vanilla, chocolate, crispy doom to name a few examples.

 

In those cases, you can't get the iwad, complevel or pwads for these demos, resulting in launching dsdadoom with just the demo name supplied. This always results in the demo playing back in dsdadoom with default iwad doom2.wad set and no pwad setting at all, i.e. complete failure if it's not doom2 and needs a pwad to run correctly.

 

On 4/7/2022 at 6:16 PM, PBeGood4 said:

This feels like a more user friendly approach than having them mess with Terminal commands.

 

This is what I have to do now since your launcher isn't helping for most of the stuff I playback. It's far worse now. I have to remove settings from the previous launch and add in new settings for the current launch. Double click functionality is gone.

 

I feel the old launcher design is more helpful. You can double click the pre v25 dsdsadoom or prboom+ exe, an IWAD, a PWAD or a LMP (even within a zip). The results are:

1. exe. The launcher pops up. You select game and files (or accept the default which is last IWAD used and no files).
2. iwad. That iwad loads, bypassing the launcher.
3. pwad. The pwad will load with an iwad determined internally (don't know how). Shift double clicking instead will force the launcher to appear so you can review/change the selections.
4. lmp. If the iwad and pwad can be picked up from the demo trailer (see @Never_Again post) then it will auto launch. If not, the launcher will appear where you can again review/change the selections. Note if the demo creator has odd iwad/pwad names then that will also bring up the launcher for review.

This old launcher behavior is particularly useful, especially when you need to review and change settings. A couple of clicks is all that is required. More often than not, its launcher settings (if it comes up) are correct. In the new launcher I'm finding myself having to type in the cmd line fragments (-file usually) to get things to work and remember to remove them again later (or the launcher will use them again even though I've moved on to another pwad).

 

Unfortunately, I've had to revert to v24.3 with its old inbuilt launcher. The new v25 with the new launcher just doesn't meet my needs for demo playback ( I do a lot of this).

 

I understand why the launcher was separated from the srcport and that it will take some time to get a new launcher working the way many will want it to. I hope you can take some of this feedback and keep up the good work with the new launcher. It is looking very promising.

[PBeGood]

@tmorrow 

 

Why are you using -file? There is a tab to add pwads.

 

For the next version I will make the launcher remove the level and the difficulty selected, when a demo is dropped (or double clicked).

I cannot remove the selected pwad, because if no pwad was found on the footer, then there is no way of knowing if the selected pwad is correct.

 

What else do you keep having the need to change manually between launches?

 

[PBeGood]

9 hours ago, s4f3s3x said:

Here's a screen capture of permission request issue
 

Registrazione_schermo_2022-12-30_alle_09_24.11.zip

 

It only gives me a pop up once and then it never shows again.

I will look into why this could be happening for you. Thanks!