Active Threads | Active Posts | Unanswered Today | Since Yesterday | This Week
Non-Windows MAME Support Jump to new posts
Re: plug out and in usb controller to get it working crumpetlump 03/27/20 10:09 PM
R.Belmont do you have any suggestions for me to try and fix this?, it was fine about a year ago , I have been doing make -j5 to compile but havent changed anything in makefile, i used to change a few options in the makefile like a year ago maybe this is part of the problem?
4 186 Read More
MAME Jump to new posts
Re: Battlezone fun Golden Child 03/27/20 05:29 PM
If we know where the locations for our position and direction are in memory, let's see if we can move things around under lua's control.

Moving the player under the control of a lua script:

[Linked Image from i.imgur.com]

Player position is stored at 2d/2e for x position and 31/32 for y position.
Tank position is stored at 2f/30 for x position and 33/34 for y position.
Tank direction is stored at 29/2c 29=lsb and 2c=msb.

The player's direction is stored at 27 = lsb and 2a = msb. When 27/2a are set to 0000 that precisely lines up on the right side of the moon with the target.

Interestingly, only the msb of the direction gets reset on the start of the game, when the game starts it will be very close to the edge of the moon.

[Linked Image from i.imgur.com]

This script will move the tank around, spin it, and move the player around also. It's kind of fun to "trap" the missile with the script and watch it rotate.

Code
mem=manager:machine().devices[":maincpu"].spaces["program"]
mem2=manager:machine():memory().regions[":maincpu"]
function hex(a,digits) digits = digits or 2 return string.format("%0"..digits.."x",a) end

function setlives(l) l=int(l) mem:write_u8(0xcc,l) end
function setscore(s) s=int(s) mem:write_u16(0xb8,s) end

function setmypos(x,y) mem:write_u16(0x2d,int(x)) mem:write_u16(0x31,int(y)) end
function setmydir(d) d=int(d) mem:write_u8(0x27,d&0xff) mem:write_u8(0x2a,(d&0xff00)>>8)  end

function settankposx(x) mem:write_u16(0x2f,int(x)) end
function settankposy(y) mem:write_u16(0x33,int(y)) end
function settankpos(x,y) settankposx(x) settankposy(y) end
function settankdir(d) d=int(d) mem:write_u8(0x29,d&0xff) mem:write_u8(0x2c,(d&0xff00)>>8)  end 

function delay(delaytime)  delaytime = delaytime or 4 emu.wait(delaytime * 1/60) end

function int(i) return math.floor(i) end

function movetank2()
-- move enemy tank in a triangle
movetable = { 10,0,  50,0,  50,10, 10,0, 50,-20, 10,0,}
for pos=1,#movetable-2,2 do
   x1=movetable[pos+0] y1=movetable[pos+1] 
   x2=movetable[pos+2] y2=movetable[pos+3]
   dist=math.sqrt((x2-x1)^2 + (y2-y1)^2)
   vel=20/60
   t=dist/vel
   frames=t
   --print(pos,x1,y1,x2,y2)
   for f=1,frames do
       x=(x2-x1)/frames * f + x1
       y=(y2-y1)/frames * f + y1
       settankpos(x*256,y*256)
       setmypos(0,0)
       setmydir(0)
       print(f,frames,x,y) 
       delay(1)
  end
end
-- spin the enemy tank or missile around 3 times
for i=1,3 do
for d=0,255 do
  setmypos(0,0)
  setmydir(0)
  settankdir(d*256)
  settankpos(0x600,0)
  setlives(4)
  setscore(d)
  delay(2)
end
end
-- move me and fix the enemy tank right in front of me
movetable = { 10,0,  50,0,  50,10, 10,0, 50,-20, 10,0,}
for pos=1,#movetable-2,2 do
   x1=movetable[pos+0] y1=movetable[pos+1] 
   x2=movetable[pos+2] y2=movetable[pos+3]
   dist=math.sqrt((x2-x1)^2 + (y2-y1)^2)
   vel=20/60
   t=dist/vel
   frames=t
   --print(pos,x1,y1,x2,y2)
   for f=1,frames do
       x=(x2-x1)/frames * f + x1
       y=(y2-y1)/frames * f + y1
       setmypos(x*256,y*256)
       settankpos(x*256+0x401,y*256)
       setmydir(0)
       setlives(4)
       setscore(f)
       print(f,frames,x,y) 
       delay(1)
    end
end
end

co1=coroutine.create(movetank2) coroutine.resume(co1)
13 1,298 Read More
MAME Jump to new posts
Re: Wonderswan driver update KanedaFr 03/27/20 09:34 AM
Just Desserts : sorry! I didn't realize the already point me to the right anwser frown I thought you were talking about using socket or not.

pmackinlay, Vas Crabb : I found the bitbanger solution while Googling, on TI82 related page but for some reason I didn't find it on command line... I thought it was since replaced by comm_localhost/comm_remotehost

so what the difference / benetifs of bitbanger vs comm_localhost/comm_remotehost ?
At this time, I successfully send data (TX), I have to fix some part of my receive code (RX) but should I move to bitbanger first ?

I'll try using device_slot after that, based on TI82 or NES example

thanks!!!!
8 460 Read More
MAME Jump to new posts
Re: The MAME Bot Thread crazyc 03/25/20 02:52 PM
There are a couple in https://forums.bannister.org/ubbthreads.php?ubb=showflat&Number=109639#Post109639 too (although these are static bots while the ones in that thread are AIs).
1 187 Read More
QMC2 Jump to new posts
Re: QMC2 and QT5.11+ stablerom 03/25/20 11:55 AM
Using source files at https://svn.code.sf.net/p/qmc2/code/trunk.

