Game Discussions Star Citizen Discussion Thread v12
- Thread starter Yaffle
- Start date
-
- Tags
- star citizen
Funny how the faithful say "you don't debug until close to release" yet have no problem with "assets with more poly and logical components" than whole Skyrim being done upfront without any clue beforehand if the engine and the network can gobble up and spit out from few hundreds of them in few seconds.
Sometimes I reall wonder what the faithful's idea of a normal development schedule really is. As far as I can tell, it goes something like...
- Art and polish
- Testing
- Balancing
- Art and polish
- Detail development
- Game design
- Core functionality
- Feature integration (VR, MMO:ness, economy)
- Debugging
FTFY
- Art and polish
- P2W Asset sales
- Mo-cap and music
- Testing
- Land sales
- Balancing
- Art and polish
- Referal and subscription schemes
- Mo-cap
- Detail development
- Game design
- Bartender AI
- Bartender AI
- Bartender AI
- Bartender AI
- Mo-cap
- Core functionality
- Feature integration (VR, MMO:ness, economy)
- Debugging
- Mo-cap
![[VR] Merkir](https://d2aefvhu2f0gi9.cloudfront.net/data/avatars/m/141/141091.jpg?1553527154){kind=avatar}
Not to forget the final two steps, preferably the week before release:
99. 64-bit positioning and physics engine development
100. Proof of concept prototyping
99. 64-bit positioning and physics engine development
100. Proof of concept prototyping
You both forgot about developing a roadmap for the roadmap towards the end* of development.
* And yes, I'm being wildly optimistic that Star Citizen/Squadron 42 is nearing the end of its development. I'm sure backers will continue to throw good money after bad for years to come.
yeah, we also forgot "network stuff", "server meshing" right at the end between some mocap sessions
None of this can happen until they have built a company, you can't rush big games. The first eight years were mostly building a company. Next Chris takes a long deserved "vacation", rises from the dead and development can really begin in earnist.
Well, SC doesnt know what it is and probably hasnt an intelligent way of degermining what can be left out and what better be ready once you crash through that doorway with full auto fire.
Distance could be a factor, but that's just me.
Played Satisfactory lately. Early Access (is a bit like "it alpha!") - wery pretty visuals. Runs well. But I hear with enough belts you can make the machine tank.
Even that game culls objects and it's buta fracion of a "verse". I think it's basic craft. Considering spawn-in methods - it doesnt really look so great when object suddenly pop in. Kinda OK in outsides since the detail is minor footnote among others - but in FPS range it really sucks.
Last edited:
If only they had some kind of layered or staged interest-management functionality where a player in one specific "box" could trivially be determined to only need to be updated about other "things" in the same "box", and also have "things" that belong in an outer "box" layer be continuously loaded in as needed as the player moved between the different "box" layers.
They could call it "thing-box continuous-loading" or something.
Well, don't tell them - I have a feeling they like to find it all out by themselves.
And if nobody tells them, they can invent it first!
About why SC have to load assets in high quality in a huge radius around a player long before they appear to that player. The scene is on a moon but you can do the same in a space port.
About the viewing distance of SC and the radius of asset loading, two screenshots (the first one is just to explain what the second is showing) :
One of the competitor of the Daymar rally with its support ship from close view
The rally seen by a player from space. The small cones of lights are competitors, even the small bunch of pixels far away. All thoses ships assets can be zoomed in real time with a snipe gun.
About the viewing distance of SC and the radius of asset loading, two screenshots (the first one is just to explain what the second is showing) :
One of the competitor of the Daymar rally with its support ship from close view
The rally seen by a player from space. The small cones of lights are competitors, even the small bunch of pixels far away. All thoses ships assets can be zoomed in real time with a snipe gun.
Fun fact: none of that should require any asset loading and processing that would massively affect frame rate.
Well, unless the purpose is to show off how pathetically tiny the SC world space is...
There is a difference between loading the game objects and streaming in the meshes/textures though. Even if the entity is loaded, there's an entirely separate streaming system (as with most modern engines) that will load up the meshes and textures asynchronously, aiming for whatever LOD is likely to be visible in the near future. The existence of sniper scopes is an endless source of pain, obviously.
Loading that stuff shouldn't affect frame rate though, as Tippis says. The driver has a separate transfer pipeline that's independent from render/compute.
The problem is that SC is not running better than what Agony describe, even on rigs that are way above system requirement. See Asp Explorer posts...
I don't think I've had paging enabled since getting 32GB, I rarely push over 28 in use at any one time. That's gonna be slow as hell though on a mechanical drive.
Yep, had it with my last computer. 8 GB RAM, too, and it showed more and more bottleneck signs. I tried the Anthem demo on it and it was a slideshow. And it wasn't the only game showing such problems.
Of course, sooner or later, as requirements keep getting pushed, we might see a similar bottleneck begin to show up with certain kinds of SSD we're starting to see coming to market
It's amusing that the same hybrid technology which was used to speed up access to regularly used data on hard drives a few years back (I use an array of several 2TB 7200RPM SSHDs on my XBox, swear by them for a mix of speed, capacity, and affordability) is now being used on the newest generation of high-capacity SSDs, as QLC technology significantly decreases the access speed, and so some designs are including a cache of traditional SLC memory working on those same principles.