Mac User pls try priv9b

what about vssetup without gtk though

there should be two executables
./vssetup

and
./vssetup_gtk

the first shouldn't require ANYTHING (not X11 nor anything)

that one shouldn't need fink's gtk

for the fink one I'll have to figure out how to statically link it
 
In Panther now...

I've rebooted in Panther to try that out.

- Music and sound effects work just fine.
- Config program works just fine. (without Fink on this platform either)
- Joystick calibration is way off (any chance of adding a joystick calibration feature to VS and PR for 10.3?)

Since everything seems fine and Panther, I'm headed back to Jaguar.

--Chris
 
ya what about the ./vssetup in jag then

gosh wish I could figure out how to get a dual boot with jag going on...the big problem is my 20 gig hard drive...maybe I need an ipod or something
 
Oh ack I see what you mean
you couldn't figure out how to launch it from the terminal
open is going to get you the same raunchy behavior.
you have to actually try executing the binary
paste your terminal logs and I'll help you get it executing there--this is vital to helping me get things working (for users without X11)
 
Back in Jaguar

Ok,

I worked my way to the right directory in terminal and executed vssetup. It gave me a segmentation fault. Here's the crash log:


Date/Time: 2004-12-15 20:06:25 -0500
OS Version: 10.2.8 (Build 6R73)
Host: Christopher-Wszaleks-Computer.local.

Command: vssetup
PID: 395

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x726f7570

Thread 0 Crashed:
#0 0x90000e60 in strlen
#1 0x0000b978 in dlg_count_columns (inputstr.c:351)
#2 0x000067e0 in dialog_menu (menubox.c:321)
#3 0x00002ab8 in ShowMainMenu(char**, char*, char*) (display_dialog.cpp:37)
#4 0x00003114 in ShowMain() (display_dialog.cpp:132)
#5 0x00002444 in Start(int*, char***) (central.cpp:29)
#6 0x000023f4 in main (setup.cpp:63)
#7 0x00002110 in _start
#8 0x00001f40 in start

PPC Thread State:
srr0: 0x90000e60 srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x0000b978 ctr: 0x90000e40 mq: 0x00000000
r0: 0x0000b978 r1: 0xbffff290 r2: 0x00000351 r3: 0x726f756c
r4: 0x00000000 r5: 0xfefefeff r6: 0x80808080 r7: 0x00000003
r8: 0x69636b00 r9: 0x726f7570 r10: 0x000f04a0 r11: 0x0004ed60
r12: 0x90000e40 r13: 0x00000001 r14: 0x00000000 r15: 0x00000016
r16: 0x000ec4c0 r17: 0x000eef94 r18: 0x00000000 r19: 0x0000000c
r20: 0x000f02f4 r21: 0x0000001d r22: 0x00000090 r23: 0x00000010
r24: 0x00000090 r25: 0x00054540 r26: 0x0000000c r27: 0x000ec520
r28: 0x000ec550 r29: 0x000ec520 r30: 0x726f7570 r31: 0x0000649c

Then I tried vssetup_gtk from the terminal and got this:

dyld: ./vssetup_gtk can't open library: /sw/lib/libgtk-1.2.0.dylib (No such file or directory, errno = 2)
Trace/BPT trap

With this crash log:

Date/Time: 2004-12-15 20:12:45 -0500
OS Version: 10.2.8 (Build 6R73)
Host: Christopher-Wszaleks-Computer.local.

Command: vssetup_gtk
PID: 400

Exception: EXC_BREAKPOINT (0x0006)
Code[0]: 0x00000001Code[1]: 0x8fe01220

Thread 0 Crashed:
#0 0x8fe01220 in halt
#1 0x8fe0323c in load_library_image
#2 0x8fe060d4 in load_images_libraries
#3 0x8fe02688 in load_executable_image
#4 0x8fe013b0 in _dyld_init

