ringDemo_segment.dat
but the file is called ringdemo_segment.dat
Note that the OXZ format is case-sensitive on all platforms to try to avoid this sort of problem in future.
Moderators: winston, another_commander
ringDemo_segment.dat
but the file is called ringdemo_segment.dat
They wouldn't dock, but were still able to launch ok in the earlier versions, though I suppose they hurried to gain some altitude! If you'd rather lower the altitude a bit to reduce the entity count, it's enough to keep it above 10% of planetary radius.. the low-alt alert kicks in at 9%.Thargoid wrote:[*]Moved the ring up to mid-way between the planet surface and the main station orbit height, to stop NPC issues with low altitude warnings (allow them to launch and dock).[/color]
Heck, thank you for creating a demo for something almost everyone had assumed wasn't possible!Thargoid wrote:BTW a thanks to everyone who has chipped into this demo - I just love how these fun little ideas grow into such community projects
Woohoo! The bugs are dropping like flies!cim wrote:As regards the mis-positioning: It's the collision detection approximation. I've turned that off in commit d5f99b6 for tonight's nightly: it didn't appear to have any noticeable effect on frame rate to do it properly even with a ring in system, but it means that they are all perfectly aligned now.
You'll love this screenshot, then.. a couple of minutes of continuous drifting and explosions have now reached the point where some segments are burning up in the atmosphere! Engineering-heads are gonna roll!JD wrote:That's actually a brilliant picture that Norby captured. It nicely illustrates the way events take place in system, and situations follow their own course, regardless of what the player gets up to.
It also feels like there's a real story behind it, something that might be reported on the Snoopers channel - a component failure has placed a large-scale engineering project in jeopardy, and its contractor has admitted that it is now struggling to complete the work by GalCop's end-of-year deadline etc.
Give each of them a ship script that:Thargoid wrote:Kept it running under TAF x16 and even with a 200m gap the ring does very slowly disintegrate still from collision radii. Not sure what the best way to deal with that may be, as using a timer per segment to reposition each would generate ~350 or so timers which isn't I think too good an idea, and one timer doing the lot would be complex. Thoughts there would be appreciated.
I've only ever seen that in nova systems. I assume it's the long frame time combined with a quick corona shimmer meaning that it tries to skip more than one corona cycle in a frame and overshoots. That should probably be fixed since it could theoretically occur without TAF.Thargoid wrote:One other thing I did notice was a weird effect with the sun when under TAF for an extended period:
Absolutely. I love it when software starts to take on the appearance of a life of its own (well, within reason of course).Diziet Sma wrote:You'll love this screenshot, then..
I dunno.. I rather liked your original idea, of it being used as a gigantic enclosed racing-circuit..pagroove wrote:New idea: Maybe these stations could provide a gateway to galaxies 9 to 16? So that the ring is actually a big artificial wormhole?
cim wrote:Bug: shipdata specifiesringDemo_segment.dat
but the file is calledringdemo_segment.dat
Note that the OXZ format is case-sensitive on all platforms to try to avoid this sort of problem in future.
This bug has re-appeared in the latest version.. I've renamed the .dat file accordingly.Thargoid wrote:Thanks - fixed and re-uploaded.
Perhaps this image from Starship Troopers might kick start some ideas?Thargoid wrote:
I was wondering if anyone would like a go at remodelling the whole ring (new segment, joint and station models) as a possible different application to yours.