In order to build in Ubuntu 17.10 the config file needs to be as follows (Ubuntu_17.10.cfg or Debian.cfg),

Code
QMAKE    = /usr/bin/qmake
LUPDATE  = /usr/bin/lupdate
LRELEASE = /usr/bin/lrelease


This will allow QMC2 Arcade to build and install.

QMC2 (non arcade version) does not build with the latest version of QT5.

Good to see you back, Rene.
2 342 Read More
MAME Jump to new posts
Re: SVN builds - new driver flood pmackinlay 03/24/20 10:44 AM
Work on the Sony NWS-3260 portable (similar to this: bignews) is progressing. We now have basic video and hle keyboard.

Interrupts, DMA and SCSI remain to be tackled, but since networking is already up, I'm going to see if I can get it to boot diskless first.

[Linked Image from i.imgur.com]
5,310 15,546,407 Read More
QMC2 Jump to new posts
Re: Hey, hey - here I am... Christina 03/21/20 04:07 AM
Welcome back!
17 788 Read More
Non-Windows MAME Support Jump to new posts
Re: Compiling SDLmame (0.219) on OSX PPC MacBox360 03/20/20 08:34 PM
Well, I have almost fixed all the compile errors but the linker fails miserably, here is the error:

Code
final section layout:
    __TEXT/__text addr=0x000024C4, size=0x017F6554, fileOffset=0x000014C4, type=1
    __TEXT/__text_cold addr=0x017F8A18, size=0x00020840, fileOffset=0x017F7A18, type=1
    __TEXT/__text_startup addr=0x01819258, size=0x0001BED4, fileOffset=0x01818258, type=1
    __TEXT/__text_cold_coal addr=0x0183512C, size=0x00000EE4, fileOffset=0x0183412C, type=1
    __TEXT/__symbol_stub1 addr=0x01836010, size=0x0004D1B0, fileOffset=0x01835010, type=27
    __TEXT/__cstring addr=0x018831C0, size=0x0006A8CE, fileOffset=0x018821C0, type=12
    __TEXT/__const addr=0x018EDA90, size=0x00158FB5, fileOffset=0x018ECA90, type=0
    __TEXT/__info_plist addr=0x01A46A45, size=0x00000223, fileOffset=0x01A45A45, type=0
    __TEXT/__eh_frame addr=0x01A46C68, size=0x0055A394, fileOffset=0x01A45C68, type=18
    __DATA/__dyld addr=0x01FA1000, size=0x0000001C, fileOffset=0x01FA0000, type=29
    __DATA/__nl_symbol_ptr addr=0x01FA101C, size=0x00008AB0, fileOffset=0x01FA001C, type=28
    __DATA/__la_symbol_ptr addr=0x01FA9ACC, size=0x0001346C, fileOffset=0x01FA8ACC, type=26
    __DATA/__mod_init_func addr=0x01FBCF38, size=0x0000047C, fileOffset=0x01FBBF38, type=32
    __DATA/__data addr=0x01FBD3B8, size=0x0001B128, fileOffset=0x01FBC3B8, type=0
    __DATA/__static_data addr=0x01FD84E0, size=0x0000010F, fileOffset=0x01FD74E0, type=0
    __DATA/__const addr=0x01FD85F0, size=0x000D2530, fileOffset=0x01FD75F0, type=0
    __DATA/__gcc_except_tab addr=0x020AAB20, size=0x000FC305, fileOffset=0x020A9B20, type=0
    __DATA/__cfstring addr=0x021A6E28, size=0x00000090, fileOffset=0x021A5E28, type=16
    __DATA/__bss0 addr=0x021A6EB8, size=0x000108F0, fileOffset=0x00000000, type=24
    __DATA/__pu_bss0 addr=0x021B77A8, size=0x00080000, fileOffset=0x00000000, type=24
    __DATA/__pu_bss4 addr=0x022377B0, size=0x00100014, fileOffset=0x00000000, type=24
    __DATA/__bss3 addr=0x023377C8, size=0x00000598, fileOffset=0x00000000, type=24
    __DATA/__bss4 addr=0x02337D60, size=0x0000A410, fileOffset=0x00000000, type=24
    __DATA/__pu_bss3 addr=0x02342170, size=0x00000020, fileOffset=0x00000000, type=24
    __DATA/__pu_bss2 addr=0x02342190, size=0x000012E8, fileOffset=0x00000000, type=24
    __DATA/__common addr=0x02343478, size=0x0000240C, fileOffset=0x00000000, type=24
    __DATA/__bss1 addr=0x02345884, size=0x000045A0, fileOffset=0x00000000, type=24
    __DATA/__bss2 addr=0x02349E24, size=0x00075650, fileOffset=0x00000000, type=24
    __OBJC/__module_info addr=0x023C0000, size=0x00000120, fileOffset=0x021A6000, type=0
    __OBJC/__message_refs addr=0x023C0120, size=0x00000048, fileOffset=0x021A6120, type=14
    __OBJC/__cls_refs addr=0x023C0168, size=0x00000014, fileOffset=0x021A6168, type=14
    __OBJC/__image_info addr=0x023C017C, size=0x00000008, fileOffset=0x021A617C, type=0
ld: bl PPC branch out of range (25310156 max is +/-16MB): from start (0x000024C4) to _main (0x018258D0) in start from /usr/lib/crt1.10.5.o for architecture ppc
collect2: error: ld returned 1 exit status
make[2]: *** [../../../../../mame] Error 1
make[1]: *** [mame] Error 2
make: *** [macosx_x86] Error 2


