Pulse96

1. there is no uber setting and to be honest the graphics settings don't do much at all
2. as of now your fps are network bound so just throwing more hardware at it doesn't help
3. the current RAM usage is about 8 GB so as long as you have Chrome closed you're probably fine
4. 3.0.1 is the most unplayable patch we ever had so I'd suggest waiting 4 weeks 6 weeks for 3.1

I'm using a roccat arvo
not mechanical.. D: god how I hate membrane.

What we need still is an opening theme.
 
So here is the schedule, it's late so feel free to moan about it, i don't intend on strictly sticking on it but its more abput if we get lost in the convo
 
Introductions and Org plug
Whats new
free flight starfarer This months report RtV/AtV Open around the table discussion (do we set a time limit or just talk till we get bored?
 
Arena Commander
What's changed in 2.3, have they fixed the missiles? what needs to be fixed what we want to see implemented in the future (wingman profiles etc) CIG's rather delicate balance between juggling optimization, feature development, and schedule management  
PU
---
Perfomance Star Citizen's Inputs and Layouts (With possible discussion on their benefits/current problems/needed tweaking) Purrrsistance in 2.4  @rucdoc discourse and discuss
 
Community downsides
Renegade's "cheating" - our take as a Org that plays together every week CIGs "secret" PTU and NDA - don't forget they had NDAs before CIG's needed (or unneeded) involvement with the community (With possible discussion on where they need to be better about responding) SC "vs" other sims
 
 
credits

With the recent update to Star Citizen the party system now (kinda) works so our resident Org got together and did some "testing"
 
After 90 minutes we finally managed to do some group shots (courtesy of @Corwin111)
 
 
And as always I streamed the whole thing to our YouTube channel:
 
 
And here are some Highlights by @Corwin111 and  @rentaspoon:
 
I'm going to cut some clips later today and add them here.
 
 
Thanks to @abyss03 @colt92 @Corwin111 @Adreyu @Gyre-Taenn @Pulse96 @rentaspoon and @Krml for showing up.
And just for lolz I'm going to tag @Slick and @LinusTech

EDIT: Be advised that you can now submit your wargame scenarios directly on the UOLTT website. Follow this link. Thanks to @Judahnator and @rucdoc for their lightning fast reaction! 
 
 
Ok guys, with the release of patch 2.2, Crusader is finally allowing consistent party joining and is stable enough to allow us to mix in some work with our usual dicking around.
 
Everyone please feel free to think up and submit your suggestions for wargame scenarios in this thread. And the Project Eden squadrons will do their best not to totally mess them up on our weekly meetups. Suggestions are welcome from anyone at this point, regardless of whether you are a UOLTT member or not. Participation in the wargames will be limited to UOLTT members only, but of course we are always happy to welcome new members.
 
I will start with the first submission. Please try to adhere to the below submission format.
 
====================================================================================
 
Name:
Rescue Mission
 
Context:
 
A VIP is stranded in hostile territory. A rescue team is on a mission to extract the VIP and bring him safely home, while an opposing force has orders to capture and kill him.
 
Area of operations:
Crusader / PU
 
Operational scope:
 
 - Ship-to-ship combat
 
 - EVA combat
 
 - Ground Combat
 
 
 
Number of participants:
4 - 8 (Up to however many the party system and instances allow in the future)
 
 
 
Participant deployment structure:
 
 - One of the participants is designated "Target".
 
 - The rest of the participants are split into two teams - Team A (Rescue Party) and Team B (Attackers).
 
 
 
Participant equipment loadout:
 
Target: The Target is armed only with a pistol.
 
Team A: The rescue party team must be equipped with at least one multicrew rescue ship. The rest of the team fly fighter ships to escort the rescue ship as well as heavy EVA weapons. 
 
Team B: The attackers are equipped with fighter ships and heavy EVA weapons.
 
Ship and weapon types may vary. TBD during the OP.
 
Initial Deployment: 
 
 - The Target is deposited at a remote location, known to both teams.
 
 - The starting positions of both teams are decided before initiating the scenario.
 
Victory conditions:
 
 - Team A must dock/land at the Target's location, extract the target via the rescue ship and escort the Target to a pre-decided rescue location on a station.
 
 - Team B must intercept and kill the target by any means necessary. Either by destroying the rescue ship with the Target on it or by killing the target either before extraction or at the station, before the rescue location is reached.
 
Special rules:
 
N/A
 
============================================================================
 
Well that's it for the first one. It's a bit conservative but don't let that restrain you, go nuts. ^^ It it looks fun, we'll likely try it at some point.