Compiling maps directly with CaWE
Hi all,
thanks to several thoughtful suggestions by Thrawn and Kai about improvements for CaWE, it will soon be possible to compile maps directly within CaWE.
Here is a preview of how it will look like:
http://images.ca3de-community.de/main.p ... itemId=385
Hope you like it.
thanks to several thoughtful suggestions by Thrawn and Kai about improvements for CaWE, it will soon be possible to compile maps directly within CaWE.
Here is a preview of how it will look like:
http://images.ca3de-community.de/main.p ... itemId=385
Hope you like it.
Best regards,
Carsten
Carsten
DONE!
Updated CaWE.exe is at http://carsten.ca3de-community.de/tempStuff/CaWE.exe
You may test it as you wish, I'll then update the entire SDK bundle in one or two weeks.
EDIT 2006-08-08: Updated URL.
Updated CaWE.exe is at http://carsten.ca3de-community.de/tempStuff/CaWE.exe
You may test it as you wish, I'll then update the entire SDK bundle in one or two weeks.
EDIT 2006-08-08: Updated URL.
Last edited by Carsten on 2006-08-08, 19:36, edited 1 time in total.
Best regards,
Carsten
Carsten
-
- Posts:108
- Joined:2006-04-14, 21:11
- Location:Zürich, Switzerland
Not sure ,but after clicking the browse button for the textures, CaWe mutates into a memory hog, not showing any textures but an increase of the consuming mem (i aborted when reaching 350 mb)
This is always repeatable to me .. i can't browse the texture lib of CaWe, but with the old exe it was no problem XD
Edit:
At 450 MB it finally opened the browser ..
This is because of so many mats and textures for the techdemo .. we need to clean things up !
Edit 2nd:
Wheee finally it worked so well, man this is how it should be since the first time i tried it XD
Carsten this was the most valuable improvement so far ..
*running around his first own level*
This is always repeatable to me .. i can't browse the texture lib of CaWe, but with the old exe it was no problem XD
Edit:
At 450 MB it finally opened the browser ..
This is because of so many mats and textures for the techdemo .. we need to clean things up !
Edit 2nd:
Wheee finally it worked so well, man this is how it should be since the first time i tried it XD
Carsten this was the most valuable improvement so far ..
*running around his first own level*
Hi Kai,
this is known behaviour -- 7000+ materials leave their memory footprint after all, see http://www.ca3d-engine.de/phpBB2/viewtopic.php?t=198 for details (the "Note:" below point 3). On my system it even goes up up to 600 MB RAM usage.
Loading all these textures also takes some time, and is responsible for many of the one-time initialization delays that you observe.
It also should have been the same with all previous versions (if you installed them properly), they behaved the same.
All this is caused by the (more than) 7000 materials that CaWE has to load during init (details to be discussed in the TD Dev forum pls ). But you're right: This (the cmats) should be cleaned up, and doing so will also lower system requirements dramatically.
this is known behaviour -- 7000+ materials leave their memory footprint after all, see http://www.ca3d-engine.de/phpBB2/viewtopic.php?t=198 for details (the "Note:" below point 3). On my system it even goes up up to 600 MB RAM usage.
Loading all these textures also takes some time, and is responsible for many of the one-time initialization delays that you observe.
It also should have been the same with all previous versions (if you installed them properly), they behaved the same.
All this is caused by the (more than) 7000 materials that CaWE has to load during init (details to be discussed in the TD Dev forum pls ). But you're right: This (the cmats) should be cleaned up, and doing so will also lower system requirements dramatically.
Best regards,
Carsten
Carsten
-
- Posts:108
- Joined:2006-04-14, 21:11
- Location:Zürich, Switzerland
Please note that languages other than English are okay on this board only when the poster feels that he cannot express himself clearly in English, but can do so in his favourite language.
Answers to such mixed language posts should preferrably be written in English again, possibly summarizing the original (foreign language) question.
This is because the use of any language other than English tends to exclude the vast majority of forum participants from discussion.
Answers to such mixed language posts should preferrably be written in English again, possibly summarizing the original (foreign language) question.
This is because the use of any language other than English tends to exclude the vast majority of forum participants from discussion.
Best regards,
Carsten
Carsten
Who is online
Users browsing this forum: No registered users and 8 guests