I must admit it was an interesting challenge, I have learned a lot looking inside the MAME sources and browsing a lot the web. Not everything is clear (I have no knowledge about this kind of language) but I start to see the structure and rules behind the build process and this was extremely useful in planning the modifications to try.
I will do more experiments in the next days... :-)
11 346 Read More
Non-Windows MAME Support Jump to new posts
Re: SDLMAME - configure to run on 2nd Display D M K 03/20/20 08:19 PM
Originally Posted by R. Belmont
Why don't newer 64-bit versions run? That would be the first problem, as 0.155 is very old.


I have tried some of the later 64bit versions from <here> but when the NAME binary is launched it loads 'in the background' so I have to switch to another application, then locate MAME in my dock before I can see it.

I seem to remember compiling a 64bit version myself using Terminal but it never produced a working version. SDLMAME 64bit last worked properly for me on my Mac around 0.152 (ish)
7 184 Read More
Non-Windows MAME Support Jump to new posts
Re: Android Build for MAME - Enabling bgfx Shaders Yash Anand 03/20/20 01:40 PM
So, after a brief flurry of other tasks I am back on this smile
RB if I understand correctly I have to make sure that the VIDEO_MODE_BGFX ( osd_renderer::make_for_type --- src/osd/modules/osdwindow.cpp) is being chosen and further the init in renderer_vk.cpp gets called.

Further in renderer_vk.cpp I am stuck as vkCreateAndroidSurfaceKHR is crashing with a SIGSEGV frown
func7 never comes and func6 gives the output as -

../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1652): BGFX func6 m_instance - c9aa5900 m_allocatorCb - 0 sci.window - 0x0
which land the suspects as the nwh (sci.window) and the allocatorcallbacks which is coming as 0x0
Before this I am able to get these values fine - Shared library functions, Instance Functions, Physical Device (Mali-T860) Device functions

#elif BX_PLATFORM_ANDROID
_BX_TRACE("func5");
{
VkAndroidSurfaceCreateInfoKHR sci;
sci.sType = VK_STRUCTURE_TYPE_ANDROID_SURFACE_CREATE_INFO_KHR;
sci.pNext = NULL;
sci.flags = 0;
sci.window = (ANativeWindow*)g_platformData.nwh;
_BX_TRACE("func6 m_instance - %x m_allocatorCb - %x sci.window - 0x%x\n", m_instance, m_allocatorCb,sci.window);
result = vkCreateAndroidSurfaceKHR(m_instance, &sci, m_allocatorCb, &m_surface);
_BX_TRACE("func7");
}

Any help is welcome as I seemed to have hit the wall here.

PS - Another scan at the output I am going to take a stab at this. Add ACCESS_SURFACE_FLINGER in the manifest file and try to make it a system app


03-20 09:07:23.742 489 525 I ActivityManager: Start proc 2082:org.mamedev.mame/u0a45 for activity org.mamedev.mame/.MAME
03-20 09:07:23.804 2082 2082 I rg.mamedev.mam: The ClassLoaderContext is a special shared library.
03-20 09:07:23.839 2082 2082 V SDL : onCreate(): null
03-20 09:07:23.843 2082 2082 E libsigchain: Warning: Unexpected sigaction action found 0xededda95
03-20 09:07:24.041 2082 2082 D OpenGLRenderer: Skia GL Pipeline
03-20 09:07:24.061 2082 2082 V MAME : MAME onCreate:
03-20 09:07:24.064 2082 2082 V MAME : copy from Asset:/storage/emulated/0/Android/data/org.mamedev.mame/files/mame.ini
03-20 09:07:24.088 2082 2082 V SDL : onResume()
03-20 09:07:24.115 257 580 W ServiceManager: Permission failure: android.permission.ACCESS_SURFACE_FLINGER from uid=10045 pid=2082
03-20 09:07:24.115 257 580 D PermissionCache: checking android.permission.ACCESS_SURFACE_FLINGER for uid=10045 => denied (1824 us)
03-20 09:07:24.117 2082 2110 I mali_so : [File] : hardware/XXXXX/mali_so/driver/product/base/src/mali_base_kbase.c; [Line] : 876; [Func] : base_context_deal_with_version_affairs_rk_ext;
03-20 09:07:24.117 2082 2110 I mali_so : arm_release_ver of this mali_so is 'r18p0-01rel0', rk_so_ver is '3@0'.
03-20 09:07:24.118 2082 2110 D mali_so : [File] : hardware/XXXXXX/mali_so/driver/product/base/src/mali_base_kbase.c; [Line] : 881; [Func] : base_context_deal_with_version_affairs_rk_ext;
03-20 09:07:24.118 2082 2110 D mali_so : current process is NOT sf, to bail out.
03-20 09:07:24.121 2082 2082 V SDL : surfaceCreated()
03-20 09:07:24.121 2082 2082 V SDL : surfaceChanged()
03-20 09:07:24.121 2082 2082 V SDL : pixel format RGB_565
03-20 09:07:24.125 253 253 D Sensors : set batch: handle = 2, period_ns = 20000000ns, timeout = 0ns
03-20 09:07:24.125 253 253 D Sensors : setDelay : 20000000 ns, (50.00 Hz)
03-20 09:07:24.125 253 253 D Sensors : set flush: handle = 2
03-20 09:07:24.126 253 568 I Sensors : report 1 flush event
03-20 09:07:24.136 2082 2122 I SDL : SDL_Android_Init()
03-20 09:07:24.136 2082 2122 I SDL : SDL_Android_Init() finished!
03-20 09:07:24.143 2082 2110 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
03-20 09:07:24.143 2082 2110 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
03-20 09:07:24.143 2082 2122 V SDL/APP : Attempting load of mame.ini
03-20 09:07:24.144 2082 2122 V SDL/APP : Parsing mame.ini
03-20 09:07:24.143 2082 2110 I OpenGLRenderer: Initialized EGL, version 1.4
03-20 09:07:24.144 2082 2110 D OpenGLRenderer: Swap behavior 2