PPC Thread State:
srr0: 0x8fe01220 srr1: 0x0002f030 vrsave: 0x00000000
xer: 0x20000000 lr: 0x8fe0a004 ctr: 0x8fe28ebc mq: 0x00000000
r0: 0x00000004 r1: 0xbffffab0 r2: 0x24008280 r3: 0x0000006b
r4: 0x00000000 r5: 0x0000006b r6: 0x0000290a r7: 0x726e6f20
r8: 0x66696c65 r9: 0x00000000 r10: 0xbffff82b r11: 0x00000026
r12: 0x8fe71a93 r13: 0x00000000 r14: 0x000028d8 r15: 0x00000000
r16: 0xbffffd54 r17: 0x00000001 r18: 0x00001548 r19: 0x00001988
r20: 0x00000001 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x8fe4b3cc r25: 0x00000002 r26: 0x00000002 r27: 0x00000000
r28: 0x00001790 r29: 0x00000000 r30: 0x8fe484d8 r31: 0x8fe09e6c

I hope that helps.

--Chris
 
oh yes it really helps...but I'm not sure how to fix it :-(

apparently OS X 10.2 uses a poor terminal emulation... I'll have to hack into the code of the dialog library to get it working it looks like...
and who knows what'll break after that... since I don'y have an old 10.2 terminal.app I'm going to be hard pressed to fix this...

gosh I really wish I had OS X 10.2 on some partition

I'll send you a new vssetup program after I try to fix it...clearly vssetup_gtk will only work for fink users...that's your best bet until I give you a new version of vssetup (without gtk) thank you
 
Ack this doesn't seem to be enough info to fix it.
If you install the devel tools and could run it in gdb....then type backtrace full
that would be most helpful

gdb ./vssetup
run
backtrace full

I'd love to do a realtime chat--my AIM handle is 4863215 and that's the same as my ICQ handle... my MSN handle is hellcatv *atsign hotmail.com

hope we can figure this out soon
 
working good for the most part

I've been playing priv9b on my ibook g4 with OS 10.3.7. It seems to work great. There are only a few problems, but I imagine they're the same as in all the other ports.

I noticed in some systems when I autopilot to a planet it shows me as being 400000 or some huge number away. It's not a big problem because it lets me dock with the planet, but I have to spend a minute or so "moving towards" a planet but not getting visibly closer. It's kind of hard to explain.

Also when I accept a mission and save the game and quit, when I go back and load the game I saved it automatically fails the mission. This might be on purpose to discourage saving and loading every five minutes, but it is annoying.

All other problems that I've noticed are my own (ie I suck pretty terribly :) ). Oh, and I can not for the life of my figure out that stupid navigation map.

Anyway, great job. I'll have to go try this out on my linux box.
 
Unregistered said:
I noticed in some systems when I autopilot to a planet it shows me as being 400000 or some huge number away. It's not a big problem because it lets me dock with the planet, but I have to spend a minute or so "moving towards" a planet but not getting visibly closer. It's kind of hard to explain.
Click to expand...
I'm betting this is in a system that isn't in Gemini. The systems in Gemini were hand made (and the scale is way off, it is like the scale in the original: really tiny) Systems outside of Gemini are randomly generated, and the scale is a lot bigger. When you auto to a planet, you come out 15,000 away, or a certain percentage of the planet's radius away, whichever is greater. From there you have to make your way to 1.6 times the planet's radius from the center.

With a really large planet, it doesn't look like you are getting closer (like how the sun doesn't look bigger when you climb a hill), but you have to get within 1.6*radius to dock, which luckily isn't far away. Dunno if that made sense, but you won't be able to leave Gemini in 1.0 so it won't really be an issue ;)
 
Turret AI

I have noticed a problem with the turret AI. I can't get my turrets to attack a ship on their own unless the particular faction the ship belongs to hates me a lot (somewhere around -50). When I tell the turrets to target a ship that fits the above description (the faction doesn't dislike me very much) with alt - t a plus sign appears on the ship, like usual, but the turrets don't fire.
I have noticed this on bounty hunting missions and against Kilrathi (or whatever the cats are called.) The cats only hate me -12 (because the confederation caught me shipping contraband I assume) but they still attack me at every opportunity. Do you know what could be causing this?
 
You must log in or register to reply here.
Back
Top