13,525
edits
Tristam Core/Logs: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
{{#if:{{{4|}}}|<br />|<div style="border:1px dotted #666666; padding:0.5em; font-family:Verdana,sans-serif; margin: 1em 1em 1em 3em;">'''MST Development Log #7''' <br>With Kells rescued and everybody back on board safe and soundly, Loupaz and I can finally get back to work! And today I walked in to see that she and Garry- <br>'''''[Sound of muffled speaking, and something hitting the desk]''''' <br>Hey! I'll add whatever I like to the log, thank you very much! Go get a coffee or something! <br>'''''[More muffled speaking]''''' <br>Anyway, getting back on topic, results of the previous experiment were a semi-success, which is good news for me. The Jalana travelled beautifully from the primary point from Mars to the secondary point orbiting Venus. We even managed to relocate the primary to orbit Jupiter with the same results, if not a bit of strain on power. This is good - as long as the technology has a connection, it works without a hitch. <br>And then we felt lucky and decided to send the primary to Neptune. It went about as well as you'd expect. Meaning it didn't. In fact, as soon as the Jalana hit the transporter stream, the entire thing fizzled itself and we ended up back at square one. We literally lost Jalana - it's gone, and we have no idea where. It didn't get destroyed, it's pattern didn't get decintigrated. The computer claims it got sent successfully, but the Secondary around Venus didn't receive anything. So either we somehow managed to get something lost in subspace - which is highly unlikely - or the Jalana is currently floating somewhere, possibly in bits and pieces, around the holographic sol system of MSTexperholo version 8.2.1. Instead of looking for her right now, we saved the holoparametres as their own file and then reset the entire thing. We can look for it when we're rendering another transporter. Regardless, this incident will go into the "if ship doesn't reappear, look for the following" section of the user's manual. <br>I'm not entirely sure what happened. Either it was too far that the connection the transporter's computer claimed to have was so weak it just didn't hold the Jalana and caved in upon itself, or it was a power fluctuation that we didn't detect. It wouldn't be the first time, but since this has nothing to do with slipstream, I'd assumed the technology was marginally safer. This means that Loupaz and I are no longer enough to really watch the experiments closely. I'll have Garry quietly added to the resources listing so that he can monitor such readings while Loupaz and I handle everything else. I'm sure Rahman won't notice.{{#if:{{{2|}}}|<div style='margin-top:.5em'>{{{2}}}</div>}}{{#if:{{{3|}}}|<div style='margin-top:.5em'>{{{3}}}</div>}} ''</div>}} | {{#if:{{{4|}}}|<br />|<div style="border:1px dotted #666666; padding:0.5em; font-family:Verdana,sans-serif; margin: 1em 1em 1em 3em;">'''MST Development Log #7''' <br>With Kells rescued and everybody back on board safe and soundly, Loupaz and I can finally get back to work! And today I walked in to see that she and Garry- <br>'''''[Sound of muffled speaking, and something hitting the desk]''''' <br>Hey! I'll add whatever I like to the log, thank you very much! Go get a coffee or something! <br>'''''[More muffled speaking]''''' <br>Anyway, getting back on topic, results of the previous experiment were a semi-success, which is good news for me. The Jalana travelled beautifully from the primary point from Mars to the secondary point orbiting Venus. We even managed to relocate the primary to orbit Jupiter with the same results, if not a bit of strain on power. This is good - as long as the technology has a connection, it works without a hitch. <br>And then we felt lucky and decided to send the primary to Neptune. It went about as well as you'd expect. Meaning it didn't. In fact, as soon as the Jalana hit the transporter stream, the entire thing fizzled itself and we ended up back at square one. We literally lost Jalana - it's gone, and we have no idea where. It didn't get destroyed, it's pattern didn't get decintigrated. The computer claims it got sent successfully, but the Secondary around Venus didn't receive anything. So either we somehow managed to get something lost in subspace - which is highly unlikely - or the Jalana is currently floating somewhere, possibly in bits and pieces, around the holographic sol system of MSTexperholo version 8.2.1. Instead of looking for her right now, we saved the holoparametres as their own file and then reset the entire thing. We can look for it when we're rendering another transporter. Regardless, this incident will go into the "if ship doesn't reappear, look for the following" section of the user's manual. <br>I'm not entirely sure what happened. Either it was too far that the connection the transporter's computer claimed to have was so weak it just didn't hold the Jalana and caved in upon itself, or it was a power fluctuation that we didn't detect. It wouldn't be the first time, but since this has nothing to do with slipstream, I'd assumed the technology was marginally safer. This means that Loupaz and I are no longer enough to really watch the experiments closely. I'll have Garry quietly added to the resources listing so that he can monitor such readings while Loupaz and I handle everything else. I'm sure Rahman won't notice.{{#if:{{{2|}}}|<div style='margin-top:.5em'>{{{2}}}</div>}}{{#if:{{{3|}}}|<div style='margin-top:.5em'>{{{3}}}</div>}} ''</div>}} | ||
{{#if:{{{4|}}}|<br />|<div style="border:1px dotted #666666; padding:0.5em; font-family:Verdana,sans-serif; margin: 1em 1em 1em 3em;">'''MST Development Log #8''' <br>Well, I got pulled up by the SCE Project Manager for not putting in a proper requisition of resources form for Garry's help since I'd be pulling him off the roster every time I needed him without proper 'authority or explanation'. I just wanted to reiterate that the person talking is currently Chief Engineer of the USS Invicta, where these logs are being authored, and if there's someone who should be able to dictate who's working when and where in Engineering, it should probably be me. <br>Turns out that that logic doesn't fly and it's the First Officer's job to look over the rosters. So basically Rahman knew I was using Garry as soon as I'd pulled him off the active duty roster for last week. Things have been cleared up and it got the green light anyway, so no harm done, really. <br>We are currently rendering another experimental Sol system plus the two transporters exactly where they were last time, but I'm going to put a transporter beacon between them. If it's too far apart from each other, the beacon will connect the range and push the matter towards the secondary. So now there's two connections on this path. I better not get into the habit of doing this - there's only so many beacons you can put into a solar system without the owners getting annoyed. <br>Also, apparently there's bets being taken on where the Jalana's gone. I think it's not rematerialized correctly and is orbiting Jupiter in scattered dust particles, but we still haven't been able to load the program up and go looking for it.{{#if:{{{2|}}}|<div style='margin-top:.5em'>{{{2}}}</div>}}{{#if:{{{3|}}}|<div style='margin-top:.5em'>{{{3}}}</div>}} ''</div>}} | |||
[[Category:Sky Blake]] | [[Category:Sky Blake]] | ||