LIBGL: Initialising gl4es LIBGL: v1.1.1 built on Dec 20 2018 17:02:06 LIBGL: Using GLES 2.0 backend LIBGL: Using Warp3DNova.library v1 revision 61 LIBGL: Warning, your Warp3DNovaBase.library is too old, minimum is v1.62, please update! LIBGL: Using OGLES2.library v1 revision 22 LIBGL: OGLES2 Library and Interface open successfuly LIBGL: Targeting OpenGL 2.0 LIBGL: Forcing NPOT support by disabling MIPMAP support for NPOT textures LIBGL: Current folder is:RAM Disk:Barony [19-26-31] Data path is PROGDIR: [19-26-31] Output path is PROGDIR:.barony LIBGL: Hardware test on current Context... LIBGL: Hardware Limited NPOT detected and used LIBGL: FBO are in core, and so used LIBGL: PointSprite are in core, and so used LIBGL: CubeMap are in core, and so used LIBGL: BlendColor is in core, and so used LIBGL: Blend Substract is in core, and so used LIBGL: Blend Function and Equation Separation is in core, and so used LIBGL: Texture Mirrored Repeat is in core, and so used LIBGL: Extension GL_OES_element_index_uint detected and used LIBGL: Extension GL_EXT_texture_format_BGRA8888 detected and used LIBGL: Extension GL_OES_texture_float detected and used LIBGL: high precision float in fragment shader available and used LIBGL: Extension GL_EXT_frag_depth detected and used LIBGL: Max vertex attrib: 16 LIBGL: Max texture size: 16384 LIBGL: Max Varying Vector: 32 LIBGL: Texture Units: 8(8), Max lights: 8, Max planes: 6 LIBGL: Extension GL_EXT_texture_filter_anisotropic detected and used LIBGL: Max Anisotropic filtering: 16 LIBGL: Hardware vendor is A-EON Technology Ltd. Written by Daniel 'Daytonta675x' Müßener @ GoldenCode.eu LIBGL: OGLES2 Library and Interface closed
@ddni On x1000 shouldnt be slow. Are you on sfs ? If so, try from ngfs.
As for dirty exit, its probably odyssey, not barony :) Try after reboot, etc. Be sure all datafiles correct and dirs of size i show, or there can be memory leaks if no all data files correct
I'ts ok but when I lose the game and wanted to ga bakc to main menu, game crashed.
log.txt:
[23-54-22] You die... [23-54-22] deleting savegame in 'PROGDIR:.barony/savegames/savegame0.dat'... [23-54-22] deleting savegame in 'PROGDIR:.barony/savegames/savegame0_npcs.dat'... [23-54-34] LoadMap PROGDIR:/maps/mainmenu1.lmp
CrashLog:
Crash log for task "Barony.exe" Generated by GrimReaper 53.19 Crash occured in module Barony.exe at address 0x7CA76C30 Type of crash: DSI (Data Storage Interrupt) exception Alert number: 0x80000003
There i again open dos library / IDOS and close in the playmusic() routine. All of which suck, as why it didn't works on public ones are strange, but whatever if it make it works.
If I understand it correctly, the IDOS symbol should be provided by the C lib startup code. A "helloworld" example shows symbol here as "S" and pointer is non-zero. With GCC4.
Barony seems to use CMake so I couldn't see the makefile that produces the binary.
Assuming pointer is non-zero right in the main() function, I don't know how it could be NULL later unless some cleanup code (?) is ran or heap corruption? Strange.
@Capehill Cmake used for build objects, but final linking line are my own, which i do at end manually. I am not at home, but will show the line later.
Strange thing that all fine in all beta setups (and on x1000, and on x5000, and on sam460).
I at moment have a guess that it maybe related to newer gcc and native threading. If you check adtools repo, few days ago there was some fix in native threading , but dunno if it at all related.
But why problems only on public oses and not on betas.. Maybe elf.library related
And its only from barony's code, which is c++11 / threads
And dunno if in main() IDOS is not null (didnt checked that), i think it can be null as well. Because any call to dos are 0x0000000, once first function called. But #include <proto/dos.h> is here, so wtf..
There dos calls happens to be from libphysfs.a and libopenal.a (in both cases , their code have #include <proto/dos.h>). So when it firstly start to crash at physfs, we realise that just pure adding of any DOS call inside of initApp() from init.cpp file of barony , even when added #include <proto/dos.h> , fail as well.
I tried to compile simple test cases with any dos call from, but exactly 1:1 the same compiling and linking lines : all works fine, but then, those simple test cases have no needs for all those linker libs of course (which may cause issues).
@all Reuploaded new version on os4depot, so far changes are:
-- get rid of double "PROGDIR:PROGDIR:" and "PROGDIR:/" constructs (last one cause crashes on SFS). So Barony now works on SFS, but NGFS still _VERY_ recomended, as SFS produce lags in game (you may notice some micro pauses)
-- added workaround to make it works on non-beta OS => on latest public versions IDOS pointer looses in the deep of c++11/native threads from Barony's code somehow, so we open dos.library/IDOS interface again to make physfs and openal works. For next update of OS all will works even as it was, but one more time open dos.library/IDOS make no harm anyway.
-- stack cookie was 100.000, just in case made it 1.000.000 to avoid any possible problems
-- added amigaos4 readme with all necessary information (so everything is more clear how install it all and co).