This mod showcases several ideas I've had, and the hackish workarounds I've implemented to make them happen, including extremely large planets (which are actually to the scale given on the wiki, directly from george), stations you can actually fire straight through, and my personal favorite hack... Gravity.
Eventually it will have a story...
http://xelerus.de/index.php?s=mod&id=841
Note: If the mod doesn't work for you, open the xml file and remove the startingShip= line from the <AdventureDesc> section. Then disable the Umbra Playership.
[Development] Singularity Proof of Concept
-
Aury
- Fleet Admiral
- Posts: 5421
- Joined: Tue Feb 05, 2008 1:10 am
- Location: Somewhere in the Frontier on a Hycrotan station, working on new ships.
I believe you did it for the very first modding competition (the one where there were lots of delays because nobody followed my submission instructions resulting in lost and mis-sorted files for a month -_-)
(shpOrder gPlayership 'barrelRoll)
(plySetGenome gPlayer (list 'Varalyn 'nonBinary))
Homelab Servers: Xeon Silver 4110, 16GB | Via Quadcore C4650, 16GB | Athlon 200GE, 8GB | i7 7800X, 32GB | Threadripper 1950X, 32GB | Atom x5 8350, 4GB | Opteron 8174, 16GB | Xeon E5 2620 v3, 8GB | 2x Xeon Silver 4116, 96GB, 2x 1080ti | i7 8700, 32GB, 6500XT
Workstations & Render machines: Threadripper 3990X, 128GB, 6900XT | Threadripper 2990WX, 32GB, 1080ti | Xeon Platinum 8173M, 48GB, 1070ti | R9 3900X, 16GB, Vega64 | 2x E5 2430L v2, 24GB, 970 | R7 3700X, 32GB, A6000
Gaming Systems: R9 5950X, 32GB, 6700XT
Office Systems: Xeon 5318Y, 256GB, A4000
Misc Systems: R5 3500U, 20GB | R5 2400G, 16GB | i5 7640X, 16GB, Vega56 | E5 2620, 8GB, R5 260 | P4 1.8ghz, 0.75GB, Voodoo 5 5500 | Athlon 64 x2 4400+, 1.5GB, FX 5800 Ultra | Pentium D 3.2ghz, 4GB, 7600gt | Celeron g460, 8GB, 730gt | 2x Athlon FX 74, 8GB, 8800gts 512 | FX 9590, 16GB, R9 295x2 | E350, 8GB | Phenom X4 2.6ghz, 16GB, 8800gt | random core2 duo/atom/i5/i7 laptops
(plySetGenome gPlayer (list 'Varalyn 'nonBinary))
Homelab Servers: Xeon Silver 4110, 16GB | Via Quadcore C4650, 16GB | Athlon 200GE, 8GB | i7 7800X, 32GB | Threadripper 1950X, 32GB | Atom x5 8350, 4GB | Opteron 8174, 16GB | Xeon E5 2620 v3, 8GB | 2x Xeon Silver 4116, 96GB, 2x 1080ti | i7 8700, 32GB, 6500XT
Workstations & Render machines: Threadripper 3990X, 128GB, 6900XT | Threadripper 2990WX, 32GB, 1080ti | Xeon Platinum 8173M, 48GB, 1070ti | R9 3900X, 16GB, Vega64 | 2x E5 2430L v2, 24GB, 970 | R7 3700X, 32GB, A6000
Gaming Systems: R9 5950X, 32GB, 6700XT
Office Systems: Xeon 5318Y, 256GB, A4000
Misc Systems: R5 3500U, 20GB | R5 2400G, 16GB | i5 7640X, 16GB, Vega56 | E5 2620, 8GB, R5 260 | P4 1.8ghz, 0.75GB, Voodoo 5 5500 | Athlon 64 x2 4400+, 1.5GB, FX 5800 Ultra | Pentium D 3.2ghz, 4GB, 7600gt | Celeron g460, 8GB, 730gt | 2x Athlon FX 74, 8GB, 8800gts 512 | FX 9590, 16GB, R9 295x2 | E350, 8GB | Phenom X4 2.6ghz, 16GB, 8800gt | random core2 duo/atom/i5/i7 laptops
Uploaded a new version, using vector maths and a per-ship overflow catcher.
I never expected this to be unique, but it's something I've been wanting to make for-freaking-ever. I hope this is a slick enough implementation to get some attention.
I never expected this to be unique, but it's something I've been wanting to make for-freaking-ever. I hope this is a slick enough implementation to get some attention.
-
Ttech
- Fleet Admiral
- Posts: 2767
- Joined: Tue Nov 06, 2007 12:03 am
- Location: Traveling in the TARDIS
- Contact:
Slick enough? If its something new, its pretty slick. Don't worry about it.Jeoshua wrote:Uploaded a new version, using vector maths and a per-ship overflow catcher.
I never expected this to be unique, but it's something I've been wanting to make for-freaking-ever. I hope this is a slick enough implementation to get some attention.
And I'm working on the next version, cleaning up code and extending the systems, yet again...
But this time it's different. I keep getting this weird bug where everything slides to the West at 10% lightspeed... which is really weird since the vector is always the same no matter where the gravity is (which is still applied, by the way).
Anyone else know anything about vector math, either in or out of TScript, that might be able to help me with tracking down this rediculous bug? Or understand it in some way so that I might do more effects with this gravity?
As it is, in 0.2 I am using gravObjects with a deffinite size. In other words, they're not point masses. Making a heavy object with no extent would make.... well... a singularity.
Understand where I got the name, yet?
But this time it's different. I keep getting this weird bug where everything slides to the West at 10% lightspeed... which is really weird since the vector is always the same no matter where the gravity is (which is still applied, by the way).
Anyone else know anything about vector math, either in or out of TScript, that might be able to help me with tracking down this rediculous bug? Or understand it in some way so that I might do more effects with this gravity?
As it is, in 0.2 I am using gravObjects with a deffinite size. In other words, they're not point masses. Making a heavy object with no extent would make.... well... a singularity.
Understand where I got the name, yet?
-
Ttech
- Fleet Admiral
- Posts: 2767
- Joined: Tue Nov 06, 2007 12:03 am
- Location: Traveling in the TARDIS
- Contact:
Jeoshua wrote:And I'm working on the next version, cleaning up code and extending the systems, yet again...
But this time it's different. I keep getting this weird bug where everything slides to the West at 10% lightspeed... which is really weird since the vector is always the same no matter where the gravity is (which is still applied, by the way).
Anyone else know anything about vector math, either in or out of TScript, that might be able to help me with tracking down this rediculous bug? Or understand it in some way so that I might do more effects with this gravity?
As it is, in 0.2 I am using gravObjects with a deffinite size. In other words, they're not point masses. Making a heavy object with no extent would make.... well... a singularity.
Understand where I got the name, yet?
No, I don't understand at all.
Nice name, it honestly seems like a logic error, I'd recommend taking out anything moving in the code and trying to figure it out.I need help to understand why this snippet of code isn't working. The whole thing returns good results the whole way through, then next time it doesn't work.
Interestingly, that last line in there, which is supposed to keep the remainder, is only works when theVelocity returns greater than 0. But that doesn't make any sense because theres not a conditional statement there.
http://transcendence.pastebin.com/1PfueuQV
Interestingly, that last line in there, which is supposed to keep the remainder, is only works when theVelocity returns greater than 0. But that doesn't make any sense because theres not a conditional statement there.
http://transcendence.pastebin.com/1PfueuQV
-
alterecco
- Fleet Officer
- Posts: 1658
- Joined: Wed Jan 14, 2009 3:08 am
- Location: Previously enslaved by the Iocrym
I am not sure what it might be. Since you are calling other of your own functions and using what appears to be global vars it is hard to know how the code runs.
Only thing that springs forward is that gravDistant is not declared in the block vars, so it will become global. The same goes for gravOutput, but that might be intentional.
Also, when you say it only works the first time through, do you mean the first time the function is called or the first iteration of the enum?
Only thing that springs forward is that gravDistant is not declared in the block vars, so it will become global. The same goes for gravOutput, but that might be intentional.
Also, when you say it only works the first time through, do you mean the first time the function is called or the first iteration of the enum?
Actually, as usual, the act of asking forced me to go back and look.
It was the storage that was my problem. I wasn't bounds checking it, and it was causing an error. sysVectorSpeed was overflowing too, and when it does it returned 0x800000 (which is negative long int). And also returned 180 degrees of that. Since a negative number can still be divided, and divided by... it started moving me quickly to the west. I added some checks to see if the calculation returned anything. Now, not only does it work, but it works 100 times faster than it did before!
I just uploaded a new version too, with some added goodies.
It was the storage that was my problem. I wasn't bounds checking it, and it was causing an error. sysVectorSpeed was overflowing too, and when it does it returned 0x800000 (which is negative long int). And also returned 180 degrees of that. Since a negative number can still be divided, and divided by... it started moving me quickly to the west. I added some checks to see if the calculation returned anything. Now, not only does it work, but it works 100 times faster than it did before!
I just uploaded a new version too, with some added goodies.