|
Post by dfcastelao on May 4, 2007 8:52:32 GMT
Hello there!
As you're porting my favorite PC shooter... thanks a lot!!!!
I have some doubts about OpenTyrian, not clarified in the README file:
Will it be compatible with OpenTyrian 2000 data files? Will it be compatible with 64 bits (linux) systems?
|
|
|
Post by Mindless on May 4, 2007 12:42:14 GMT
Will it be compatible with OpenTyrian 2000 data files? We hope so. We don't have the 2000 source, so it'll take a bit more work than being compatible with 2.x data files. Will it be compatible with 64 bits (linux) systems? I can't think of any reason that it wouldn't.
|
|
|
Post by dfcastelao on May 5, 2007 8:47:03 GMT
Great!
About the 64 bits part, it doesn't seems to be compatible now (ubuntu amd64).
The first intro screen is corrupted and the game crashes after showing it. It doesn't happens on my other PC (debian i386).
|
|
|
Post by Mindless on May 5, 2007 14:33:16 GMT
Perhaps you could compile with debugging info and post a backtrace... however, the IRC channel would be best for that. If not, I'll have to kill my Windows partition and install a 64-bit distro.
|
|
|
Post by death on May 5, 2007 20:00:28 GMT
where do you get open tyrian
|
|
bb1
Member
Posts: 256
|
Post by bb1 on May 5, 2007 23:42:21 GMT
Firstly: Questions end in a ?
Second: It isn't done yet.
|
|
|
Post by yuriks on May 9, 2007 22:09:48 GMT
Third: Go on our website and checkout a copy.
Fourth: It will work on the enchanched port. Right now the code only works on 32-bit little-endian processors/OSes.
|
|
|
Post by dfcastelao on May 9, 2007 22:32:48 GMT
Mindless, here you have a backtrace. As I said, the program breaks just after the fade out effect. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47893784736256 (LWP 10301)] 0x00002b8f208a012d in getenv () from /lib/libc.so.6 (gdb) bt #0 0x00002b8f208a012d in getenv () from /lib/libc.so.6 #1 0x00002b8f208d5484 in ?? () from /lib/libc.so.6 #2 0x00002b8f2095172f in __stack_chk_fail () from /lib/libc.so.6 #3 0x00000000004107a1 in JE_loadPic (PCXnumber=11 '\v', storepal=0) at src/picload.c:95 #4 0x16c4171917c215c3 in ?? () #5 0x07c2090f1518c217 in ?? () #6 0xc308070807cd0908 in ?? () #7 0xc407c40605c80607 in ?? () ... #56 0x10c313151314100f in ?? () #57 0x1615c314c31312c2 in ?? () #58 0x0ec210121110c214 in ?? () ...
The ?? frames last forever. Looks like something broke the stack . Well, after reading the Fourth Rule I supose that I should wait for the enchanched version . I understand your choice, believe me. Please, drop me a line if you want some help with 64bits testing/debugging/coding/whatever sometime.
|
|
|
Post by yuriks on May 9, 2007 23:27:29 GMT
The classic port mostly only works on little endian 32-bit becuase the original Tyrian only worked on little endian 32-bit. =P
|
|
|
Post by Mindless on May 10, 2007 1:17:26 GMT
The classic port mostly only works on little endian 32-bit becuase the original Tyrian only worked on little endian 32-bit. =P There's no reason it shouldn't be able to work on 64-bit processors (and in the future, big-endian processors). <_<
|
|
|
Post by Mindless on May 10, 2007 1:30:46 GMT
Mindless, here you have a backtrace. As I said, the program breaks just after the fade out effect. Any chance you could hop onto the IRC channel some time? (#tyrian on irc.freenode.net) I think you may have bad data files, since I don't understand how it can crash there. (You need the files from version 2.x) However, it *could* just be that I don't understand differences in programming for 32- and 64-bit processors. Also, how is the first screen corrupted? Is it at all recognizeable? A screenshot could be most helpful. Edit: Actually, checkout the source again, rebuild, and see if it works correctly now that we're using SDL's types.
|
|
|
Post by dfcastelao on May 10, 2007 21:36:10 GMT
SDL types did the work. Now it reaches the same point than the 32 bits binary. Nice job!
|
|
|
Post by death on May 19, 2007 0:37:12 GMT
um... endian?
|
|
|
Post by yuriks on May 20, 2007 23:52:33 GMT
What?
|
|