03-20 09:07:24.167 2082 2110 D mali_winsys: EGLint new_window_surface(egl_winsys_display *, void *, EGLSurface, EGLConfig, egl_winsys_surface **, egl_color_buffer_format *, EGLBoolean) returns 0x3000
03-20 09:07:24.170 2082 2122 V SDL/APP : Available videodrivers:
03-20 09:07:24.172 2082 2122 V SDL/APP : Android
03-20 09:07:24.172 2082 2122 V SDL/APP :
03-20 09:07:24.172 2082 2122 V SDL/APP : Current Videodriver: Android
03-20 09:07:24.172 2082 2122 V SDL/APP : Display #0
03-20 09:07:24.172 2082 2122 V SDL/APP : Renderdrivers:
03-20 09:07:24.172 2082 2122 V SDL/APP : opengles2 (0x0)
03-20 09:07:24.173 2082 2122 V SDL/APP : opengles (0x0)
03-20 09:07:24.173 2082 2122 V SDL/APP : software (0x0)
03-20 09:07:24.173 2082 2122 V SDL/APP : Available audio drivers:
03-20 09:07:24.173 2082 2122 V SDL/APP : dummy
03-20 09:07:24.175 2082 2122 V SDL/APP : android
03-20 09:07:24.175 2082 2122 V SDL/APP : Build version: 0.218 (mame0218-123-ge32eb4a36f-dirty)
03-20 09:07:24.175 2082 2122 V SDL/APP : Build architecure:
03-20 09:07:24.175 2082 2122 V SDL/APP :
03-20 09:07:24.175 2082 2122 V SDL/APP : Build defines 1:
03-20 09:07:24.175 2082 2122 V SDL/APP : SDLMAME_UNIX=1
03-20 09:07:24.175 2082 2122 V SDL/APP : SDLMAME_LINUX=1
03-20 09:07:24.176 2082 2122 V SDL/APP :
03-20 09:07:24.176 2082 2122 V SDL/APP : Build defines 1:
03-20 09:07:24.176 2082 2122 V SDL/APP : LSB_FIRST=1
03-20 09:07:24.176 2082 2122 V SDL/APP : MAME_NOASM=1
03-20 09:07:24.176 2082 2122 V SDL/APP : MAME_DEBUG=1
03-20 09:07:24.177 2082 2122 V SDL/APP :
03-20 09:07:24.177 2082 2122 V SDL/APP : SDL/OpenGL defines:
03-20 09:07:24.177 2082 2122 V SDL/APP : SDL_COMPILEDVERSION=2005
03-20 09:07:24.177 2082 2122 V SDL/APP : USE_OPENGL=0
03-20 09:07:24.177 2082 2122 V SDL/APP :
03-20 09:07:24.177 2082 2122 V SDL/APP : Compiler defines A:
03-20 09:07:24.177 2082 2122 V SDL/APP : __GNUC__=4
03-20 09:07:24.177 2082 2122 V SDL/APP : __GNUC_MINOR__=2
03-20 09:07:24.178 2082 2122 V SDL/APP : __GNUC_PATCHLEVEL__=1
03-20 09:07:24.178 2082 2122 V SDL/APP : __VERSION__="4.2.1 Compatible Android (5900059 based on r365631c) Clang 9.0.8 (https://android.googlesource.com/toolchain/llvm-project 207d7abc1a2abf3ef8d4301736d6a7ebc224a290)"
03-20 09:07:24.178 2082 2122 V SDL/APP :
03-20 09:07:24.179 2082 2122 V SDL/APP : Compiler defines B:
03-20 09:07:24.179 2082 2122 V SDL/APP : __unix__=1
03-20 09:07:24.179 2082 2122 V SDL/APP :
03-20 09:07:24.179 2082 2122 V SDL/APP : Compiler defines C:
03-20 09:07:24.179 2082 2122 V SDL/APP :
03-20 09:07:24.179 2082 2122 V SDL/APP : Enter init_monitors
03-20 09:07:24.179 2082 2122 V SDL/APP : Adding monitor screen0 (1280 x 1024)
03-20 09:07:24.179 2082 2122 V SDL/APP : Leave init_monitors
03-20 09:07:24.180 2082 2122 V SDL/APP : Enter sdlwindow_init
03-20 09:07:24.181 2082 2122 V SDL/APP : Unable to find the /storage/emulated/0/Game/bgfx folder. Please reinstall it to use the BGFX renderer
03-20 09:07:24.181 2082 2122 V SDL/APP :
03-20 09:07:24.181 2082 2122 V SDL/APP : Hints:

