3.23 EPTU LOD issues - just documenting
If you are interested in Star Citizen use my code for free 5000 UEC: STAR-VNSX-7YQP
Spreadsheet toughness tests: docs.google.com/spreadsheets/...
#starcitizen #spacesim #sciencefiction
Erkul's DPS Calculator: www.erkul.games/calculator
Olakeen's Ship Performance Viewer: www.spviewer.eu/pages/ship-pe...
nova_rain's Hardpoint: hardpoint.io/
Dabalta's FPS data: docs.google.com/spreadsheets/...
Component finder:
AterDracones: docs.google.com/spreadsheets/...
TrazosD: docs.google.com/spreadsheets/...
thehumangerm: docs.google.com/spreadsheets/...
Star Citizen - Universal Item Finder: finder.cstone.space/
Legacy Fleet's SPAT tool: docs.google.com/spreadsheets/...
Music
Outro
email (anti bot, remove the blanks): dgiannini @ web.de
Twitter: / camural_sc
Reddit: Camural
Spectrum: Camural
PC specs:
AMD Ryzen 7 7800X3D
64GB DIMM DDR5
NVIDIA GeForce RTX 4090
4 TB NVMe SSD Samsung 990 PRO with Heatsink
2 TB NVMe SSD Samsung 970 Evo Plus
20 TB HDD TOSHIBA MG10ACA20TE
4K 144Hz 32inch main monitor
All game engines, except the newest ones, have trouble with LOD: level of detail: switching from low res 2D background graphics to high res close by 3D graphics. However, I have never seen so many pop ins like with Star Engine, even at walking speed and 2m in front of the player. Documenting this.
All engines have to option to push LOD out to ridiculus distances, but that comes at a cost of course. That is why ue5 uses nanite, to help minimise that penalty. This right here is CIG setting it to short distance in a desperate attempt to improve performance. Might even go as far as saying somebody missed a few zeros.
Reminder that we are not yet fully implemented into star engine. This looks like a temporary situation during the move.
The small trees not loading until you're basically within arms reach is crazy lol. This game never fails to impress.
This is why the engine demo CIG showed at CitizenCon last year rang so hollow for me. That was all canned and baked into the demo. I'd love to hear how many hard drives that footage was on. I play a 2000+ modlist for Skyrim and JUST the LODs for that are larger than the base game itself was at launch in 2011.
I'm watching on a lower resolution with lots of compression but this looks pretty good. The major issue I see is the smaller tree, and some of the further background trees that might need an asset update. The grass and plants fade in at a reasonable distance and don't go through jarring LOD shifts like those trees do. What annoys me is that they're all so static instead of physicalized.
Lod issues are a constellation owers worst nightmarr and i noticed this on ptu. The top center mfds are far enough to derender depending on LOD settings lol. You end up with those 3 MFD vanishing until y ok u zoom in as a result.
At least its not worse that DayZ where a player is hiding behind a bush, can't see anything past it, and a sniper a kilometer away sees this player crouching apparently out in the open.
It would most likely be the exact same, as obviously anyone further away from the things popping in in the video would not see them. Meanwhile player characters have a fairly long draw distance AFAIK. I remember old Planetside 2, where I would snipe players with the Engi's rocket turret at distances where it was just a few pixels on a washed out background.
Popcorn sounds on the background would have fit well here.
😂😂😂😂😂
All engines have to option to push LOD out to ridiculus distances, but that comes at a cost of course. That is why ue5 uses nanite, to help minimise that penalty. This right here is CIG setting it to short distance in a desperate attempt to improve performance. Might even go as far as saying somebody missed a few zeros.
Perfectly adequate for a screenshot simulator.
Would be sick if they work on a nanite type render solution in the future.
They need to implement nanite technology to their engine if its even possible or make more LODs so that change is less dramatic and visible.
@Baltazar009 I don't think CIG can just add Unreal 5's nanite technology into the obsolete Star engine. Switching engines would be an enormous task for a game that is delayed by many years already, Polygon 2015 "By the end of this year backers will have everything they originally pledged for plus a lot more," Roberts says." www.polygon.com/features/2015/3/2/8131661/star-citizen-chris-roberts-interview So we might be focked.
@@Camural Ofc they cant switch engine or just take nanite from unreal and use them in star engine. They need to make their own solution for Star engine which will work similar how nanite works in unreal.
SC "1.0" is beginning to make more and more sense..
That is immersion breaking.
link to issue council report ? ( there would be no point in posting obvious model mismatch w/o reporting it in issue council )
I mean it's not much different on live rn. Yesterday I visited one of the recent settlements and it took 3 minutes until all buildings were loaded in.
@justalex4214 of course it is not any different on live :) We have pop ins of stones at walking speed 2 m in front of the player. Sometimes building only pop in after minutes.
That’s ridiculous
one day i will play the perfect sprace grame
Reminds me of Arma
Did you forget you forget to run Dyndolod?
I don't think server meshing or master modes is going to fix this one, CIG. We all know what that means... IT'S TIME FOR THE NEXT BUZZWORD WONDER TECH THAT WILL FIX EVERYTHING! I joke, obviously, but I do think it's funny how CIG can spend 2+ years hyping up backend tech that every other developer doesn't even mention. Do folks not think Palworld has something impressive under the hood with (at one point) 2 million concurrent players? Of course it does, but you don't see those devs pitching it to players like it's the second coming of Jesus.
@austinm5630 of course server meshing, static or dynamic, if we ever get it, won't fix LOD pop ins. A lot of (older) games have trouble with LOD pop ins. But it is acceptable if the distance isn't too close. Stones and trees popping in at walking speed 2m in front of the player is something special, though :).
Star Engine next gen my ass, still if at least they had it with high fps and stable would be excusable, but not even that!
this is no lod issue.. its an alien planet and these are stealth trees !
Vulcan? Dx11?
@lumavolt doesn't make a difference when it comes to such brutal LOD issues.
They still have to do a lot of work with the forests. They look very unnatural
Need to push that out and make it fade in. Looks bad as it is.
take an outdated and dead engine historically unsuited for multiplayer experiences even back in its time for which there are no experts, no college seminars, no udemy courses, no google hivemind trail and that to this day is unable to properly run its original tech-testimonial flight level as it was built for a hardware paradigm that went exactly the other way - then give it to the cheapest HR possible chosen for their subservience willingness and nothing else as a secondary (outliers nonwithstanding, but outliers are outliers, not the stereotype as defined by median and average). That is what you get - aber TWELVE YEARS and almost SEVEN HUNDRED MILLION wasted (by a company that even fails at implementing a basic fetchquest chain).
@TheEtrattner Cry-engine/Lumberyard/Star-engine is obsolete by now. However, CIG is stuck with it and I won't say: "Just switch engines" because this is an enormous task. In 5 years when Star Citizen still won't be released the situation will be much worse, though.
@@Camural it is also too late for an engine switch. Timewise about 7-8 years. Budgetwise... well.. best leave it at that. But that is this entire project's mantra. The absolute worst possible approach and alternative chosen for everything, at every point. There would have been many occasions where at least something could have been concepted dilligently, systemically. Where somthing would have felt and looked like at least one solid lego brick. But it never was, nowhere, not even attempted.
Nanite would be nice... but hey, we have stupid CryEngine... I mean Lumberyard... I mean StarEngine...
Nanite doesn't solve the pop-in issue, it just removes the need to optimise a game with LODs, which can reduce overall geometry allocation buffers, but still has the exact same issues as standard LODs, which is why most games don't use Nanite, and the ones that do typically use it in more linear areas where you can save on both memory and having to waste time on LOD assets. But if you attempt to use Nanite on larger open world settings, you can very obviously see the pop-in, especially in open maps on Fortnite where you move from far away to up close to an area with dense forestry.
crappy game...