Package Details: blastem 0.6.2-2

Git Clone URL: https://aur.archlinux.org/blastem.git (read-only, click to copy)
Package Base: blastem
Description: Fast and accurate Sega Genesis/Mega Drive emulator
Upstream URL: https://www.retrodev.com/blastem/changes.html
Keywords: megadrive
Licenses: GPL3
Submitter: darkfm
Maintainer: Vaporeon
Last Packager: Vaporeon
Votes: 8
Popularity: 0.000074
First Submitted: 2017-06-04 11:06 (UTC)
Last Updated: 2021-01-15 14:28 (UTC)

Dependencies (5)

Required by (0)

Sources (2)

Latest Comments

1 2 Next › Last »

tototoro commented on 2021-09-08 12:57 (UTC)

@Fourus I use "DejaVu Sans Condensed".

Fourus commented on 2021-08-26 23:33 (UTC)

I'm having the same problem as the person below me. What font did you use to fix the problem tototoro?

width: 640, height: 480
Window created with size: 640 x 480
config says: 512
Initialized audio at frequency 48000 with a 512 sample buffer, 32-bit float 
format
Added 14 game controller mappings from gamecontrollerdb.txt
Min samples buffered before audio start: 800
blastem: nuklear_ui/nuklear.h:18538: nk_begin_titled: Assertion `ctx- 
>style.font && ctx->style.font->width && "if this triggers you forgot to add 
a font"' failed.
Aborted

tototoro commented on 2021-08-06 23:02 (UTC) (edited on 2021-08-07 09:38 (UTC) by tototoro)

width: 640, height: 480
Window created with size: 640 x 480
config says: 512
Initialized audio at frequency 48000 with a 512 sample buffer, 32-bit float format
Added 14 game controller mappings from gamecontrollerdb.txt
Min samples buffered before audio start: 2400
blastem: nuklear_ui/nuklear.h:18538: nk_begin_titled: Assertion `ctx->style.font && ctx->style.font->width && "if this triggers you forgot to add a font"' failed.

I installed vasm from AUR and xcftools from community repo. Do I need to install some fonts?

EDIT:

I changed default font in KDE Settings and it works now. I don't now why it didn't work with Nimbus Sans.

SteelT commented on 2020-06-30 05:56 (UTC)

The multiple defined errors is due to the code not being GCC 10 compliant, since it defaults to -fno-common now. https://gcc.gnu.org/gcc-10/porting_to.html

doragasu commented on 2020-06-24 18:35 (UTC)

That error can be solved by changing the comparison in mw_putc function to this:

static void mw_putc(megawifi *mw, uint8_t v)
{
    if (mw->receive_bytes >= sizeof(mw->receive_buffer)) {
        return;
    }
    mw->receive_buffer[mw->receive_bytes++] = v;
}

But it still fails to build, with a lot symbols multiply defined.

trotskytown commented on 2020-05-27 03:03 (UTC) (edited on 2020-05-27 03:05 (UTC) by trotskytown)

Fails to build for me :(

In function ‘mw_putc’,
    inlined from ‘start_reply’ at megawifi.c:181:2:
megawifi.c:94:42: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
   94 |  mw->receive_buffer[mw->receive_bytes++] = v;
      |                                          ^
megawifi.c: In function ‘start_reply’:
megawifi.c:70:11: note: at offset 4098 to object ‘receive_buffer’ with size 4096 declared here
   70 |  uint8_t  receive_buffer[4096];
      |           ^
collect2: error: ld returned 1 exit status
make: *** [Makefile:260: blastem] Error 1
==> ERROR: A failure occurred in build().
    Aborting...

<deleted-account> commented on 2019-06-06 11:22 (UTC)

Blastem segfaults if it can't find the images/ directory. This seems to be new to 0.6.2. The offending line of code is in nuklear_ui/blastem_nuklear.c 1382. With no images to load, controller_image is nothing so a division by zero occurs.

doragasu commented on 2019-04-11 20:14 (UTC)

AFAIK, the optional dependencies are only required for the menu.bin ROM. I do not get any segfaults when entering the controllers menu. But I have no gamepads plugged to my computer, so the menu only has the "Back" button.

retronostalgia commented on 2019-04-10 18:44 (UTC)

I get a segfault when selecting the "controllers" menu option. The program author thinks it may be a packaging issue. For more, see http://www.sega-16.com/forum/showthread.php?34009-BlastEm-0-6-1-Released&p=840166&viewfull=1#post840166

Also, I'm confused about the vasm and xcftools optional dependencies. Are they only for generating the menu.bin ROM, or are they also needed for the Nuklear UI?

Thanks!