FAangband 2.0beta

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Arralen
    replied
    Originally posted by backwardsEric
    It's likely the Angband releases are also affected.
    Nope, 4.2.2. works fine for me

    Although I think NILWIN the kobold wander won't get very far ...

    Leave a comment:


  • backwardsEric
    replied
    Originally posted by Nick
    There was some change in how the windows build gets packaged after that build, but it's mainly to do with documentation. If there's a .dll file named in the error, it's possible that it's one that's newly required by later builds and your system doesn't have it or has a version that doesn't work - but I'm guessing here.
    It looks like the releases that fail on Windows 8.1 were built with MinGW on Ubuntu 20.04 LTS (Ubuntu's package list says mingw-w64 is 7.0.0-2) rather Ubuntu 18.04 LTS (Ubuntu's package list says mingw-w64 is 5.0.3-1). Could set the release script to only run Ubuntu 18.04 LTS or figure out if there's something that can be set so the builds on Ubuntu 20.04 LTS will be compatible with Windows 8.1. It's likely the Angband releases are also affected.

    Leave a comment:


  • Arralen
    replied
    Had a look into the system log, and used process explorer to spy amateurishly on faangband.exe ... here's what I found:

    SYSTEM LOG:
    Code:
    Log name: Application
    Source: Application Error
    Date: 03/14/2021 22:47:09
    Event ID: 1000
    Task category:(100)
    Level: Error
    Keywords:Classic
    User: Not applicable
    Computer: 4Foen
    Description:
    Failed application name: faangband.exe, version: 0.0.0.0, timestamp: 0x602ece2f
    Name of the corrupted module: eta1-87-g5abab8fa\faangband.exe!                
    , version: 6.3.9600.19678, timestamp: 0x5e82c0f7
    Exception code: 0xc0000139
    Error offset: 0x0009d452
    ID of the faulty process: 0x1ad8
    Start time of the faulty application: 0x01d7191b94ec6129
    Path of the corrupted application: E:\_noinstall_games_\_command_line_\FAangband 2\FAangband-2.0beta1-87-g5abab8fa\faangband.exe
    Path of the corrupted module: eta1-87-g5abab8fa\faangband.exe
    Berichtskennung: d36a4f8d-850e-11eb-8cc0-fcaa142d66aa
    Full name of the corrupted package: 
    Application ID relative to the corrupted package:
    Note the version number - the only thing with this version number is NTDLL.DLL itself ...

    Here's the list of DLLs that Process Explorer thinks are associated with a running FAangband.exe.
    Everything marked with (*) did not load for v0.87 compared to v0.85.
    Code:
    Process	PID	CPU	Description	Company Name
    System Idle Process	0	94.23		
     System	4	0.77		
      smss.exe	340		Windows-Sitzungs-Manager	Microsoft Corporation
    csrss.exe	468		Client-Server-Laufzeitprozess	Microsoft Corporation
    wininit.exe	544		Windows-Startanwendung	Microsoft Corporation
     services.exe	584		Anwendung für Dienste und Controller	Microsoft Corporation
      svchost.exe	736		Hostprozess für Windows-Dienste	Microsoft Corporation
       explorer.exe	4760		Windows-Explorer	Microsoft Corporation
        procexp64.exe	6792	0.38	Sysinternals Process Explorer	Sysinternals - www.sysinternals.com
        faangband.exe	6744			
    
    Process: faangband.exe Pid: 6744
    
    Name	Description	Company Name	Path	Version
    ADVAPI32.dll	Erweiterte Windows 32 Base-API	Microsoft Corporation	C:\Windows\SysWOW64\ADVAPI32.dll	6.3.9600.18895
    * bcryptPrimitives.dll	Windows Cryptographic Primitives Library	Microsoft Corporation	C:\Windows\SysWOW64\bcryptPrimitives.dll	6.3.9600.18895
    cfgmgr32.dll	Configuration Manager DLL	Microsoft Corporation	C:\Windows\SysWOW64\cfgmgr32.dll	6.3.9600.17415
    combase.dll	Microsoft COM für Windows	Microsoft Corporation	C:\Windows\SysWOW64\combase.dll	6.3.9600.19846
    COMCTL32.dll	Bibliothek für Steuerelemente	Microsoft Corporation	C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17810_none_7c5b6194aa0716f1\COMCTL32.dll	5.82.9600.17810
    COMDLG32.DLL	DLL für gemeinsame Dialoge	Microsoft Corporation	C:\Windows\SysWOW64\COMDLG32.DLL	6.3.9600.17415
    * CRYPTBASE.dll	Base cryptographic API DLL	Microsoft Corporation	C:\Windows\SysWOW64\CRYPTBASE.dll	6.3.9600.17415
    DEVOBJ.dll	Device Information Set DLL	Microsoft Corporation	C:\Windows\SysWOW64\DEVOBJ.dll	6.3.9600.17415
    * dwmapi.dll	Microsoft Desktopfenster-Manager-API	Microsoft Corporation	C:\Windows\SysWOW64\dwmapi.dll	6.3.9600.17415
    faangband.exe			E:\_noinstall_games_\_Kommandozeile_\FAangband 2\FAangband-2.0beta1-85-gaca9e322\faangband.exe	
    GDI32.dll	GDI Client DLL	Microsoft Corporation	C:\Windows\SysWOW64\GDI32.dll	6.3.9600.19920
    * IMM32.DLL	Multi-User Windows IMM32 API Client DLL	Microsoft Corporation	C:\Windows\SysWOW64\IMM32.DLL	6.3.9600.17415
    * kernel.appcore.dll	AppModel API Host	Microsoft Corporation	C:\Windows\SysWOW64\kernel.appcore.dll	6.3.9600.17415
    KERNEL32.DLL	Client-DLL für Windows NT-Basis-API	Microsoft Corporation	C:\Windows\SysWOW64\KERNEL32.DLL	6.3.9600.19843
    KERNELBASE.dll	Client-DLL für Windows NT-Basis-API	Microsoft Corporation	C:\Windows\SysWOW64\KERNELBASE.dll	6.3.9600.19724
    libpng12.dll	Libpng12: PNG image compression library	GnuWin32 <http://gnuwin32.sourceforge.net>	E:\_noinstall_games_\_Kommandozeile_\FAangband 2\FAangband-2.0beta1-85-gaca9e322\libpng12.dll	1.2.37.3442
    locale.nls			C:\Windows\System32\locale.nls	
    * MSCTF.dll	MSCTF-Server-DLL	Microsoft Corporation	C:\Windows\SysWOW64\MSCTF.dll	6.3.9600.19724
    MSIMG32.DLL	GDIEXT Client DLL	Microsoft Corporation	C:\Windows\SysWOW64\MSIMG32.DLL	6.3.9600.17415
    msvcrt.dll	Windows NT CRT DLL	Microsoft Corporation	C:\Windows\SysWOW64\msvcrt.dll	7.0.9600.17415
    ntdll.dll	DLL für NT-Layer	Microsoft Corporation	C:\Windows\SYSTEM32\ntdll.dll	6.3.9600.19678
    ntdll.dll	DLL für NT-Layer	Microsoft Corporation	C:\Windows\SysWOW64\ntdll.dll	6.3.9600.19678
    * ole32.dll	Microsoft OLE für Windows	Microsoft Corporation	C:\Windows\SysWOW64\ole32.dll	6.3.9600.19810
    * RPCRT4.dll	Remoteprozeduraufruf-Laufzeitumgebung	Microsoft Corporation	C:\Windows\SysWOW64\RPCRT4.dll	6.3.9600.19919
    * sechost.dll	Host for SCM/SDDL/LSA Lookup APIs	Microsoft Corporation	C:\Windows\SysWOW64\sechost.dll	6.3.9600.19749
    * SHCORE.DLL	SHCORE	Microsoft Corporation	C:\Windows\SysWOW64\SHCORE.DLL	6.3.9600.19750
    SHELL32.dll	Allgemeine Windows-Shell-DLL	Microsoft Corporation	C:\Windows\SysWOW64\SHELL32.dll	6.3.9600.19823
    SHLWAPI.dll	Shell Light-weight-Hilfsprogrammbibliothek	Microsoft Corporation	C:\Windows\SysWOW64\SHLWAPI.dll	6.3.9600.17415
    * SortDefault.nls			C:\Windows\Globalization\Sorting\SortDefault.nls	
    * SspiCli.dll	Security Support Provider Interface	Microsoft Corporation	C:\Windows\SysWOW64\SspiCli.dll	6.3.9600.18454
    * StaticCache.dat			C:\Windows\Fonts\StaticCache.dat	
    USER32.dll	Multi-User Windows USER API Client DLL	Microsoft Corporation	C:\Windows\SysWOW64\USER32.dll	6.3.9600.19920
    * uxtheme.dll	Microsoft UxTheme-Bibliothek	Microsoft Corporation	C:\Windows\SysWOW64\uxtheme.dll	6.3.9600.19597
    WINMM.DLL	MCI API-DLL	Microsoft Corporation	C:\Windows\SysWOW64\WINMM.DLL	6.3.9600.17415
    WINMMBASE.dll	Base Multimedia Extension API DLL	Microsoft Corporation	C:\Windows\SysWOW64\WINMMBASE.dll	6.3.9600.17415
    wow64.dll	Win32 Emulation on NT64	Microsoft Corporation	C:\Windows\SYSTEM32\wow64.dll	6.3.9600.19629
    wow64cpu.dll	AMD64 Wow64 CPU 	Microsoft Corporation	C:\Windows\system32\wow64cpu.dll	6.3.9600.18931
    wow64win.dll	Wow64 Console and Win32 API Logging	Microsoft Corporation	C:\Windows\system32\wow64win.dll	6.3.9600.19574
    zlib1.dll	Zlib: general purpose data compression / decompression library	Zlib	E:\_noinstall_games_\_Kommandozeile_\FAangband 2\FAangband-2.0beta1-85-gaca9e322\zlib1.dll	1.2.3.2027
    Now, if it loaded NT.DLL and then quit - I'll have a hard time replacing my NTDLL.DLL with a newer version
    Last edited by Arralen; March 14, 2021, 23:03.

    Leave a comment:


  • Nick
    replied
    Originally posted by Arralen
    Sadly, most of them don't help me much ... everything after beta1-85-gaca9e322 says something like:
    "The procedure entry point " " was not found in the DLL "E:\ ..... \FAangband 2\FAangband-2.0beta1-87-g5abab8fa\faangband.exe" and refuses to run

    I am running Win8.1(64), if that matters.
    There was some change in how the windows build gets packaged after that build, but it's mainly to do with documentation. If there's a .dll file named in the error, it's possible that it's one that's newly required by later builds and your system doesn't have it or has a version that doesn't work - but I'm guessing here.

    Leave a comment:


  • Arralen
    replied
    Originally posted by Nick
    Thanks. All is fine, it's just been RL interfering with my Angband life
    Yet you got out a new release 5 days ago ... yeah!

    So I am only 16 releases late to the party

    Sadly, most of them don't help me much ... everything after beta1-85-gaca9e322 says something like:
    "The procedure entry point " " was not found in the DLL "E:\ ..... \FAangband 2\FAangband-2.0beta1-87-g5abab8fa\faangband.exe" and refuses to run

    I am running Win8.1(64), if that matters.

    Leave a comment:


  • Nick
    replied
    Originally posted by Ingwe Ingweron
    Glad to see you're back, Nick. Hope all is well.
    Thanks. All is fine, it's just been RL interfering with my Angband life

    Leave a comment:


  • Ingwe Ingweron
    replied
    Originally posted by Nick
    Note that there are still many bugs, few of which are properly filed ... (despite Ingwe sending me reams of them).
    Sorry about that, but you found the way to get me to stop -- just don't repair My Crash Bug on level 98 of the angband dungeon.

    Glad to see you're back, Nick. Hope all is well.

    Leave a comment:


  • Nick
    replied
    The latest builds of FA for Windows and macOS can now (similarly to V) be found on its release page.

    Note that there are still many bugs, few of which are properly filed on the issue page (despite Ingwe sending me reams of them). There have been some fixes since 2.0beta1 was released though, so it could be worse

    Leave a comment:


  • Nick
    replied
    Originally posted by tg122
    Started playing FAangband on Termux on my Android phone. This variant is a masterpiece, thanks for continuing to support this after so many years. So here's a question. I was fighting a giant Roc and it said the monster was hitting me for 60 damage for example, but my hitpoints were only reduced by about 20. Is the damage number that is reported before any damage reduction, or was this a bug?
    Looks like a bug. Thanks for the report.

    Leave a comment:


  • tg122
    replied
    Started playing FAangband on Termux on my Android phone. This variant is a masterpiece, thanks for continuing to support this after so many years. So here's a question. I was fighting a giant Roc and it said the monster was hitting me for 60 damage for example, but my hitpoints were only reduced by about 20. Is the damage number that is reported before any damage reduction, or was this a bug?

    Leave a comment:


  • Ingwe Ingweron
    replied
    CRASH bug. Try and look at the objects list "]" and get an instant crash. Ingwe.zip

    Leave a comment:


  • Ingwe Ingweron
    replied
    Nick, here's an example of the @ being walled in upon descent of stairs. This time, if one looks at the location, it says "You are on a permanent wall."

    Ingwe.zip

    Yes, I will just phase door out since @ can do that now. But still a bug.

    EDIT: Also, I think something is wrong with artifact generation. Look at the “Known Artifacts” menu and the only things on there after all this time, are two lights and one staff.
    Last edited by Ingwe Ingweron; January 16, 2021, 02:33.

    Leave a comment:


  • Nick
    replied
    Originally posted by Sideways
    Monsters' hit probability as calculated for display here is probably wrong; it uses the new numbers from Vanilla's test_hit() (12% guaranteed hit chance, a minimum accuracy of 9 and a 2/3 AC multiplier), while FAangband's test_hit() uses a 5% guaranteed hit chance, a minimum accuracy of 0 and (in practice) a 3/4 AC multiplier provided by the check_hit() call.
    Thanks. Pity the maintainer's MIA...

    Leave a comment:


  • Sideways
    replied
    Monsters' hit probability as calculated for display here is probably wrong; it uses the new numbers from Vanilla's test_hit() (12% guaranteed hit chance, a minimum accuracy of 9 and a 2/3 AC multiplier), while FAangband's test_hit() uses a 5% guaranteed hit chance, a minimum accuracy of 0 and (in practice) a 3/4 AC multiplier provided by the check_hit() call.

    Leave a comment:


  • Sacksquatch
    replied
    Had more time to mess around with it. You probably already know this, but yeah the map works fine on sdl. Sdl2 has the map pull up in it's own window, instead of the main window (which is awesome), but that's probably the issue.

    Leave a comment:

Working...
😀
😂
🥰
😘
🤢
😎
😞
😡
👍
👎