Nope, it loads but doesn't run the wads and once I added some directories for wads and such it now crashes whenever opened. Could be my terrible file arranging..
That seems like a bug somewhere in Doomsday's file loading code. Delete the "~/Library/Application Support/Doomsday Engine/runtime/persist.pack" file to reset back to the default config where it shouldn't crash any more.
We should try to narrow down which file(s) it is that are causing it to crash. Try putting the WAD files in one folder, and other kinds of data files in another. It shouldn't crash if you just add the WAD files in Doomsday.
Well, now it doesn't run any version 2x Interestingly, I don't find "~/Library/Application Support/Doomsday Engine/runtime/persist.pack" to exist, nor for that matter the whole "~/Library/Application Support/Doomsday Engine/" folder. So either that folder got trashed or the runtime never actually got installed right, yet somehow managed to produce a working install (I have seen this before in other software)! I also should admit that dengine version 2 got installed overtop version 1.. ;-) So maybe I have to reinstall version 1.x (think it was 1.15.8) then install version 2.x overtop of that..
Hmm, that's very odd that "~/Library/Application Support/Doomsday Engine" isn't there. It is also used in version 1.15.8.
Note that you can also run Doomsday 2 directly from the .dmg file, without installing anything, so at least that way it is guaranteed to have valid contents.
Ok, I've reinstalled #2025 but haven't got the profiles to copy over from my backup drive yet. Not sure what all needs to be copied over and where it's at.
Both the 'include' and 'cmake' folders are in the applications folder. They seem to be complete but I still have no games other than the shareware defaults showing up. Running from the backup drive works fine, though, with all the registered versions working from what appear to be the same locations on that backup drive.
Then again maybe I've missed something. I'm also wondering if I have some kind of permissions issue affecting all this.
I think that all I need is the location of the file(s) Doomsday uses to store the data on what installed game(s) and their episode list(s) are presented to the user for selection at the Doomsday home screen. If I can find that, then I can copy it/them from my backup drive and have the setup running complete again.
Ideally you should transfer the entire "Library/Application Support/Doomsday Engine" folder from your backup, since that contains all the relevant information.
Note that the "Library" subfolder in your macOS user home folder is nowadays hidden by the OS and can only be accessed by manually entering the path. (The shortcut is Command-Shift-G in Finder.)
When it comes to knowing which games are installed, Doomsday looks in the configured IWAD folders for recognized WAD files (such as doom2.wad). These folders can be selected in the ⚙ > Data Files settings. The configured values are actually stored in "~/Library/Application Support/Doomsday Engine/runtime/persist.pack".
If you have created custom game profiles, those are stored in "~/Library/Application Support/Doomsday Engine/runtime/configs/game.dei".
Thanks skyjake! This should solve my problem. Once that's done, I'm going to add the devices I need to upgrade. Besides I don't see the older v2 links anymore, and that's a good thing. Time for Sierra already..
Comments
It has been built with a deployment target of macOS 10.10.
Here's the code:
We should try to narrow down which file(s) it is that are causing it to crash. Try putting the WAD files in one folder, and other kinds of data files in another. It shouldn't crash if you just add the WAD files in Doomsday.
Joe
Process: Doomsday [1666] Path: /Applications/Doomsday.app/Contents/MacOS/Doomsday Identifier: ??? Version: 2.0 (2.0.0) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Doomsday [1666] User ID: 504 Date/Time: 2017-03-04 14:06:29.467 -1000 OS Version: Mac OS X 10.11.6 (15G1217) Report Version: 11 Anonymous UUID: 908240AF-10F5-7692-7FE2-990F5999838A Time Awake Since Boot: 4000 seconds System Integrity Protection: enabled Crashed Thread: 9 Thread (pooled) Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0: --> __TEXT 00000001083a0000-00000001087b4000 [ 4176K] r-x/rwx SM=COW /Applications/Doomsday.app/Contents/MacOS/Doomsday Thread 0:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff8d9c7db6 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff8f25e728 _pthread_cond_wait + 767 2 org.qt-project.QtCore 0x000000010a9205db 0x10a8f5000 + 177627 3 org.qt-project.QtCore 0x000000010a920492 QWaitCondition::wait(QMutex*, unsigned long) + 162 4 org.qt-project.QtCore 0x000000010a91a75f QSemaphore::acquire(int) + 79 5 libdeng_core.dylib 0x000000010a57428b de::Waitable::wait() const + 59 6 libdeng_core.dylib 0x000000010a572dab de::TaskPool::waitForDone() + 27 7 libdeng_doomsday.dylib 0x0000000108f14d0b DoomsdayApp::initialize() + 587 8 0x00000001083d1632 ClientApp::initialize() + 642 9 0x0000000108426ac4 main + 52 10 libdyld.dylib 0x00007fff8afae5ad start + 1 Thread 9 Crashed:: Thread (pooled) 0 ??? 000000000000000000 0 + 0 1 libdeng_core.dylib 0x000000010a605c04 de::File::description(int) const + 52 2 libdeng_core.dylib 0x000000010a60c0fe de::FileSystem::interpret(de::File*) + 478 3 libdeng_core.dylib 0x000000010a6032f1 de::DirectoryFeed::populateFile(de::Folder const&, de::String const&, QList<de::File*>&) + 257 4 libdeng_core.dylib 0x000000010a602803 de::DirectoryFeed::populate(de::Folder const&) + 819 5 libdeng_core.dylib 0x000000010a6113e1 de::Folder::populate(QFlags<de::Folder::PopulationBehavior>)::$_0::operator()() const + 113 6 libdeng_core.dylib 0x000000010a5725b7 de::Task::run() + 23 7 org.qt-project.QtCore 0x000000010a91bd67 0x10a8f5000 + 159079 8 org.qt-project.QtCore 0x000000010a91efba 0x10a8f5000 + 171962 9 libsystem_pthread.dylib 0x00007fff8f25d99d _pthread_body + 131 10 libsystem_pthread.dylib 0x00007fff8f25d91a _pthread_start + 168 11 libsystem_pthread.dylib 0x00007fff8f25b351 thread_start + 13 Thread 10:: Thread (pooled) 0 libsystem_kernel.dylib 0x00007fff8d9c9362 read + 10 1 org.qt-project.QtCore 0x000000010aa63bee 0x10a8f5000 + 1502190 2 org.qt-project.QtCore 0x000000010aa14f81 QFileDevice::readData(char*, long long) + 177 3 org.qt-project.QtCore 0x000000010aa1b410 QIODevice::read(char*, long long) + 816 4 libdeng_core.dylib 0x000000010a618a04 de::NativeFile::get(unsigned long long, unsigned char*, unsigned long long) const + 148 5 libdeng_core.dylib 0x000000010a5d3883 de::Reader::Impl::readBytes(unsigned char*, unsigned long long) + 51 6 libdeng_core.dylib 0x000000010a5d2a0a de::Reader::operator>>(unsigned int&) + 26 7 libdeng_core.dylib 0x000000010a5fae08 de::internal::LocalFileHeader::operator<<(de::Reader&) + 24 8 libdeng_core.dylib 0x000000010a5d30d5 de::Reader::operator>>(de::IReadable&) + 21 9 libdeng_core.dylib 0x000000010a5f72f5 de::ZipArchive::ZipArchive(de::IByteArray const&) + 917 10 libdeng_core.dylib 0x000000010a5fef35 de::ArchiveFeed::Impl::Impl(de::ArchiveFeed*, de::File&) + 581 11 libdeng_core.dylib 0x000000010a5fcdfa de::ArchiveFeed::ArchiveFeed(de::File&) + 58 12 libdeng_doomsday.dylib 0x0000000108f1f775 DataFolder::DataFolder(DataBundle::Format, de::File&) + 261 13 libdeng_doomsday.dylib 0x0000000108f6a894 DataBundle::Interpreter::interpretFile(de::File*) const + 948 14 libdeng_core.dylib 0x000000010a60c080 de::FileSystem::interpret(de::File*) + 352 15 libdeng_core.dylib 0x000000010a6032f1 de::DirectoryFeed::populateFile(de::Folder const&, de::String const&, QList<de::File*>&) + 257 16 libdeng_core.dylib 0x000000010a602803 de::DirectoryFeed::populate(de::Folder const&) + 819 17 libdeng_core.dylib 0x000000010a6113e1 de::Folder::populate(QFlags<de::Folder::PopulationBehavior>)::$_0::operator()() const + 113 18 libdeng_core.dylib 0x000000010a5725b7 de::Task::run() + 23 19 org.qt-project.QtCore 0x000000010a91bd67 0x10a8f5000 + 159079 20 org.qt-project.QtCore 0x000000010a91efba 0x10a8f5000 + 171962 21 libsystem_pthread.dylib 0x00007fff8f25d99d _pthread_body + 131 22 libsystem_pthread.dylib 0x00007fff8f25d91a _pthread_start + 168 23 libsystem_pthread.dylib 0x00007fff8f25b351 thread_start + 13Note that you can also run Doomsday 2 directly from the .dmg file, without installing anything, so at least that way it is guaranteed to have valid contents.
Both the 'include' and 'cmake' folders are in the applications folder. They seem to be complete but I still have no games other than the shareware defaults showing up. Running from the backup drive works fine, though, with all the registered versions working from what appear to be the same locations on that backup drive.
Then again maybe I've missed something. I'm also wondering if I have some kind of permissions issue affecting all this.
I'm not sure how to help you, though. Perhaps you could show some screenshots of what's happening?
Thanks!
Note that the "Library" subfolder in your macOS user home folder is nowadays hidden by the OS and can only be accessed by manually entering the path. (The shortcut is Command-Shift-G in Finder.)
When it comes to knowing which games are installed, Doomsday looks in the configured IWAD folders for recognized WAD files (such as doom2.wad). These folders can be selected in the ⚙ > Data Files settings. The configured values are actually stored in "~/Library/Application Support/Doomsday Engine/runtime/persist.pack".
If you have created custom game profiles, those are stored in "~/Library/Application Support/Doomsday Engine/runtime/configs/game.dei".