03-20 09:07:24.184 2082 2122 V SDL/APP : Leave sdlwindow_init
03-20 09:07:24.217 2082 2082 V SDL : onWindowFocusChanged(): true
03-20 09:07:24.218 2082 2122 V SDL/APP : Enter sdl_info::create
03-20 09:07:24.224 489 531 I chatty : uid=1000(system) android.display expire 1 line
03-20 09:07:24.228 2082 2122 V SDL : getNativeSurface()
03-20 09:07:24.229 2082 2122 D mali_winsys: EGLint new_window_surface(egl_winsys_display *, void *, EGLSurface, EGLConfig, egl_winsys_surface **, egl_color_buffer_format *, EGLBoolean) returns 0x3000
03-20 09:07:24.229 2082 2122 V SDL/APP : int renderer_bgfx::create()
03-20 09:07:24.229 2082 2122 V SDL/APP : width 1280 height 1024
03-20 09:07:24.229 2082 2122 V SDL/APP : backend as vulkan
03-20 09:07:24.229 2082 2122 V SDL/APP : Calling bgfx::INIT 888
03-20 09:07:24.230 2082 2122 D : BGFX bgfx init
03-20 09:07:24.230 2082 2122 D : BGFX NULL == _init.allocator calling BX_NEW
03-20 09:07:24.230 2082 2122 D : BGFX NULL == _init.callback calling stub
03-20 09:07:24.230 2082 2122 D : ../../../../../3rdparty/bgfx/src/bgfx.cpp (3371): BGFX bgfx platform data like window handle or backbuffer is not set, creating headless device.
03-20 09:07:24.230 2082 2122 D : ../../../../../3rdparty/bgfx/src/bgfx.cpp (3402): BGFX Init...
03-20 09:07:24.230 2082 2122 D : ../../../../../3rdparty/bgfx/src/bgfx.cpp (1761): BGFX g_platformData is NULL - 0x0 0x0 0x0 0x0 0x0
03-20 09:07:24.231 2082 2122 D : ../../../../../3rdparty/bgfx/src/bgfx.cpp (1791): BGFX Creating rendering thread.
03-20 09:07:24.232 2082 2122 D : ../../../../../3rdparty/bgfx/src/bgfx.cpp (1800): BGFX Running in multi-threaded mode
03-20 09:07:24.232 2082 2124 D : ../../../../../3rdparty/bgfx/src/bgfx.cpp (2572): BGFX Scoring in BX_PLATFORM_ANDROID
03-20 09:07:24.232 2082 2124 D :
03-20 09:07:24.232 2082 2124 D : ../../../../../3rdparty/bgfx/src/bgfx.cpp (2572): BGFX Scoring in BX_PLATFORM_ANDROID
03-20 09:07:24.232 2082 2124 D :
03-20 09:07:24.232 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (4190): BGFX RendererContextI* rendererCreate(const Init& _init)
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (4192): BGFX s_renderVK -
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1105): BGFX INIT CALLED
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1124): BGFX 1
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1130): BGFX 2
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1141): BGFX 3
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1153): BGFX 4
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1162): BGFX Shared library functions:
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1167): BGFX 0xeba2986d vkCreateInstance
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1167): BGFX 0xeba299bd vkGetInstanceProcAddr
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1167): BGFX 0xeba2987b vkGetDeviceProcAddr
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1167): BGFX 0xeba29b59 vkEnumerateInstanceExtensionProperties
03-20 09:07:24.235 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1167): BGFX 0xeba29b55 vkEnumerateInstanceLayerProperties
03-20 09:07:24.238 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (576): BGFX ENTERING DUMPEXTENSIONS
03-20 09:07:24.238 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (579): BGFX ENTERING DUMPEXTENSIONS1
03-20 09:07:24.243 2082 2124 D vulkan : searching for layers in '/data/app/org.mamedev.mame-FTGcdIQJrHLGRwuuNuwHlA==/lib/arm'
03-20 09:07:24.243 2082 2124 D vulkan : searching for layers in '/system/fake-libs'
03-20 09:07:24.244 2082 2124 D vulkan : searching for layers in '/data/app/org.mamedev.mame-FTGcdIQJrHLGRwuuNuwHlA==/base.apk!/lib/armeabi-v7a'
03-20 09:07:24.245 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (585): BGFX ENTERING DUMPEXTENSIONS2
03-20 09:07:24.245 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (599): BGFX Global extensions (6):
03-20 09:07:24.245 2082 2124 D :
03-20 09:07:24.245 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (290): BGFX v25 VK_KHR_surface
03-20 09:07:24.245 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (290): BGFX v6 VK_KHR_android_surface
03-20 09:07:24.245 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (290): BGFX v3 VK_EXT_swapchain_colorspace
03-20 09:07:24.245 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (290): BGFX v1 VK_KHR_get_surface_capabilities2
03-20 09:07:24.245 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (290): BGFX v9 VK_EXT_debug_report
03-20 09:07:24.245 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (290): BGFX v1 VK_KHR_get_physical_device_properties2 (supported)
03-20 09:07:24.246 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (614): BGFX 2enumerateLayerProperties
03-20 09:07:24.246 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (616): BGFX 1enumerateLayerProperties - 0, result - 0
03-20 09:07:24.246 2082 2124 D :
03-20 09:07:24.246 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (669): BGFX EXITING DUMPEXTENSIONS
03-20 09:07:24.246 2082 2124 D :
03-20 09:07:24.246 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1224): BGFX numEnabledExtensions - 3: extension.m_name - VK_KHR_get_physical_device_properties2
03-20 09:07:24.243 2082 2082 I SDLThread: type=1400 audit(0.0:137): avc: denied { open } for path="/dev/__properties__/u:object_r:bluetooth_a2dp_offload_prop:s0" dev="tmpfs" ino=9414 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:bluetooth_a2dp_offload_prop:s0 tclass=file permissive=1
03-20 09:07:24.243 2082 2082 I SDLThread: type=1400 audit(0.0:138): avc: denied { getattr } for path="/dev/__properties__/u:object_r:bluetooth_a2dp_offload_prop:s0" dev="tmpfs" ino=9414 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:bluetooth_a2dp_offload_prop:s0 tclass=file permissive=1
03-20 09:07:24.243 2082 2082 I SDLThread: type=1400 audit(0.0:139): avc: denied { open } for path="/dev/__properties__/u:object_r:bluetooth_prop:s0" dev="tmpfs" ino=9415 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:bluetooth_prop:s0 tclass=file permissive=1
03-20 09:07:24.243 2082 2082 I SDLThread: type=1400 audit(0.0:140): avc: denied { getattr } for path="/dev/__properties__/u:object_r:bluetooth_prop:s0" dev="tmpfs" ino=9415 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:bluetooth_prop:s0 tclass=file permissive=1
03-20 09:07:24.243 2082 2082 I SDLThread: type=1400 audit(0.0:141): avc: denied { open } for path="/dev/__properties__/u:object_r:bootloader_boot_reason_prop:s0" dev="tmpfs" ino=9416 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:bootloader_boot_reason_prop:s0 tclass=file permissive=1
03-20 09:07:24.262 2082 2124 I mali_so : [File] : hardware/XXXXXX/mali_so/driver/product/base/src/mali_base_kbase.c; [Line] : 876; [Func] : base_context_deal_with_version_affairs_rk_ext;
03-20 09:07:24.262 2082 2124 I mali_so : arm_release_ver of this mali_so is 'r18p0-01rel0', rk_so_ver is '3@0'.
03-20 09:07:24.263 2082 2124 D mali_so : [File] : hardware/XXXXXX/mali_so/driver/product/base/src/mali_base_kbase.c; [Line] : 881; [Func] : base_context_deal_with_version_affairs_rk_ext;
03-20 09:07:24.263 2082 2124 D mali_so : current process is NOT sf, to bail out.
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1249): BGFX vkCreateinstance result - 0 m_instance - -365055928
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1258): BGFX Instance functions:
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba25b25 vkDestroyInstance
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba2ba29 vkEnumeratePhysicalDevices
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba2626d vkEnumerateDeviceExtensionProperties
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba26211 vkEnumerateDeviceLayerProperties
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xdb5e25b8 vkGetPhysicalDeviceProperties
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xdb5e2af0 vkGetPhysicalDeviceFormatProperties
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xdb5e3020 vkGetPhysicalDeviceFeatures
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xdb5e2b70 vkGetPhysicalDeviceImageFormatProperties
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xdb5e2a38 vkGetPhysicalDeviceMemoryProperties
03-20 09:07:24.282 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xdb5e2a94 vkGetPhysicalDeviceMemoryProperties2KHR
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xdb5e2f58 vkGetPhysicalDeviceQueueFamilyProperties
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba2f921 vkGetPhysicalDeviceSurfaceCapabilitiesKHR
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba2fa8d vkGetPhysicalDeviceSurfaceFormatsKHR
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba2fcc1 vkGetPhysicalDeviceSurfacePresentModesKHR
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba2f875 vkGetPhysicalDeviceSurfaceSupportKHR
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba25bb9 vkCreateDevice
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba2604d vkDestroyDevice
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba2f83d vkDestroySurfaceKHR
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0x0 vkCreateDebugReportCallbackEXT
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0x0 vkDestroyDebugReportCallbackEXT
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0x0 vkDebugReportMessageEXT
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba2f72d vkCreateAndroidSurfaceKHR
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1295): BGFX ---
03-20 09:07:24.283 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1328): BGFX Physical device 0:
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1329): BGFX Name: Mali-T860
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1330): BGFX API version: 400027
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1331): BGFX Driver version: e7ca91ce
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1332): BGFX VendorId: 13b5
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1333): BGFX DeviceId: 8602000
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1334): BGFX Type: 1
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1350): BGFX Memory type count: 3
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1357): BGFX 0: flags 0x00000007, index 0
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1357): BGFX 1: flags 0x0000000b, index 0
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1357): BGFX 2: flags 0x00000011, index 0
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1360): BGFX Memory heap count: 1
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1369): BGFX 0: flags 0x00000001, size 3.75 GiB
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (576): BGFX ENTERING DUMPEXTENSIONS
03-20 09:07:24.284 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (579): BGFX ENTERING DUMPEXTENSIONS1
03-20 09:07:24.287 2082 2124 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
03-20 09:07:24.288 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (585): BGFX ENTERING DUMPEXTENSIONS2
03-20 09:07:24.288 2082 2124 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
03-20 09:07:24.288 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (599): BGFX Global extensions (2):
03-20 09:07:24.288 2082 2124 D :
03-20 09:07:24.288 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (290): BGFX v1 VK_KHR_incremental_present
03-20 09:07:24.288 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (290): BGFX v70 VK_KHR_swapchain
03-20 09:07:24.288 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (614): BGFX 2enumerateLayerProperties
03-20 09:07:24.288 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (616): BGFX 1enumerateLayerProperties - 0, result - 0
03-20 09:07:24.288 2082 2124 D :
03-20 09:07:24.288 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (669): BGFX EXITING DUMPEXTENSIONS
03-20 09:07:24.288 2082 2124 D :
03-20 09:07:24.288 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1377): BGFX VK_NULL_HANDLE == m_physicalDevice
03-20 09:07:24.288 2082 2124 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1455): BGFX Supported 8

