Up until 1.74 the rings were in fact a model in Oolite that could be replaced. Actually it was just one ring that the engine placed in different enlargements.
But, since 1.75 the rings are generate differently and is no longer a model like the normal ships. So it will not be possible to change them by adding a different model or by adding shaders to a texture.
btw, those nice effect of the BGS is only there when using shaders. When switching of you don't see anything at all except the normal rings. That might also give a problem when generally removing the rings by the oxp as than the shader-less people won't see a jump effect at all.
Thank you for clarifying that, it was worth a try.
As for the latter issue, it could still be implemented, but left off by default. Still better than having a second OXP to modify another OXP.
"A brilliant game of blasting and trading... Truly a mega-game... The game of a lifetime." (Gold Medal Award, Zzap!64 May 1985).
Sorry I did not find the time to test but as I said this release was a hit anyway . But I got 2 more ideas for the BGS OXP.
--Q-Bomb Sound FX--
As we all know in space there is no sound. But the hell with that . Oolite ships actually use sound generation fields to create situational awareness. What about making a grand effect for the Q-Bomb. If it explodes you hear a sound and see some static on your view screen.
--Idle Sound==
Also an Idle sound would be cool. As you stop the ship there is now no sound. But I think you should still hear 'some' systems.
--Explosion sound or shockwave sounds-
Explosion sounds would also be cool. Not bangs but more like a sort of sonic booms (probably underwater like).
If you like I can put my Synths to work to generate some sounds?
btw, those nice effect of the BGS is only there when using shaders. When switching of you don't see anything at all except the normal rings. That might also give a problem when generally removing the rings by the oxp as than the shader-less people won't see a jump effect at all.
Yep - that's why I haven't touched the hyperspace_tunnel_colors (planetinfo.plist). I'm also undecided if BGS should use the vectorForward.multiply() as it moves the player to another location. The question is here if this can cause trouble, e.g. catapulting the player into another object, etc. We can implement it with a switch for a testversion (thanks to Okti) and after some weeks it can go in a release version. He - and this would give us enough time to develop the other new ideas for BGS...
pagroove wrote:
If you like I can put my Synths to work to generate some sounds?
Hey Pag, sure - switch it on .-) I'll run some tests to see how much resources BGS is currently eating and where we can do a little bit more without hitting the framerate.
How about this for a Q-bomb sound. Made with an An1x through a lot of fx. First the explosion sound and then the sound of the expanding sphere. http://www.box.net/shared/2qijjr6c18ajjth88lkp
The testversion-script to trick the breakpattern rings can be downloaded -> BGS-M1.3.6Testversion.zip (5.4 KB)
Changes:
- new property bgsHyperMove which acts as multiplier. Default 500. Set to any positive number (to get the rings partial ~300, or absolutely not >=500) or 0 (zero) to disable this feature.
Pushing the player forward is only enabled if bgsHyperFX is true.
Up until 1.74 the rings were in fact a model in Oolite that could be replaced. Actually it was just one ring that the engine placed in different enlargements.
But, since 1.75 the rings are generate differently and is no longer a model like the normal ships. So it will not be possible to change them by adding a different model or by adding shaders to a texture.
btw, those nice effect of the BGS is only there when using shaders. When switching of you don't see anything at all except the normal rings. That might also give a problem when generally removing the rings by the oxp as than the shader-less people won't see a jump effect at all.
Thank you for clarifying that, it was worth a try.
As for the latter issue, it could still be implemented, but left off by default. Still better than having a second OXP to modify another OXP.
Not to worry!
You can tell via js if oolite is using shaders, so you can tweak the hyperspace effect to displace the ship - using bgsHyperMove - only if shaders are on - in fact, I suspect Svengali might implement this very concept in the next version of BGS...
You can tell via js if oolite is using shaders, so you can tweak the hyperspace effect to displace the ship - using bgsHyperMove - only if shaders are on - in fact, I suspect Svengali might implement this very concept in the next version of BGS... ;)
Well, the borrowed laptop I'm using can run 60 odd FPS on Windows XP, but with no shaders. However, for some reason once I use Ubuntu, I can get 35 FPS, with simple shaders. So, I thought I'd be optimistic and try out the hyperspace effect and see what it's like. It had the unfortunate effect of slowing things down to 1 frame every 25 or so seconds, but I have to say it was pretty spectacular, and it would be amazing to see at full speed. It seems to show on screen how the hyperspace jump looks in my imagination! Most impressed!
Of course I will! Actually, I test possible new candidates for screen recording software specifically with that effect so that it will be as lag-free as possible
Of course I will! Actually, I test possible new candidates for screen recording software specifically with that effect so that it will be as lag-free as possible
Cool
But better wait for the next BGS version... then you can show another new feature too... .-)
. But I got 2 more ideas for the BGS OXP.
![[EliteWiki]](/images/elitewikismall.png){kind=small}
Capt. Murphy's OXPs
