ofc 3.24 is also on the 4.0 codebase, and a more recent version as well. But having a playtest advertised as 'come play a slightly older version of the game, but with Pyro!' probably wouldn't work as well 
Game Discussions Star Citizen Discussion Thread v12
- Thread starter Yaffle
- Start date
-
- Tags
- star citizen
They'd need to get the 4.0 codebase working nice first...
It seems fairly shaky in the 3.24 PTU as it is...
Alongside the novel bugs...
robertsspaceindustries.com
And like, all the old bugs. (Hull C is borked again, mineables not spawning etc)
Nevermind. I'm sure the Zeus bugs will get fixed in time
It seems fairly shaky in the 3.24 PTU as it is...
we have tried several times in the last few days to test the new event in the PTU but we still can't say anything about it because the performance of the PTU is currently so bad,
that testing the event is not even possible.
The servers have such bad FPS.
Calling a ship to be able to fly in the first place is difficult, alone landing on a mission without ramming the ship into the ground due to dsync or hitting an enemy because they are jumping around doesn't help at all.
In theory, the event and its missions seem to be well-intentioned but not playable in the current PTUs
Spectrum - v7.4.3
RSI’s Spectrum is our integrated community and player interaction service, including chat, forums, game integration, and Player Organization facilities. Player Organizations (“Org”...
Alongside the novel bugs...
[All Waves PTU] Star Citizen Alpha 3.24.2 PTU.9381373 Patch Notes - Star Citizen Spectrum
Star Citizen Alpha Patch 3.24.2 Alpha Patch 3.24.2 has been released to the PTU, and is now available to test! Patch should now show: VERSION 3.24.2-PTU.9381373. Characters in this new...
robertsspaceindustries.com
And like, all the old bugs. (Hull C is borked again, mineables not spawning etc)
Nevermind. I'm sure the Zeus bugs will get fixed in time
Marketing has already decided 3.24 is going to Live today - your issues are irrelevant - buy a Zeus!
Source: https://twitter.com/RobertsSpaceInd/status/1846270957310083556
Source: https://twitter.com/RobertsSpaceInd/status/1846270957310083556
Well, they already sold the ship. Why bother fixing it?
V12 of the thread, nearly 4000 pages and still no game just wow.
Viajero
Volunteer Moderator
Is it possible that CIG genius modus operandi of releasing extremely crappy, buggy, broken stuff on top of already extremely crappy, buggy and broken stuff is catching up with them slowly but surely?They'd need to get the 4.0 codebase working nice first...
View attachment 404761
It seems fairly shaky in the 3.24 PTU as it is...
Alongside the novel bugs...
[All Waves PTU] Star Citizen Alpha 3.24.2 PTU.9381373 Patch Notes - Star Citizen Spectrum
Star Citizen Alpha Patch 3.24.2 Alpha Patch 3.24.2 has been released to the PTU, and is now available to test! Patch should now show: VERSION 3.24.2-PTU.9381373. Characters in this new...
And like, all the old bugs. (Hull C is borked again, mineables not spawning etc)
Nevermind. I'm sure the Zeus bugs will get fixed in time
I mean, I guess you can only ignore how broken your product is for so long. At some point the sheer crappiness and brokenness of it all is going to make quite difficult even to try to release stuff.
Last edited:
How many times have we heard from the faithful, when someone complains about bugs, they say "you don't fix bugs until later in development, no point fixing things when they are still subject to change"
Which flies in the face of Agile and just about any other development practice.
I can imagine though, at CIG, with SC being a massive and woefully managed project, devs simply work around bugs when they develop some new code. So, they need to do something that calls upon a routine that is buggy, they either:
a) Develop their own routine to avoid calling the buggy one
b) Patch in workarounds to their code to handle the buggy results from the routine they are calling
c) Just do it and blame their routine not working on the buggy routine, meaning the new code doesn't work as expected either
d) Fix the broken routine themselves... but devs are under pressure, and fixing someone else's buggy code unless instructed isn't likely to happen.
Let's give a simple example, imagine a sideways platformer game, like the old Mario games. The routine for jump should take a parameter jump_height, which is passed depending on current jump height of the character. They may have a standard jump height, maybe its modified by type of jump, or potions of increased jumping, whatever. Problem is, the jump routine is bugged, it only makes the character jump half the height it should. So what is the developer supposed to do who is coding the part that calls the jump routine?
Let's apply these to the variants above.
a) So, they develop their own jump routine, they call it jump2. Now they have a working jump routine. This is fine, except: now there are 2 routines for doing the same thing. Another coder might not know the difference (poor documentation, lack of code comments) and some might call the old buggy routine and some the new, producing inconsistent results. QA won't understand why sometimes the character jumps the right height and sometimes it doesn't.
b) They use the old routine, but double the size of the returned value so it jumps the correct height. Again, with similar results to A.
c) Consistently buggy
d) Great! Now we have a working routine we all call. Except, maybe some other dev already encountered this issue, and instead of doing D, they did either A or B, meaning again, inconsistent results.
Most scenarios lead to further issues down the road.
Fixing issues as you develop provides a stable and predictable base for what is added later.
How adorably naive to think it might be anything other than con hype.
I know sign ups are slow, but not sure killing backers with hoverquads will help...
CitizenCon 2954 Referral Bonus - Roberts Space Industries | Follow the development of Star Citizen and Squadron 42
Roberts Space Industries is the official go-to website for all news about Star Citizen and Squadron 42. It also hosts the online store for game items and merch, as well as all the community tools used by our fans.
robertsspaceindustries.com
Is that a typical link and did it previously redirect properly under the same URL? Could be a forgotten redirect if that was never used.Carrack variant in the Citcon goodie bag by the looks...
The -Old delivers a 404. The pledge store links to here:
Ships - Roberts Space Industries | Follow the development of Star Citizen and Squadron 42
Roberts Space Industries is the official go-to website for all news about Star Citizen and Squadron 42. It also hosts the online store for game items and merch, as well as all the community tools used by our fans.
robertsspaceindustries.com
Edit: could be a generic redirect for variants. So yes, a Carrack variant is probably up.
https://robertsspaceindustries.com/pledge/ships/aegis-avenger/ redirects to https://robertsspaceindustries.com/pledge/ships/aegis-avenger/Avenger-OLD (404)
Last edited:
It's about Ubisoft, but the at at 21:50 about hiring fresh out of college rings a bell. In general a lot of stuff in that video sounds like CIG as well.
I wonder if its an industry thing at this point and if so was if CIG who started it or took the idea form Ubisoft or if this is what cost suting companies do?
12 Years and $700 Million Later, What's Going on With Star Citizen's Development?
Speaking with over a dozen sources about the turbulent development of Star Citizen at Cloud Imperium Games.
insider-gaming.com
I like the nod to Soulsinger
12 Years and $700 Million Later, What's Going on With Star Citizen's Development?
Speaking with over a dozen sources about the turbulent development of Star Citizen at Cloud Imperium Games.
Lol
Never change CIG...