03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0x0 vkCreateDebugReportCallbackEXT
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0x0 vkDestroyDebugReportCallbackEXT
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0x0 vkDebugReportMessageEXT
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1264): BGFX 0xeba2f72d vkCreateAndroidSurfaceKHR
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1295): BGFX ---
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1328): BGFX Physical device 0:
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1329): BGFX Name: Mali-T860
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1330): BGFX API version: 400027
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1331): BGFX Driver version: e7ca91ce
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1332): BGFX VendorId: 13b5
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1333): BGFX DeviceId: 8602000
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1334): BGFX Type: 1
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1350): BGFX Memory type count: 3
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1357): BGFX 0: flags 0x00000007, index 0
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1357): BGFX 1: flags 0x0000000b, index 0
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1357): BGFX 2: flags 0x00000011, index 0
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1360): BGFX Memory heap count: 1
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1369): BGFX 0: flags 0x00000001, size 3.75 GiB
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (576): BGFX ENTERING DUMPEXTENSIONS
03-20 10:50:36.566 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (579): BGFX ENTERING DUMPEXTENSIONS1
03-20 10:50:36.570 2222 2263 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
03-20 10:50:36.571 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (585): BGFX ENTERING DUMPEXTENSIONS2
03-20 10:50:36.571 2222 2263 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
03-20 10:50:36.571 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (599): BGFX Global extensions (2):
03-20 10:50:36.571 2222 2263 D :
03-20 10:50:36.571 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (290): BGFX v1 VK_KHR_incremental_present
03-20 10:50:36.571 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (290): BGFX v70 VK_KHR_swapchain
03-20 10:50:36.571 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (614): BGFX 2enumerateLayerProperties
03-20 10:50:36.571 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (616): BGFX 1enumerateLayerProperties - 0, result - 0
03-20 10:50:36.571 2222 2263 D :
03-20 10:50:36.571 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (669): BGFX EXITING DUMPEXTENSIONS
03-20 10:50:36.571 2222 2263 D :
03-20 10:50:36.571 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1377): BGFX VK_NULL_HANDLE == m_physicalDevice
03-20 10:50:36.571 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1455): BGFX Supported 8
03-20 10:50:36.571 2222 2263 I chatty : uid=10045(u0_a45) org.mamedev.mame identical 145 lines
03-20 10:50:36.578 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1495): BGFX Queue family property 0:
03-20 10:50:36.579 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1496): BGFX Queue flags: 0x00000007
03-20 10:50:36.579 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1497): BGFX Queue count: 2
03-20 10:50:36.579 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1498): BGFX TS valid bits: 0x00000000
03-20 10:50:36.579 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1503): BGFX Min image: 1 x 1 x 1
03-20 10:50:36.579 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1564): BGFX Extension::Count - 4
03-20 10:50:36.579 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1598): BGFX Device being created+++++++++++++++
03-20 10:50:36.579 2222 2263 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
03-20 10:50:36.579 2222 2263 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
03-20 10:50:36.594 2222 2263 I mali_so : [File] : hardware/XXXXXX/mali_so/driver/product/base/src/mali_base_kbase.c; [Line] : 876; [Func] : base_context_deal_with_version_affairs_rk_ext;
03-20 10:50:36.594 2222 2263 I mali_so : arm_release_ver of this mali_so is 'r18p0-01rel0', rk_so_ver is '3@0'.
03-20 10:50:36.594 2222 2263 D mali_so : [File] : hardware/rXXXXXX/mali_so/driver/product/base/src/mali_base_kbase.c; [Line] : 881; [Func] : base_context_deal_with_version_affairs_rk_ext;
03-20 10:50:36.594 2222 2263 D mali_so : current process is NOT sf, to bail out.
03-20 10:50:36.612 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1605): BGFX Device created++++++++++++++
03-20 10:50:36.612 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1615): BGFX Device functions:
03-20 10:50:36.612 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1620): BGFX 0xeba2bced vkGetDeviceQueue

