Can't wait to see what people do with this! Long build times though...
From the PDF:
TYPICAL BUILD TIMES: Initial map loads: 20–60 minutes Load times after initial load: 1–3 minutes Build an asset mod (does not include any maps): 10–30 minutes Build a mod that includes one map about the size of Wellspring: 20–40 minutes
Can't wait to see what people do with this! Long build times though...
From the PDF:
TYPICAL BUILD TIMES: Initial map loads: 2060 minutes Load times after initial load: 13 minutes Build an asset mod (does not include any maps): 1030 minutes Build a mod that includes one map about the size of Wellspring: 2040 minutes
Can't wait to see what people do with this! Long build times though...
From the PDF:
TYPICAL BUILD TIMES: Initial map loads: 2060 minutes Load times after initial load: 13 minutes Build an asset mod (does not include any maps): 1030 minutes Build a mod that includes one map about the size of Wellspring: 2040 minutes
Yeah, I just read that. That's pretty amazing. Oh well, I still want to look through it.
Can't wait to see what people do with this! Long build times though...
From the PDF:
TYPICAL BUILD TIMES: Initial map loads: 2060 minutes Load times after initial load: 13 minutes Build an asset mod (does not include any maps): 1030 minutes Build a mod that includes one map about the size of Wellspring: 2040 minutes
Sweet Jesus, who would use this tool kit with load times like that!?
From Shacknews: "Don't expect your modding progress to be quick and painless, though. "Doing significant work will require patience, because internally we use a 300 core renderfarm for megatexture creation," id's John Carmack said on Twitter." Hah. I guess, that's why.
From Shacknews: "Don't expect your modding progress to be quick and painless, though. "Doing significant work will require patience, because internally we use a 300 core renderfarm for megatexture creation," id's John Carmack said on Twitter." Hah. I guess, that's why.
So, on average, how long do you think it would take to create a standard megatexture on your typical quad core home PC?
"Oh, this MEGAtexture is gonna be GRREAAT!!"
How big is the Wellspring map? Aren't the timings based from how the final game shipped? I've had relatively small sized scenes in UDK take a while to process, mainly because of lightmaps. 40GB+ is pretty hefty though.
Can't wait to see what people do with this! Long build times though...
From the PDF:
TYPICAL BUILD TIMES: Initial map loads: 2060 minutes Load times after initial load: 13 minutes Build an asset mod (does not include any maps): 1030 minutes Build a mod that includes one map about the size of Wellspring: 2040 minutes
FFS. Not sure how this mega textures concept ever got out the gate.
Well of course, but the man is much smarter than that. Megatextures should have been shelved at prototype stage; not a mad idea, just 5-10 years too early.
I'm so damm excited to try check this baby out. I wonder if this means we are going to see uncompressed, or less compressed versions of Rage in the very near future.
FFS. Not sure how this mega textures concept ever got out the gate.
From what I understand from our engine guys at work, it has the potential to run much faster than vertex-blended layered textures. Generally, blended textures create overdraw up the wazoo and the more layers you have (ie the more "next-gen" and "totally awesome" you want your mats to be), the worse it runs. It eats dev time, but devs who invest in the tech can set up render farms like the film boys to offset that, but it pays dividends in the quality-vs-framerate tradeoff. Kudos to iD for blazing that trail so the rest of the industry can jump on and build off what they've done to make it better.
I might bite it and download all 43gigs just to play with the tech before we switch to it at work.
Personally, I wont be sad to see the end of the days of blend maps and vertex color.
Replies
It's 35GB minimum.
From the PDF:
TYPICAL BUILD TIMES:
Initial map loads: 20–60 minutes
Load times after initial load: 1–3 minutes
Build an asset mod (does not include any maps): 10–30 minutes
Build a mod that includes one map about the size of Wellspring: 20–40 minutes
Yeah, I just read that. That's pretty amazing. Oh well, I still want to look through it.
Sweet Jesus, who would use this tool kit with load times like that!?
And just think how fun it would be if you kept getting crashes.
Also 35 - 43 GB might be a bit to much for me :P
So, on average, how long do you think it would take to create a standard megatexture on your typical quad core home PC?
"Oh, this MEGAtexture is gonna be GRREAAT!!"
It will never be the hobbyists toolset in the way the previous engines were due to the pipeline.
FFS. Not sure how this mega textures concept ever got out the gate.
Well of course, but the man is much smarter than that. Megatextures should have been shelved at prototype stage; not a mad idea, just 5-10 years too early.
From what I understand from our engine guys at work, it has the potential to run much faster than vertex-blended layered textures. Generally, blended textures create overdraw up the wazoo and the more layers you have (ie the more "next-gen" and "totally awesome" you want your mats to be), the worse it runs. It eats dev time, but devs who invest in the tech can set up render farms like the film boys to offset that, but it pays dividends in the quality-vs-framerate tradeoff. Kudos to iD for blazing that trail so the rest of the industry can jump on and build off what they've done to make it better.
I might bite it and download all 43gigs just to play with the tech before we switch to it at work.
Personally, I wont be sad to see the end of the days of blend maps and vertex color.