Zandronum 1.0-alpha-120602-1356

This looks good. Is this based on the same old ZDoom revision Skulltag was?

(06-05-2012 05:45 PM)Sgt Dopey Wrote:  This looks good. Is this based on the same old ZDoom revision Skulltag was?

Yes. I'm told that as soon as this alpha is stabilized (that means we need some testers folks!), we'll start working on slowly catching up to the ZDoom revisions.

A FreeBSD 64 build would be appreciated.

(06-06-2012 03:53 AM)HeX9109 Wrote:  A FreeBSD 64 build would be appreciated.

I'll see if I can reactivate / update my FreeBSD x64 virtual machine for this.

I get an error message when trying to run Zandronum. I've downloaded any new software updates and re-downloaded Zandronum and I still ge this error message:

Spoiler: Error Message (Open)

Spoiler: Report (from above screenshot) (Open)

Process: zandronum [1706]
Path: /Users/user/Desktop/Marathon Trilogy/Skulltag (DooM)/Zandronum 1.0 Alpha ƒ/Zandronum.app/Contents/MacOS/zandronum
Identifier: net.skulltag.Skulltag
Version: ()
Code Type: X86 (Native)
Parent Process: launchd [149]

Date/Time: 2012-06-05 18:34:43.909 -0400
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Interval Since Last Report: 16401881 sec
Crashes Since Last Report: 240
Per-App Crashes Since Last Report: 4
Anonymous UUID: 68DA6E2B-5AA6-4E3A-BE18-6E1185F20669

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0

Dyld Error Message:
Library not loaded: /Users/blzut3/Code/svnteam/Zandronum/build/snes_spc/libsnes_spc.dylib
Referenced from: /Users/user/Desktop/Marathon Trilogy/Skulltag (DooM)/Zandronum 1.0 Alpha ƒ/Zandronum.app/Contents/MacOS/zandronum
Reason: image not found

Binary Images:
0x8fe00000 - 0x8fe4163b dyld 132.1 () <4CDE4F04-0DD6-224E-ACE5-3C06E169A801> /usr/lib/dyld

I'm running Mac OS X (Version 10.6.8), same thing I was running Skulltag with.


And on an (unrelated?) note:

Spoiler: lolappicon (Open)

I don't get it Shoggy.

(06-06-2012 10:04 AM)Mangetsu Wrote:  I don't get it Shoggy.

Im exicited, finally a update for ST, a new change and look!

Fixed a major problem in the compat pack. I ended up accidentally converting the flats to patch format, so I went back again to convert the flats to their proper format.

(06-06-2012 03:53 AM)HeX9109 Wrote:  A FreeBSD 64 build would be appreciated.

I built and uploaded FreeBSD x64 binaries (with FreeBSD 9.0), and added the link to the first post.

[/home/skulltag/st]% tar -xzf ZandroDev1.0-120602-1356freebsd-x64.tar.bz2
tar: Error opening archive: bzip decompression failed

7zip gives me the same error on Windows.

(06-07-2012 09:35 AM)HeX9109 Wrote:  [/home/skulltag/st]% tar -xzf ZandroDev1.0-120602-1356freebsd-x64.tar.bz2
tar: Error opening archive: bzip decompression failed

Please try again. For some reason the default transfer mode of FreeBSD's command line FTP client is ACSII and transferring the file in this mode broke it.

*Cough*

(06-06-2012 08:37 AM)President People Wrote:  I get an error message when trying to run Zandronum. I've downloaded any new software updates and re-downloaded Zandronum and I still ge this error message:

Spoiler: Error Message (Open)

Spoiler: Report (from above screenshot) (Open)

Process: zandronum [1706]
Path: /Users/user/Desktop/Marathon Trilogy/Skulltag (DooM)/Zandronum 1.0 Alpha ƒ/Zandronum.app/Contents/MacOS/zandronum
Identifier: net.skulltag.Skulltag
Version: ()
Code Type: X86 (Native)
Parent Process: launchd [149]

Date/Time: 2012-06-05 18:34:43.909 -0400
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Interval Since Last Report: 16401881 sec
Crashes Since Last Report: 240
Per-App Crashes Since Last Report: 4
Anonymous UUID: 68DA6E2B-5AA6-4E3A-BE18-6E1185F20669

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0

Dyld Error Message:
Library not loaded: /Users/blzut3/Code/svnteam/Zandronum/build/snes_spc/libsnes_spc.dylib
Referenced from: /Users/user/Desktop/Marathon Trilogy/Skulltag (DooM)/Zandronum 1.0 Alpha ƒ/Zandronum.app/Contents/MacOS/zandronum
Reason: image not found

Binary Images:
0x8fe00000 - 0x8fe4163b dyld 132.1 () <4CDE4F04-0DD6-224E-ACE5-3C06E169A801> /usr/lib/dyld

I'm running Mac OS X (Version 10.6.8), same thing I was running Skulltag with.


And on an (unrelated?) note:

Spoiler: lolappicon (Open)

*Cough*

I don't have a Mac so unfortunately I can't help you with this. Blzut3 builds the Mac binaries, so you'll need to ask him.

Ah. I'll have to ask him in a while. Sorry for being an annoyance.

(06-06-2012 08:37 AM)President People Wrote:  I get an error message when trying to run Zandronum. I've downloaded any new software updates and re-downloaded Zandronum and I still ge this error message:

Fixed a typo in my build script and redid the disk image. Try downloading it again. (The new image should be less than 5MB.)

For some reason, I cannot get Timidity++ to load with Zandronum.
I've typed this: timidity_exe c:\timidity
and every time this happens, a weird block-looking character shows up in place of "\t", and changing the folder name to "miditimidity" gets rid of the block, but every remedy I've tried leads to the same message:
"could not access c:(block)imidity" or "could not access c:\miditimidity" Any advice?

(06-09-2012 05:32 AM)Hellstorm Archon Wrote:  For some reason, I cannot get Timidity++ to load with Zandronum.
I've typed this: timidity_exe c:\timidity
and every time this happens, a weird block-looking character shows up in place of "\t", and changing the folder name to "miditimidity" gets rid of the block, but every remedy I've tried leads to the same message:
"could not access c:(block)imidity" or "could not access c:\miditimidity" Any advice?

use two backslashes
IE: timidtiy_exe C:\\path\\to\\timidity.exe

Also, it has to point to the executable file, not the directory.

May I suggest that you put installer like Skulltag, that installs both Zandronum and Doomseeker (it's last version). It bothers me when I overwrite current Doomseeker with latest beta and I am unable to contact anyone on IRC, it says doomseeker isn't responding after it crashes and always so (meaning IRC always bugs).

Installer is very simple and comfortable thing.

Like in Skulltag, we plan to prepare packages with installer for the public stable releases but not for the beta builds.