Eridonia Archives
Search Results
890 items found for ""
- (RP) The Second Battle of Eridonia. (4521 A.D.) (Intro Part 1)
After the liberation of the Aquarian Home System in 4242 A.D from the scourge of the Pirate Cartels of the Angel Reach, no one could have imagined that a mere three hundred cycles later, the fate of the Home System would once again hinge on the actions of a brave few, or perhaps; many. But indeed, Humanity is wrought in the fires of war, forged in the flames of conflict; after all, it is all we know. The attack happened much sooner than we expected. Naval Intelligence had approximately 3 Eridonian Days notice to prepare for the arrival of the first alien fleet elements. This, in and of itself, was a feat given the inconclusive nature of essentially all intelligence coming in and out of the Taran Nebula. Scouts in the Angel Reach detected Subspace Echoes consistent with a two-point standing gate jump between the Core Systems of Aquarius and the Taran Nebula. Of course, it wasn't a large jump to conclude that the target system was Eridonia. -Fleet Admiral J. Rykhani, 1st Rapid Response Force, Eridonia Core Sector Fleet, Aquarian Imperial Navy We had enough forces to hold the aliens at bay for a while, or at least we thought. I wouldn't say overconfident; I would say cautiously optimistic. We all knew how much preparation for an eventual attack on Eridonia had already taken place, after all; this is what we had trained so much for. It's the fighting with your back to the wall; as a whole State, a whole Species - that idea knowing that there's no one coming to bail you out if you fail. 'Those are the thoughts that make us human' they say, but at the same time, I can't help but contemplate the idea that we may be standing on the brink of the final days of humanity in Aquarius. -Unnamed Ensign, 1st Rapid Response Force, Eridonia Core Sector Fleet, Aquarian Imperial Navy Despite all the anxiety, the fear, the 'human' elements of the 'machine'; we stood together as one. There isn't much more impressive and awe-inspiring than seeing an Imperial Dreadnought getting underway with a dozen cruisers at her side, all ready to give everything they have to something I'm a little cautious as to call a 'final stand'. We were scared, we're human, after all. But we absolutely had the courage and the dedication to see this through until the end, whatever that end would be. -Unnamed Ensign, 3rd Standing Guard Force, Eridonia Core Sector Fleet, Aquarian Imperial Navy The precipice we stand upon now, as a people; a species, unified, represents a turning point in our history. I will not draw from the history of the human species, but from Aquarius; as Aquarians, we have defined our own history; one that today, we will proudly enshrine in the annals of human history as a moment that we took our place among the stars, and we stood by it. Unwaivering. As your leader, I stand by each and every one of you - from the highest to the lowest ranks. Each and every one of you will do your part, and I will do mine. I will work from behind the scenes to co-ordinate and direct your passion into a stalwart and tangible shield that, let me tell you now: will hold back these alien, inhuman aggressors. But not only that, after they have worn themselves down upon the barbs of our shield, we will return the gesture ten-fold, in-kind, and promptly. The enemy has declared they cannot co-exist with us without genocide; and so we will accept that declaration and deliver unto them, a genocide never before seen in the history of their people, or ours. Let the Aliens test our ability to wage all-out war. They will not find us lacking. -The Director, excerpt from The Director's Speech, broadcast to all Imperial Navy units taking part in the first-phase defence of Eridonia, 4521 A.D.
- I like Microsoft Edge, but I am switching to Firefox effective immediately for reasons not actually innately related to the Browser itself.
UPDATE: Seems to work. Firefox it is <3 Because. Fuck. YouTube. Adverts. Oh, here's a guide I found that I will be following. I will update this if it is successful. I would rather simply stop using YouTube entirely (I have alternative ways of acquiring that content, trust me). than sit and watch those cancerous fucking adverts. Fuck you google, shoving that shit down my throat. And no, I won't pay a penny to your stupid fucking ShitTube Premium crap until you STOP ACTIVELY HOSTING HOSTILE RUSSIAN PROPAGANDA PRESENTED AS "FACT" YOU FUCKING TOOLS. RIP Chromium browsers Whenever the fuck Idk - June 2024 F.
- (RP) TN-2425C Incident Task Force A N-Comm Logs Transcript
|| [AUTHENTICATION SUCCESS] || ACCESSING AIN INCIDENT REPORT DATABASE. . . || COMPLETE. || ACCESSING INCIDENT [TN-2425C-1]. . . || COMPLETE. || DISPLAYING TRANSCRIPT. . . {TS REDACTED}[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Task Force A is approximately 100,000 K from NAV-POINT CASTLE. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Report status of high resolution SDD scans. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Ineffective. We are still too close to the debris field. I am unable to reliably determine scan data points beyond a 1000 K tolerance threshold. EWAD remains limited to Wide-Beam MLADAR fallback at this time. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[NVO]->[CPT]: Captain. There is deviation in our projected trajectory - we are closer to the debris field than anticipated. Distance closing rapidly, we will be within 5000 K of the highest density barrier within a few LSM. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: ELI, re-run course trajectory calculations. Something is wrong. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Our current trajectory adheres to the calculated result to align with NAV-POINT CASTLE, within acceptable margins of error, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Verify MLADAR distancing algorithms and sensory data. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: All data verified successfully. Sensors are operating nominally. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[NVO]->[CPT]: Captain. We are within 5000 K of the highest density barrier. Advise caution. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Our apparent trajectory differs from the plotted course significantly. Ruling out localised sensor or system failure, this phenomena could be linked to the gravitational anomaly detected earlier within the core of the debris field. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: ELI, does our deviated course intersect the high density barrier? {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Affirmative. Intersection will occur in approximately 1 LSM and 32 LSS. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[NVO]->[CPT]: 1000 K, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[TF-A]: RV2M-02 to all ships. We have detected a trajectory misalignment on our current projected course. We are approaching the high density barrier of the debris field. Brace for impactors. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[NVO]->[CPT]: Zero distance to intersection. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Hold her steady. ELI, will our shields hold long enough to transition the high density barrier? {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Variable. Current simulated interactions with the debris field based on Wide-Beam sensory data indicate a high probability of shield integrity collapse should our course continue to deviate towards the core of the debris field. Advise immediate emergency course alterations. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Engage manual helm override. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Captain. It is inadvisable to operate the helm in manual mode during cruise. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Override safeguards. Engage manual helm to my station. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Of course, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[TF-A]: RV2M-02 to all ships. I am manually adjusting our heading. Maintain locked formation and accept new course adjustments. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: The helm is yours, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[NVO]: 13.2 degrees Port, hold. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[NVO]->[CPT]: 13.2 degrees Port, holding, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: ELI, override inertial stress safeguards. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Captain. It is highly inadvisable to- {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: This is why humans are in charge, ELI. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Understood, Captain. Overriding ISS. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: 14 degrees Port, Hold. Steady. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[NVO]->[CPT]: 14 degrees Port, holding, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Inertial Stress levels reaching recommended maximum threshold, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Navy spec allows for at least 5% overhead on the book, these hulls are built better than they let you believe in the Fleet. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: I cannot comment on this subject, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[NVO]: Hold 14 degrees Port until further instruction. If I judged this correctly we will miss the core of the debris field by around 10,000K and minimise our time in the high density barrier. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Monitor inertial stress along the lateral superstructure shear fault zones to approximately 458,300 Newtons with inertial dampers at 80%. RV hulls will hold in excess of 500 KN if you angle it right. Escorts have a more uniform CoG so we're the weakest link here. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: 430,000 Newton Meters and steady, captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Re-run projected course calculations with the gravitational deviation from the anomaly factored in. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: New projected course trajectory minimises exposure to the high density barrier to within levels permissible to maintaining shield integrity over 50%, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: There we go. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-75]-[CPT]->[RV2M-02/CPT]: EL-075 reporting shield impactor event. Group Leader, advise. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[FR-EL-75/CPT]: Maintain group cohesion. We are running manual course adjustments to compensate for the gravimetric field disturbance. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[SNO]->[CPT]: Captain, high priority alert from Wide-Beam scans. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[SNO]: Report. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[SNO]->[CPT]: MLADAR pings detected approximately 17,000 K off our starboard bow, course trajectory overlaps ours. IFF inconclusive, without high resolution SDD we cannot determine their mass. Wide-Beam reports a single approximately frigate-sized contact with two consistently corvette or smaller sized signatures flanking it. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: IFF trace on the MLADAR sigs. Radiological scans. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Inconsistent with AIN registers. I am not detecting any known IFF transponder signal. I am detecting elevated EMR levels consistent with high-powered space craft. Advise caution. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Sound General Quarters Alert. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[SBC]: [--GENERAL QUARTERS ALERT TRIGGERED--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[SBC]: [--REDACTED EVENT--] {TS REDACTED[REDACTED]-[RED]: [--OBJECTIVE ASSIGNMENT: ELIMINATE ALL CONTACTS--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: [REDACTED] has been activated under [REDACTED], effective immediately, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[TF-A]: RV2M-02 to all ships. We have detected unknown contacts on an overlap course trajectory. All ships to combat-ready status immediately. General Quarters. Repeat: All ships General Quarters. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-75]-[CPT]->[TF-A]: EL-075 is entering combat stance. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--GENERAL QUARTERS ALERT TRIGGERED--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/PRG-HY2114-02]-[CPT]->[TF-A]: HY2114 reports combat ready stance. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/HY2114]-[SBC]: [--GENERAL QUARTERS ALERT TRIGGERED--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Synchronise the Battle Network with all ships factoring in an in-cruise interception from the new contacts along our current heading. Fleet ROE is RET only but given the nature of the situation I'm willing to make the first move if our new 'friends' don't declare their intentions promptly, given we are broadcasting standard short-range IFF data. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Synchronisation complete, Captain. The unidentified contacts are already within the effective minimum engagement range of our A-Type battery, effective fire is unlikely to be achievable at the current heading and velocity. Escort FR-EL-075 will be able to conduct in-cruise engagement from their B-Type battery at approximately 1,000 K from course overlap with a success rate of approximately 80%. Accuracy of engagement is severely degraded by the relative initial velocity of both parties. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: It's not possible to drop cruise and deaccelerate quick enough. The "book" doesn't factor in high-speed in-cruise intercepts like this simply because this shouldn't be possible. EMR readings are climbing but I'm not seeing a spike as expected before weapons discharge. Do they even know we're here? {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: EMR readings are climbing in consistent relation to potential thermal build up during high-speed cruise. It is unlikely the contacts have powered weapons if we broadly apply AIN energy densities to their given, assumed warship classifications. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Estimate time until intercept at point-blank. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Approximately 3 LSM. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Activate Broad-Wave and directed EM Jammers. Target the largest contact with the Tight-Beam EM dazzlers. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[TF-A]: RV2M-02 to all ships. Switching Battle Network to Combat Mode. All ships prepare for Action and express OC silence. Adhere to Battle Network cohesion unless otherwise instructed. RV2M-02 going OC Silent. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[SBC]: [--ENGAGED ACTIVE EWS--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: TBEM Jamming Array in Alignment; Jamming activated. BWEM Jamming online. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Synchronise all ships, deploy active countermeasures. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Countermeasures deployed. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[SBC]: [--DEPLOYED ACTIVE COUNTERMEASURES--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--DEPLOYED ACTIVE COUNTERMEASURES--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/PRG-HY2114-02]-[SBC]: [--DEPLOYED ACTIVE COUNTERMEASURES--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/HY2114]-[SBC]: [--DEPLOYED ACTIVE COUNTERMEASURES--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Energy spike detected in EMR output from all unidentified contacts. Distance closing to 3,000 K. Advise caution, they have likely powered weapons. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Whoever they are, we caught them off guard with the jammers. Synchronise Battle Network with FR-EL-075 increasing relative velocity to us, closing the distance to within 1,000K. Target the lead contact, Fire at Will. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Acknowledged, Captain. 2,000 K and closing. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--ENGAGED [UNIDENTIFIED CONTACT C-01] --] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--REPORT ENGAGMENT: NO CONFIRMED HITS--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--REPORT ENGAGEMENT: ADJUSTING FIRE--] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Contacts are within 1,000K, Captain. I have conducted short-range high-resolution MLADAR scans and the data is inconsistent with any known human space craft. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--REPORT ENGAGEMENT: CONFIRMED HITS ON [UNIDENTIFIED CONTACT C-01] STATUS: ACTIVE --] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: I am detecting high-energy pulses emanating from the lead contact. They are consistent with plasma-based weapon discharges. However, we appear to have engaged the enemy while they are in a disadvantageous position; their stern is aligned with our bow. It is unlikely they are able to respond with their full weapons capabilities if it is assumed they are consistent with [REDACTED]. Relative velocities of their weapons fire are degraded due to the intercept circumstances. Evasion will likely be trivial. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Boost frontal shield arcs in any case. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--REPORT ENGAGEMENT: CONFIRMED HITS ON [UNIDENTIFIED CONTACT C-01] STATUS: SHIELD COLLAPSE --] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--REPORT ENGAGEMENT: RECIEVING HOSTILE FIRE FROM [UNIDENTIFIED CONTACT C-01] STATUS: ACTIVE. SHIELD INTEGRITY >90% --] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Contact relative velocity stabilising at 600 K. They are almost withing the maximum effective range of our B-Type Battery, Captain. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Hold fire. FR-EL-075 will handle this. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Captain I am detecting multiple new contacts emerging from the debris field bearing 020, approximately 20,000 K from our starboard bow. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Why didn't we detect them earlier? Broadwave is out to about 100K clicks for EWAD, is the enemy employing active camouflage? I don't believe this is a co-ordinated attack. Something feels wrong. It could be related to the anomaly. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Gravimetric and spatial readings from SDD arrays indicated significant space-time distortion around the centre of the debris field, it is possible it may conceal a natural subspace phenomena such as a wormhole. The high density barrier is reducing the effectiveness of our EWAD capabilities. Calculations confirm the current detection distance is within the expected range for the circumstances. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: This complicates things. We may have caught them off guard, but we're not exactly in an advantaged position ourselves. We need to escalate this. Broadcast [REDACTED] to ASG Command on the QEC, High Priority. Request immediate reinforcements be dispatched to TN-2425B, there is a risk the platform there could be attacked. As for these new contacts, I want detailed information from MLADAR sweep; estimated size, estimated mass, EMR levels, trajectory, everything. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: I am compiling a detailed multi-spectrum analysis, Captain. It will take a moment to compile the necessary sensor data and run sufficient logical heuristics to produce a viable conclusion given our lack of effective SDD data. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--REPORT ENGAGEMENT: CONFIRMED HITS ON [UNIDENTIFIED CONTACT C-01] STATUS: DISABLED [PROBABILITY [75%] --] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: FR-EL-075 reports they have successfully disabled the lead contact C-01 with a probability of 75%. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: ELI, detailed report. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Sensors indicate the contact is falling out of formation with the smaller contacts. I have detected a significant reduction in its EMR output, consistent with at least a partial system power failure. Optical scans indicate multiple confirmed 1050/400 Subcalibre Mass Driver penetrative hits on the outer hull with preliminary data suggesting at least some internal damage. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Good, [REDACTED] will want it at least somewhat intact for analysis. Have the PRG-HY2114-02 break formation and deploy a limpet to stabilise its course for retrieval. FR-EL-075 will Switch targets to the 'escorts'. Standby to engage with our own B-Type battery if necessary. Monitor the trajectory of the new contacts and give me that sensor report. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: I have completed the sensory report, Captain. New contacts C-04 and C-05 are consistent with frigate-class warships similar to the C-01, with a probability of 80%. The third new contact, C-06 is much larger and consistent with a cruiser-class warship. I am not detecting any smaller escorts in formation, however there is potential that their signatures are masked by interference from the debris field. At our current rate of acceleration to NAV-POINT CASTLE along the adjusted trajectory, they will be within 10,000K of us in approximately 20 LSM. Advise caution {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: We have no idea how many more there are beyond our sensor range in the debris field. We have no choice but to conduct an emergency cruise exit and engage the enemy proper, in circumstances more advantageous to us. Transmit a detailed report and update to ASG Command on the QEC, and inform [REDACTED] of the developments. I await their prompt response. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--REPORT ENGAGEMENT: RECIEVING HOSTILE FIRE FROM [UNIDENTIFIED CONTACT C-02] STATUS: ACTIVE. SHIELD INTEGRITY >90% --] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--REPORT ENGAGEMENT: RECIEVING HOSTILE FIRE FROM [UNIDENTIFIED CONTACT C-03] STATUS: ACTIVE. SHIELD INTEGRITY >90% --] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--REPORT ENGAGEMENT: CONFIRMED HITS ON [UNIDENTIFIED CONTACT C-02] STATUS: SHIELD COLLAPSE --] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/FR-EL-075]-[SBC]: [--REPORT ENGAGEMENT: CONFIRMED HITS ON [UNIDENTIFIED CONTACT C-02] STATUS: DISABLED [PROBABILITY [75%] --] {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: ELI, we'll try and disable the remaining close contact with minimal damage to its hull. FR-EL-075 will hold fire with their B-Type SMDs and engage subsystem targeting with their C-Type point laser weaponry. Synchronise Battle Network and have HY2114 engage with their B-Type point laser battery. Engage with our B-Type point laser battery. Target their drives and weapon systems. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: Begin a synchronised Task Force emergency cruise exit at our current position. Fire deaccelerators when contact C-03 is disabled. PRG-HY2114-02 will remain free of formation and deploy limpets to stabilise their trajectories for retrieval. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[CPT]->[ELI]: When we drop out of cruise, standby to calculate firing solutions on the new contacts with our A-Type IMPAC battery and load anti-ship warheads to L-class torpedoes in launch bays BS-1 through BS-16, BP-1 through BP-16. Instruct FR-EL-075 to maintain their current relative position and not to move ahead and engage. ROE is still RET unless I give the order otherwise. {TS REDACTED[AIN/ASGSF-9SDF/TF-A/RV2M-02]-[ELI]->[CPT]: Acknowledged, Captain. || ............................... || ERROR LOADING TRANSCRIPT || THE REQUESTED DATA IS INCOMPLETE. || [AUTHENTICATION FAILURE] || CLOSING DATABASE. . .
- Never before have I been so negatively effected by a single video game.
This post may not be coherent. I am writing this post to cope (yes, even if you internet scum find that meme-worthy) with extreme anger and powerlessness that comes from the culmination of a long time affliction of playing the game 'War Thunder'. I have spent a lot of money in this game, but the sunk-cost fallacy must end, and I must terminate my involvement in this game effective immediately. Never before in my life have I been so negatively effected by such a broken, unbalanced, blatantly unfair online competitive gaming experience with such a toxic, disgusting, subhuman-by-choice community of entitled, whiny manchildren. It ends now. I'm terminating my account with >£500 worth of in-game vehicles and over a year of premium time left, because, with inability to overstate this, I am no longer able to accept self-harming because of the sunk cost fallacy of a single video game.
- (Meh) Meh, the "me problem"
So where do I start? Does it even matter where I start? Not really. So here goes. This post is just going to be a sash-thought-shit rant crap post so whatever. Today I triggered an old but still very familiar "emotional response" in my stupid, squishy, organic neural processing clump in my skull. It's something I've encountered many times before, mostly in my later teenage years and early 20s. Now I'm nearly 31, it's happened less often but that is largely down to the improved coping mechanisms I've developed, rather than the issue "going away", so to speak. And I have a LOT of coping mechanisms, believe me. So maybe I should actually state what the issue is - Gender dysphoria. Or, well, it involves gender. It's definitely Dysphoria, though; the absolute opposite of euphoria, a total feeling of hopelessness and melancholy. Even as I type this, my face is slumped into a frown and I can't even feel any sense of positivity or self-worth. The central feeling revolves around my brain, creating physical feelings such as the "Butterfly feeling" in my belly, shaking, etc. This central feeling is hopelessness. The hopelessness is very real. It's knowing that you're afflicted with a problem that has no solution, no way around, no "light at the end of the tunnel", so to speak. Absolutely none. The feeling will always haunt you until the day you die and there is nothing, absolutely nothing, you can do about it. Well, nothing to solve it, but there are sure ways to stop it. If you know what I mean. I'm talking about my body. Being who, what, I am. A male, in this life, this person, sitting here in bed typing this. A "longing" to be someone I'm not, in situations I'm not, many of which I struggle to understand the reasoning behind, but I've had this feeling for long enough - I've studied it long enough - to come to a basic conclusion. I wish I was someone else, but who? Do I wish I was female? or is this dysphoria hiding behind a façade of Gender Dysphoria because of the social situations I mostly encountered (online, male, gaming communities) creating a sort of "special status" for females? Is it the wish to BE female innately, or to be unique, different from my self that I loathe for different reasons, that I can't identify? I don't know. As I look deeper into this feeling, I start to see some trends develop. Self-awareness is important in tracing the sources of emotions back to their origins, often nested behind red-herrings and false positives. Hidden, psychological back-doors in emotions that lead to other emotions, not visible on the surface. That's one thing I've learned a lot over the years of being a hermit, having so much time to think about my own thought processes. As I get deeper, I uncover genuine discomfort/dysphoric feelings deriving from male attributes such as facial hair, and my genitalia/body structure. This discomfort certainly seems to reinforce the idea that my gender identity isn't male, but it doesn't confirm that I'm female, either. Well, identity-wise; I'll always be a male biologically. No escaping that fact. This is the part where it gets convoluted and, well, quite messed up. But since I'm having a trend lately of completely lacking any form of self-control (don't ask, metaphorically), I'll just spew it all down here because typing this does seem to be offering some comfort - likely due to the distraction. There's a very distinct and very strange, somewhat disturbing nuance attached to all my fantasies about being female. Something I've historically not been too comfortable admitting even to myself, let alone on my blog. But since no one actually reads this, I'll just type it here anyway. The fantasies achieve the highest gratification (important word here) in situations where I'm female, but under threat of some kind. In a situation where I may be harmed or even killed. This is likely derived from, or at least somewhat related to my masochistic traits (I don't think I've ever even mentioned this on this blog, lol). It is both sexual and non-sexual gratification from a variety of submissive acts whereby I am submitting to a dominant person, up to and including situations where said dominant person causes me physical harm. The sexual side of this gratification has another component, that I will not discuss here as I'm not ready yet (don't worry, I'm not a pedophile, all my kinks revolve around me, not other people), but it also involves situations where I would come to harm, up to and likely including death. The non-sexual gratification component appears to have a neutralising effect on the dysphoria I mentioned earlier. There is a possibility that it is not related, but simply "crops up" when thinking about how much I hate myself in those moments - i.e, I want to be female, but I also want, even more, to be submitting to someone. But the underlying cause of the dysphoria is likely not the fact that I'm not actively submitting, if you know what I mean. It's just mixed in with the fantasy. There is no denying that I find the male aspects of my body to be extremely uncomfortable, but I would hesitate to suggest I am in a "Pre-MTF Transgender" situation and largely apply myself to the "non-binary" classification since I AM a transhumanist by nature. But that's another topic for another day. Long story short: psychological gender identity is detached from biological sex. I suppose I should actually type about the trigger that caused this excessively long, drawn-out post? Well, it was a situation I've been in many times before; with the same mistakes made, and the same dysphoric feelings as a result. I simply don't learn, apparently. I made a new friend playing War Thunder a while back, a really nice, friendly guy. I never intended the friendship to go beyond War Thunder, and the idea of voice chat was never even considered (as usual with me), but it developed into a situation where voice chat was present and now a second game (PlanetSide 2) is involved, along with more people. I, of course, cannot actually speak on these voice chats for twofold reasons, the first of course being my extremely bad social anxiety, and the second being, well, I told this person I was female. The same driving force of "online, I can pretend to be whoever I want", bullshit that has burned me so many times before: it simply serves to remind me that I will never truly be who I want, and that all my interactions and relationships built upon this lie are fake. Every single time. Even when pronouns are used to refer to me in the voice call I am a participant of (listening only), of course being female pronouns, it simply reminds me that I'm not female really, and I hate myself. This is something I've experienced many times before, and I actually found it better to not pretend to be someone else, and just "roll" with who I am, because the fakeness of the "pretending to be what I WANT to be, but am actually not" was worse than the gratification from a genuine (not fake) friendship. But here we are. I dug myself a hole. Of course, the very fact that I feel I can't just turn around and explain this to this person is another indicator of the underlying issues: anxiety. Fear of human beings. A deep-seated, intrinsic fear of being hurt by other people has broken my ability to interact in many ways. I've typed about this before, many times. This is also the cause of my engagement in the situation to start with - the classic "Can't say no" problem where I'm essentially strung along for the ride and watch myself forced into even worse anxiety-provoking social situations because I literally am terrified to say "no" to people. I guess that comes from the same "self-preservation" complex that kicks in from being constantly, on a daily basis, abused at school and to some degree at home. The constant defensive fear of people, often reinforced by physical consequences (being beaten, hurt, especially at school) has created this broken complex where I must be a "pleaser" and a "yes-man" to stay alive and not get hurt. Because, as I remember very vividly, those behaviours actually helped me avoid physical abuse at school. Lovely. Anyway, the point is that all of these issues culminated today and I was simply overwhelmed. We were playing Planetside 2 (rather hectic large-scale mmo warfare game), I was listening on a 4+way voice call, felt pressured to be good at the game (my aim is terrible, and no, this friend at no point pressured me, this was entirely my own anxiety). Throw in the dysphoria, and the inability to say "i have to go", it was a pressure cooker waiting to explode. Of course it was. and of course, I was absolutely powerless to do anything about it until it actually exploded. And it did. I quit the game instantly and turned my PC off without saying anything. Great, ironic, actually, if you consider the entire premise of the anxiety is to NOT draw attention to myself/provoke a negative response from people. But, my mental health conditions rarely make "sense". The idea was to remove myself from the situation before anyone could say anything and I would go and hide in this very bed, likely cry a bit, and then sleep. Then everything would be OK tomorrow and the cycle repeats. Unfortunately I didn't turn the PC off fast enough and got a response from my friend. Of course, my autistic, broken, anxiety-ridden brain is picking this response apart and coming to all kinds of bizarre and likely completely unwarranted conclusions, but that's just the way it is. So I guess I can add that to the list of shit that hit the fan, finish this post, publish it, go for a piss, then go to sleep. I might also hug my cat. Bye.
- Слава Україні!
Just a reminder that Ukraine is a sovereign, independent, free, democratic nation state with a rich culture, and a great people. Ukraine is older than russia, and has more right to sovereignty than the criminal organisation calling itself the "russian federation". Official website of Ukraine Russia’s war in Ukraine: official website | MFA of Ukraine UNITED24 - The initiative of the President of Ukraine (u24.gov.ua) Благодійний Фонд «Енергія Відродження» (energyofrebirth.com)
- (Sash Rant) S****y NVIDIA Drivers. (Updated: Not drivers)
Update: 27/04/2024: Turns out I didn't jiggle the right part of the cursed 4x8-pin to 16-pin adapter cable. So, the issue was connectivity problems on the 8-pin side, apparently one of the 8-pins wasn't fully inserted (ironic, isn't it?) and caused the problem. I jiggled the 8-pin side of the adapter, and poof, black screen. I can't confirm 100% this fixed the issue but I've resat all 4 connectors and cable-tied them to the 24-pin ATX power cable for stability so the adapter isn't having to act as a weight bearing support, too. I will say, though, this connector is absurd and extremely difficult to work with, given the power socket on the GPU faces away from the source of the cables, meaning you need to bend / stress the adapter cables regardless of anything. I'll update this post if it happens again. Original post: And here we go again, with a persistent problem with NVIDIA's unstable, potato "Studio" drivers, while I'm trying to get shit done. The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\000000a9 CMDre 00000001 00003ffc ffffffff 00000007 00ffffff The message resource is present but the message was not found in the message table Googling reveals it's a known issue with some of their drivers, going back from 2022 to 2016 (nice). Also of note: the "CMDre 00000001 00003ffc ffffffff 00000007 00ffffff" part is repeated in the dozens of "Event ID 14" error entries, but the "00000001" goes up each time, to "00000002" and so on, but sometimes makes larger jumps, like from 00000008 to 00000021. The issue is essentially, a black screen often with a system lockup and then a BSOD (Watchdog Timeout) or it will literally recover, minus the RTX 4090 in Task Manager (Windows Yeeted that shit out the window, apparently). The displays are still reporting no signal, but I use Remote Desktop from my phone to remote-in and shows the PC is still fully operational, minus the GPU. Nice. Rebooting fixes it entirely. For the sake of records and googling: I have tried reseating the GPU and cleaning the slot/finger (PCI-E connectivity issues) Lowering all GPU overclocks to stock closing random 3D software in the background DDU and reinstall the latest drivers Reseating the power cable Jiggling the power cable while its under load (didn't cause it) Jiggling the GPU while its under load (didn't cause it) None of the above fixed it. Things that are consistent with my machine: I have multiple monitors, sometimes they are turned off, but always connected (2 displays usually). I work with Blender (OpenGL preview and OptiX with Cycles) and premiere Pro every day. I have multiple instances of blender open at any time. I leave my PC on for >24 hours at a time, it can be under load for most of that. My CPU and memory are not overclocked (JEDEC RAM) 860W Platinum PSU. RTX 4090 with NVIDIA-provided 4x 8-pin to 1x16pin adapter, all populated with 3 cables to the PSU, 1 is shared. Happens on Driver version 552.22 Studio, (And one before, can't remember version). Notes on symptoms: Doesn't seem to happen under load, even when the GPU is stressing at 450W in premiere pro. Happened at idle, usually after an intense load, or just sat idling on the desktop. Happened immediately when I opened another blender instance (the moment the interface loaded, black screen, GPU gone from Task Manager). Some previous errors have indicated random applications have errored with "Out of memory" exceptions, and 3D-accelerated windows processes like dwm.exe (desktop window manager) have errored out and restarted multiple times before the TDR event in the Event Viewer. Current Diagnosis: driver issue. Current prognosis: gonna happen again -.- current suggested remedial action: FIX YOUR SHIT NVIDIA
- My Journey
I think I have mentioned this before, maybe in passing, maybe in more detail, either way I will mention it again here. I feel like I'm on a journey that has a definitive end (no, I am not talking about life in general which technically fits that criteria). I feel like my journey will 'end' sooner than when my organic body expires. The problem is, I don't feel like I'm able to change the course of that journey. I can't really explain it, but it's something existential, something dreadful, something 'wrong' with my life as it is now. I recognise the approximate framework for the fundamental issues causing this feeling, but I won't be detailing them here, at least not now, in this post. My journey towards that 'end' seems to be accelerating, not slowing down or remaining the same pace; an alarming trend indeed. Yet I feel powerless to change the course, largely because I've been 'dealing' with this issue by pretending it's not an issue and hoping my life will magically adjust itself and everything will be fine. Just another day, Ash. Tomorrow will be better, won't it? I do realise this 'train' terminates at a very undesirable station, so to speak... Maybe I don't want to change course? Maybe that's it. Maybe I'm too scared to face my fears and make the changes? Or maybe it's something else, something else entirely and here we are - yet another loop in the endless jumps of the race of coping with a distinct lack of control. Sounds about right.
- (RP Animation) War is Coming (4512 A.D.)
Teaser for the the looming Second Battle of Eridonia in the human-Tyandirric war.
- (Real World) The russian federation isn't a sovereign country
Everything can be easily explained by simply describing the russian federation as what it literally is; this 'state; isn't a sovereign country, it's a loosely organised crime syndicate, similar to a mafia, pretending to be a country and somehow has a seat on the UN. Everything russia does, everything, from foreign relations to internal politics and policies, is functionally no different from a mafia-like organised crime syndicate run by a crime boss sitting in a big mansion. Even the power structure is the same - pure ruthlessness and respect for the one in charge, respect generated by fear and controlling those that oppose you. Mafia. the russian federation isn't a sovereign country, it's a loosely organised crime syndicate, similar to a mafia, pretending to be a country and somehow has a seat on the UN.
- Day 3.
FUCK PEOPLE YEAH!
- Day 2.
Texted Borbossa (via SMS/MMS) because apparently I'm allowed to circumvent my own restrictions on interaction. But I think it was more that I wanted him to know I'm not actually ignoring him. I mean, we all know this is entirely in my head. I'll probably Telegram Zeno later, too. Whatsapp, discord, though? I seem to associate these apps with negative emotions. We'll see.