@sev

Awesome

Thanks a lot

Hi devs, I have a question regarding installing a snapshot build with shared plugins. Right now I can use (in the .mk file) cp ($PLUGINS) ($INSTALLATIONPATH)/plugins/ to copy the whole lot of engines. But of course they will be non-stripped. Is there a way to also access all plugins as single files?...

RetroJaro wrote: ↑

Sat Oct 12, 2019 6:48 pm

So what is OBJETS/VS1.HLZ? Every time I add a game to 2.1.0 it keeps checking for this file and says not found. Is there something I'm missing?

What platform are you running ScummVM on?

RetroJaro wrote: ↑

Sat Oct 12, 2019 1:55 am

Thanks for this! I see that it now supports lipsync for scumm v6 and v7+ games.. I tried searching but nothing really... what are the v6 and v7+ games?

https://wiki.scummvm.org/index.php?title=SCUMM/Versions

Thank you.

I know that a shared build of scummvm can be stripped, just like a static build, but what about the engine plugins?
Should those be stripped as well for release?

This may be a regression, since it happens far into the game probably no one else has caught it because noone else played it for a long time (or didn't bother to submit a bug report)

Could you provide a save state?
And maybe also report it as bug?

Neat.

Is "Adromedas Erbe" based on the same engine and can we expect those two games to be supported too?

Just for my own completeness and for future reference i created a bug report.
Looks like an engine issue...but i'm not sure, of course

@sev Thank you for chiming in I figured it out myself and was using the scumm engine solely, because i wanted to be able to test a game after compiling as well. It works now, but i need to compile the whole app with shared objects (a static app with shared engines access doesn't work here as it will...

@criezy I know about the configure switch and already tried it, but it seems it needs some more "configuring" (at least on my platform), since in my test compile all the engines were still build static into the executable. Anything else i should have take a look? Thank you edit: Hmm, does compiling ...

No one has a list of available egines to be built as plugins?

Or maybe i misunderstood and have to add plugin code to all the engines myself?

The white screen issue is gone for me, yes.
I consider it fixed

Thank you very much.

But, it seems the fix from https://bugs.scummvm.org/ticket/11078#comment:29
has issued a problem in android 4.2.2 (and older?).

Maybe you want to take a look there?

I just tried quickly on macOS and I have no such issue. The aspect ratio of the display seems correct both in windowed and fullscreen mode. I tried both with 2x and OpenGL graphics modes. And in fullscreen mode, when I use a Fit to Window stretch mode, I get some small black bars on the side but no...

Which engine feature dynamic module building?

If i want to configure them to do so, do i really have to give every single engine to --enable-engine-dynamic= ?
As i can --disable-all-engines and --enable-all-engines, why not --enable-all-engines-dynamic?