Page 2 of 2
Posted: Tue Jul 17, 2007 5:19 am
by Wolfwood
PsychotropicDog wrote:wolfwoods_variants.oxp --ok, but cobra Rapier, courier, and probably all these variants have a layer of the HUD in the center of screen - it slipped.
Darn, I thought I had fixed that one already... Well, I guess I'll have to download the latest build and make sure...
Posted: Tue Jul 17, 2007 3:38 pm
by Commander McLane
PsychotropicDog wrote:(fix for cargo wrecks worked - though I see a lot of treasuroids now)
Well, you should. That command adds treasuroids.
Anyway it was meant for testing purposes, you can safely take it out.
Posted: Tue Jul 17, 2007 5:00 pm
by PsychotropicDog
Outrider has a HUD problem as well.
So far marett has not caused any problems, and I have shot a few of the ships.
Testing Falcon.oxp (modified so I can buy one.. eventually)
edit
should be ok besides the firepower they throw at me, though I have started to get Virtual Memory Exhausted - game left unattended - exits.
edit2
phoenix.oxp
played hours until I fragged one, should be ok
AsteroidStorm did the mission, no ugliness in stderr
Posted: Wed Jul 18, 2007 3:34 pm
by JensAyton
I’ve improved PNG loader error messages to specify which file they’re talking about. So far I’ve seen “Not a PNG file” errors for flamekrait_rear.png and flamekrait_bottom.png in custpaint1.oxp. Closer inspection revealed these to be mislabelled BMP files, which Oolite no longer supports.
Posted: Wed Jul 18, 2007 4:35 pm
by PsychotropicDog
Glad you found a problem with
NavyStarships.oxp
https://bb.oolite.space/viewtopic.php?t=3722
Note, I have not got an Orb.oxp.
going to leave Kestrel and Merlin out for now.
transports.oxp I have seen a few with no stderr messages, maybe I should shoot some - seems ok, but I have not seen a Moray Transport yet, for some reason this vaguely reminds me of something I saw in stderr but did not save
'probably ok'
testing behemoth
edit
got this again, but easily a half hour before I actually saw a behemoth.
Code: Select all
2007-07-18 13:08:01.000 oolite.exe[3176] [exception]: ***** Exception during during update:entity in [Universe update:] : NSInvalidArgumentException : SkyEntity(instance) does not recognize primaryTarget *****
2007-07-18 13:08:01.000 oolite.exe[3176] *** NSTimer ignoring exception 'NSInvalidArgumentException' (reason 'SkyEntity(instance) does not recognize primaryTarget') raised during posting of timer with target 0x1258d70 and selector 'performGameTick:'
just thought I'd mention it.
I am determined to land in a behemoth - I sort of left a cobra stain on my first try.
Posted: Fri Jul 20, 2007 3:26 am
by PsychotropicDog
I have had no problems with the following...
Executive Spaceways v2.1.oxp
Outrider.oxp
Taranis.oxp (needs Outrider)
cobraclipperPC.oxp
Ore_processor.oxp
leaves a bunch of messages that are probably normal
(and I finally discovered scooping splinters lol)
Posted: Wed Jul 25, 2007 6:00 pm
by lolwhites
Is it safe to play this version while doing Assassins?
Posted: Wed Jul 25, 2007 10:20 pm
by LittleBear
Not the current version. The 1.3 that I'm playtesting now seems OK with 1.69.1 (I can PM you a new script if you like). However, the setspecificplanetinfo: is still broken on PC 1.69.1 though!.
In the 1.3 script I've cunningly set the setspecificplanetinfo: command last in all dos though. So the OXP will work. It just means on the PC the descriptions on planets won't change as stuff happens. This isn't a biggy though. It just mean on the PC when the Thargoids invade system X, the description of system X won't change to say "Commander are advised to avoid this system as it is under Thargoid attack". The OXP will still run with all features though. The Bugs will still be there and you can play all the missions, you'll just miss out on a bit of polish to the system description on the F7 screen. The 1.3 version does stop the looping bug!
Posted: Thu Jul 26, 2007 9:35 am
by lolwhites
Thanks for the offer. I think I'll stick with the current version on 1.65 for the time being.