You've missed water physics before the shower system... or is it that you need a tap before water <- WATER MINING whoa I'm getting good at this lets play fantasy SC.
The Star Citizen Thread V10
- Thread starter Sir.Tj
- Start date
- Status
You've missed water physics before the shower system... or is it that you need a tap before water <- WATER MINING whoa I'm getting good at this lets play fantasy SC.
The engine supports water level natively.
True, but we might need better water physics and fidelity as it slide over the characters bodies and add proper scatter physics as water droplets bounce off. Should only cost us 30 fps or so...
Not far off from what CIG is spouting. Remember, they have more content they can add, its just they can't because the engine can't handle it.
Not far off from what CIG is spouting. Remember, they have more content they can add, its just they can't because the engine can't handle it.
That's what object streaming is for. There is no need for all the assets on your 
It (CryEngine / Lumberyard) supports PvE and look at the state it's in. The engine might be able to do it but CIG appear incapable.
And, of course, none of that will be possible without SSOCS, or without whatever's going to replace SSOCS as the next buzzword-heavy fantasy technology that will be guaranteed to solve all of SC's limitations, until it doesn't.
Well, the new buzzword-heavy fantasy technology is already here: fibers!
Specifically:
Now, this isn't fantasy, as such — fibres are a real concept. So real, in fact, that it has already been tried and tested and proven to be wholly inadequate for all conceivable applications since every other solution is infinitely better, to the point where people who actually knew what they were doing abandoned the whole thing over a decade ago:
This post has been stolen wholesale from nasty ebil goons.
Specifically:
Now, this isn't fantasy, as such — fibres are a real concept. So real, in fact, that it has already been tried and tested and proven to be wholly inadequate for all conceivable applications since every other solution is infinitely better, to the point where people who actually knew what they were doing abandoned the whole thing over a decade ago:
CI¬G — always on the cutting edge of obsolescence and abandoned decades-old tech, and always without a clue that everyone else has moved on from this supposedly “new” thing.Nishanov said:
This post has been stolen wholesale from nasty ebil goons.
Last edited:
Genuine Roberts is already busy coding in the garage of his mansion inventing preemptive multitasking. Just you wait and see!
Well I think my computer saved me. This was the second time I've tried to play SC during free fly. First time, the game ended up being "house arrest simulator" as all I could do was get out of bed. The icon to open the door wouldn't work. This week, I tried to download the game twice and in both cases, I received error messages so I gave up again. I guess I will check back when the game is completed...whenever that is.
dayrth
Volunteer Moderator
Quote of the month
Stackless Infidels. Enjoy your thread weaving while every fiber of our bodies is ready to answer the calls.
I'm sure everyone is crafting their thoughts on not including fibers in C++.
Anyways:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p0866r0.pdf
Anyways:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p0866r0.pdf
…and when even the attempted objection confirms the fundamental issues and inapplicability, you know the idea is in trouble.
Also, to Archer some more:
Also, to Archer some more:
Tokamak said:The example use-case (deferring initialisation of unneeded components of a spawning spaceship until required) is trivially solved with regular threads, but after reading more of the article I think they have much greater ambitions.
The use of fibers is emblematic of the way they have developed the engine 'on the go'. Whenever they implement a new feature, it is implemented on a per parent-object basis. This was okay when there were only a few ships and one location, so the copy/pasting was relatively minimal and trouble free. As they kept adding new content, it made implementing features a huge burden and forced them to come up with 'Object 2.0' (which provides a framework to 'macro' in features as needed). The side effect is that there is no real separation of concerns, and everything is poorly encapsulated. It has also led to a combinatorial object explosion, with everything simultaneously doing its own thing... poorly.
Untangling the big ball ofwould necessitate a rebuild of the engine and game assets, which isn't going to happen. They have realised that a lot of the game/object data is 'sparse', and only a small amount of it needs to be running at one time. It seems like the solution is to split up the game into logical chunks by sticking each parent-object inside its own fiber. So you end up with ship fibers, landing zone fibers, point of interest fibers, planet_surface[x, y] fibers... with the idea that you'd just freeze and unfreeze each fiber wholesale, rather then having to manage the individual components inside the chunk of .
I can see this becoming the basis for server meshing. They could extend the fiber functionality to allow fibers to be transferred between servers. So as a server reaches 100% utilisation, they could spin up a new server, transfer half of the active fibers, then transfer the relevant players over. While none of this is exactly seamless, you could see how someone might come to the conclusion that fibers are a solution to the pile CIG has created.
CIG has made a ginormous batch spaghetti, so why not split up the spaghetti into individual containers of spaghetti, stick them in the freezer, and then thaw as needed. That way everybody gets a plate of spaghetti when they want it and when you no longer want spaghetti, you can pop it back in the freezer for the next person. It also means you can cook more spaghetti to freeze without worrying the old spaghetti. This is a very good and sane plan and we can foresee no problems with juggling a million containers of frozen spaghetti.
Last edited:
Every couple of months or so I drop in on Star Citizen to see if anything has changed. CGI's approach to development seems in many ways to be the opposite of FDev. FDev says nothing but keeps making incremental improvements to the game. CGI runs off at the mouth expounding on how great they are doing and the game remains buggier than a quarter-billion dollar bag full of cockroaches. Zoom the view in while in the cockpit and it will not zoom back out. Get out of the chair to reset the view and the QT HUD disappears. Get landing clearance at Port Olisar, maneuver to the indicated landing pad only to receive a warning "Blocking Landing PAD!". Try to set a course and cannot get an icon in the HUD. Set course to another destination, then set the original destination and whoopee! the icon appears but Quantum drive will not engage.
All of those are mentioned in the patch notes conveniently placed right there in the launcher... so you can be aware of those particular annoyances before even launchingEvery couple of months or so I drop in on Star Citizen to see if anything has changed. CGI's approach to development seems in many ways to be the opposite of FDev. FDev says nothing but keeps making incremental improvements to the game. CGI runs off at the mouth expounding on how great they are doing and the game remains buggier than a quarter-billion dollar bag full of cockroaches. Zoom the view in while in the cockpit and it will not zoom back out. Get out of the chair to reset the view and the QT HUD disappears. Get landing clearance at Port Olisar, maneuver to the indicated landing pad only to receive a warning "Blocking Landing PAD!". Try to set a course and cannot get an icon in the HUD. Set course to another destination, then set the original destination and whoopee! the icon appears but Quantum drive will not engage.
Last edited:
- Status