Local Toolkit Processing

I am not sure exactly how much juice a PC would need to process our zips into pcugcs but if there were a a way you guys could make a downloadable program for doing it so we don't have to wait in queue forever for the next test it would be amazing. I personally would be perfectly happy to pay for it like DLC. I realize it may be a tall order, but my biggest frustrations with the toolkit pretty much all stem from turnaround time on testing changes before releasing something. Between wait times, and weird server timeouts and errors, it can be really irritating.
 
I am not sure exactly how much juice a PC would need to process our zips into pcugcs but if there were a a way you guys could make a downloadable program for doing it so we don't have to wait in queue forever for the next test it would be amazing. I personally would be perfectly happy to pay for it like DLC. I realize it may be a tall order, but my biggest frustrations with the toolkit pretty much all stem from turnaround time on testing changes before releasing something. Between wait times, and weird server timeouts and errors, it can be really irritating.

+ 10000 [heart]
 
I don't know if it's possible or something Frontier would choose to do, but I wholeheartedly agree this would make our lives a lot easier.

Part of the trouble was that they wanted to be able to push out updates and fixes often, but it seems like they could maybe do that with a tool on Steam too.
 
I don't know if it's possible or something Frontier would choose to do, but I wholeheartedly agree this would make our lives a lot easier.

Part of the trouble was that they wanted to be able to push out updates and fixes often, but it seems like they could maybe do that with a tool on Steam too.

Exactly, if it was through Steam it would be easy to update.
 
There's some problems with that, even though i would like to see a local converter, too.
Correct me if i am wrong, but this is my perspective on the matter.

1. The source code - it opens up a possibility to reverse engineer the underlying code structure the game uses for the Cobra Engine. Of course it wouldn't give away too much, but enough for other companies to stoop into the Engine's "logic"

2. Security and Tampering (Moderation) - If you compare it to, say, Second Life, SL has and always had an open structure, the downfall was, anyone could grab the 3D data AND the textures by simply grabbing it off the data stream, And LindenLabs never cared to add encryption. With PlanCo, TMT converts into a in-house filetype container (.pcugc), this is actually a good thing because that's exactly why i stopped creating assets in SL. (It's really painful to see others cashing in on YOUR hard work, and nothing you can do about it without having an (expensive) army of lawyers at your expense. I've created about 20.000 assets in 6 years of my SL "life" (models and textures (no, i am not joking)) and almost all of them could be found in others' shops. If their (the people who copied your assets) jurisdiction is some exotic country, or even another yountry than your own, good luck in getting your justice. I actually like how they've set up TMT and how it's not so easy to "grab" the 3D data. Localizing it would endanger this kind of structure and it wouldn't take long until someone modded a tool to grab the models (and let's not forget the vanilla content, Sam & Co. wouldn't risk any vulnerabilites to the PlanCo assets that are preventable)
And let's assume someone uploaded a , if the TMT was local, they couldn't properly moderate on their terms.

I'd rather see the bugs vanish soon, but maybe a good middle way would be a Viewer of some kind, like a small prog that could display the asset with it's ingame shading properties without actually converting the .fbx
 
A viewer would be a good middle ground. Plus it could check through the FBX and materials to give instant feedback on any basic errors.
 
Back
Top Bottom