TOO MANY HERE

03-20 10:50:36.615 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1622): BGFX func1
03-20 10:50:36.615 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1628): BGFX func2
03-20 10:50:36.615 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1630): BGFX func3
03-20 10:50:36.615 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1632): BGFX func4
03-20 10:50:36.615 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1645): BGFX func5
03-20 10:50:36.615 2222 2263 D : ../../../../../3rdparty/bgfx/src/renderer_vk.cpp (1652): BGFX func6 m_instance - c9aa5900 m_allocatorCb - 0 sci.window - 0x0
A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x58
6 298 Read More
MAME Jump to new posts
Re: The mysteries of N64 microcodes Happy 03/18/20 09:03 PM
Having disassembled many different N64 microcodes, I find it sort of interesting. All the microcodes have to deal with the issue of IMEM and DMEM being very limited in size, so there are a few different techniques to stream data in and out. However with respect to MAME, I think more of the issues with MAME's N64 emulation of the RSP are related to timing issues and synchronization with the rest of the N64 components..

Also you can optimize the RSP code all you want, but the RDP and memory bandwidth are still going to be major factors in the overall performance that you can't do much to optimize.
5 488 Read More
MAME Jump to new posts
Re: TMS-09xx/1xxx thread (was New Dumps) DarthMarino 03/17/20 11:04 AM
Originally Posted by Rik
Originally Posted by DarthMarino
I don't think there's anything I will change on Crab Grab since it doesn't really have a background image to clean-up or rework. I'm pretty happy with everything on my drive. Someone requested a unit-only with black background view for the Table Top units, so I will be adding those soon, that's likely it for any major changes.


Should the little ovals around the Game A/Game B buttons be silver on the 'white version'? I can't tell if that would be the chromed plastic, or if that is part of the (I assume) aluminum sticker with the printing on it...

Just being nit-picky! Never seen these in person. smile


Not nitpicking at all. I checked and they are indeed white. Good call! I have updated it.

Game & Watch Artwork
3,511 2,194,670 Read More
MAME Jump to new posts
Re: Use of Stable Controller IDs illando 03/16/20 01:53 AM
You are right, I extensively tested Mame 0.218 and it's working by accident when everything's plugged in.

But during the past, I remember I used it a lot, so I tried with an old version, Mame 0.203, and I can assure you, It's working perfectly. Also in case one of the controller is not connected, it keeps the position assigned.
For example, if I unplug controller #1 and start MAME with just #2 and #3 connected they keeps their position, and #1 remains unassigned (you must use the keyboard).

This is the content of my .cfg file placed inside the "ctrlr" folder:

<mameconfig version="10">
<system name="default">
<input>
<mapdevice device="8BitdoNES30Arcade" controller="JOYCODE_1" />
<mapdevice device="Nimbus" controller="JOYCODE_2" />
<mapdevice device="PLAYSTATION(R)3Controller" controller="JOYCODE_3" />
<mapdevice device="PS4Controller" controller="JOYCODE_4" />
</input>
</system>
</mameconfig>

Would you be able to bring back that function please? It was awesome!
6 363 Read More
MAME Jump to new posts
Re: ex- USSR and Soviet Bloc hardware shattered 03/13/20 11:09 AM
rt1715w WIP -- card games, using loadable chargen for graphics:

[Linked Image from i.imgur.com]
368 317,551 Read More
MAME Jump to new posts
Re: PC/XT/AT (inside) WIP topic rfka01 03/09/20 06:09 PM
Right, thanks! I dumped these as 27C512 EPROMs, so I hope the dumps are correct.
2,658 4,399,142 Read More
MAME Jump to new posts
Re: 8bit Apples - Apple I, II, /// and the 16 bit GS R. Belmont 03/08/20 04:31 AM
GSPlus-compatible host file I/O is starting to work in the IIgs driver for the ProDOS 8 version of the protocol. Here's BASIC.SYSTEM CATALOGing MAME's src/devices/bus directory.

[Linked Image from rbelmont.mameworld.info]
521 100,165 Read More
MAME Jump to new posts
Re: Linux screen tearing in portrait mode RomKnight 03/06/20 07:26 PM
Originally Posted by R. Belmont
Syncrefresh is a really bad idea, it makes the game run at the monitor's refresh rate. There are almost zero drivers in MAME where 60 or 70/72/74 Hz is right. Waitvsync is the correct flag; if your graphics driver doesn't respect it (which is unfortunately a thing on Linux), try different -video settings.



This might explain some WTF moments like the ball in arkanoid collision detection in vaus sides as sometimes I swear I at the right place in time to it the ball.

I'll try waitvsync but isn't it this one that adds input lag by enabling vsync? I need to reread what all those do. Been a while since I've done it.

Anyway as far as tearing goes, i don't notice it with above settings. I may have to decide between tearing, accuracy, lag apparently...

Thanks for the hints.

/edit
Well, syncrefresh or waitvsync have no influence on tearing (for me). I do feel something different in gameplay though, especially in sf2, snowbors... like the games are faster. But i've been wrong before.
8 512 Read More
MAME Jump to new posts
Re: Per system custom INIs (cps1, segas24...)? pakoman 03/06/20 11:50 AM
Great! Just was missing placing them in the "source" folder.

Thanks so much!
2 175 Read More
MAME Jump to new posts
Re: Create CHD with FreeDOS inside. rfka01 03/03/20 09:00 PM
Hi Carlo,

get Freedos from https://www.freedos.org/download/ (use the boot floppy from FD12FLOPPY.ZIP, unpack the floppy image.
This installer expects you to download the CD image as well for a full install, but you can use just the boot floppy for a basic install.

Then open a command line window and move to your MAME directory.

Create a CHD file with

Code
chdman createhd -c none -o 820-6-17_harddisk.chd -chs 820,6,17 


I've used the track/head/sector values from a Seagate ST 251. You should see CHDMAN create the harddisk file.

Open MAME with the ct486 driver. This is handy as its BIOS can autotype the harddisk, and you can assign a nice amount of RAM:

Code
mess64 ct486 -window -ramsize 16M


TAB into MAME's file manager and attach the FreeDOS floppy image to the first floppy drive and the harddisk image to the harddisk slot. RESET!!!

On the next boot, enter the emulated PC's BIOS, choose "Auto detect hard disk", your CHD file should be picked up, the second harddisk should be empty.
Then enter the standard CMOS settings, set both floppy drives for 1.44MB, exit to the main BIOS menu and enter Advanced CMOS settings.

Set "System boot up sequence" to "A:, C:"

Exit to the main BIOS menu, select "Write to CMOS and exit" and reboot the emulated computer.

It will boot from the Freedos disk - ignore the error message, your harddisk image is completely blank.

Select your preferred language, then exit the installer to DOS. Issue "FDISK"

Depending on the size of your disk, select FAT32 support, create a DOS primary partition, set it active and exit FDISK, then REBOOT!!!

The disk will take you through the language selection again, exit the installer, then issue "FORMAT C: /S" and confirm with "YES".

After formatting the hard disk image, issue "MD C:\DOS" and "COPY FDSETUP\BIN\*.* C:\DOS"

This will copy a base system onto your harddisk.

TAB into MAME's menu, select file manager and empty the Floppy slot. Reboot, and FreeDOS starts from harddisk.


This should get you going.



1 508 Read More
MAME Jump to new posts
Re: mslug "render" problem? Haze 03/02/20 11:37 AM
Yeah, same, it's been like that for a while.
4 354 Read More
MAME Jump to new posts
Re: MAME 0.219 Shoegazer 03/01/20 05:53 AM
Thanks RB. This was a clean source tree. However, I recently compiled a custom Qt5 since this distro's version is way outdated. I can't get it to recognize the new version as the default though, so sometimes I run into issues like this and I have to force recognition manually, so it looks like I'll have to do that for mame from now on (I just did and it compiles fine now).
19 750 Read More
Who's Online Now
3 registered members (mfm005, box, AJR), 114 guests, and 3 spiders.
Key: Admin, Global Mod, Mod
ShoutChat Box
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics8,762
Posts115,156
Members4,888
Most Online890
Jan 17th, 2020
Powered by UBB.threads™ PHP Forum Software 7.7.3