Commented 3 years ago2021-02-25 22:44:51 UTC
in vault item: FlowgroveComment #103360
Thank you for the feedback! Captain P, thank you for the optimization tips, I'll try to make this map more optimized. It's interesting that you found this map whimsical, another person that tried this map found it oppressing and depressing. Well, except for the circular pool area. I did intend for it to have this clash of tones, where the areas outside the circular pool feel strange, lonely and oppressing, and the circular pool feels normal and comfortable.
Commented 3 years ago2021-02-25 13:46:25 UTC
in vault item: FlowgroveComment #103357
I really like the whimsical setting of this map! It's like falling down a rabbit hole and ending up in the underground botanical gardens of a mad scientist. Speaking about rabbits, it reminded me of the 'Fanolint' levels in the first Jazz Jackrabbit game.
I agree that, in its current form, it's not really suitable for DM. The layout is too linear and the doors, narrow doorways and various protrusions hinder fast movement. If you want to make a 'proper' DM map, I'd suggest creating a 'blockout' level that focuses entirely on layout and gameplay. Keeping it visually simple allows you to make gameplay tweaks more easily. Once you're satisfied with the gameplay, start decorating it, using this map as a style guide.
As for optimizations, maybe you know some (or all) of this already, but just in case, here are some of the things that you can do:
reduce texture scales on large, far-away surfaces (faces are split every 240 texture units)
use func_detail instead of func_wall (entities are drawn entirely even if only a small part is in the visible area, whereas func_details become world geometry)
replace certain details like plants and stones with models (model rendering is more efficient and allows for finer details)
use the gl_wireframe 1 console command to look for areas with lots of face splitting (typically near rounded shapes), and see if you can reduce that with a func_detail or some other trick
use less faces on rounded shapes, especially ones that are never seen up-close (such as the blue overhead pipes)
if you start a 'blockout' map, use gl_wireframe 2 to see which areas are visible at any given moment, and adjust the layout to ensure that not too much it visible from any given position (maps often use U-bends in corridors to block visibility between areas)
Commented 3 years ago2021-02-18 21:01:16 UTC
in vault item: Monsters Sample MapsComment #103333
@Hardian GT: for questions like these it's better to make a topic in the forums, or to ask on the Discord server. Be sure to explain exactly what you're doing, or upload your map so others can have a look at it.
Commented 3 years ago2021-02-18 12:53:08 UTC
in vault item: Monsters Sample MapsComment #103326
@Hardian GT: see the notes at the bottom of the monster_osprey entity page: you'll need a monster_osprey that targets a path_corner (which needs to be part of a cyclic route of path_corners), and at least one monster_human_grunt.
Enjoy every moment. They grow up way too fast.
Also I suggest you only use lowercase letters in your map names, capital letters have caused changelevel problems in the past.
I agree that, in its current form, it's not really suitable for DM. The layout is too linear and the doors, narrow doorways and various protrusions hinder fast movement. If you want to make a 'proper' DM map, I'd suggest creating a 'blockout' level that focuses entirely on layout and gameplay. Keeping it visually simple allows you to make gameplay tweaks more easily. Once you're satisfied with the gameplay, start decorating it, using this map as a style guide.
As for optimizations, maybe you know some (or all) of this already, but just in case, here are some of the things that you can do:
gl_wireframe 1console command to look for areas with lots of face splitting (typically near rounded shapes), and see if you can reduce that with a func_detail or some other trickgl_wireframe 2to see which areas are visible at any given moment, and adjust the layout to ensure that not too much it visible from any given position (maps often use U-bends in corridors to block visibility between areas)@I have a plan
I did the tests, and 100%-ed them lol. But it was just simple HTML and CSS stuff, nothing special.
@Captain P.
I expect to become... very old.
Thanks! She's 2.5, old enough to talk all day long, do jigsaw puzzles and make abstract art. It's a joy.
But... how old do you expect you will become if you felt the need for leading zeroes?
Btw, you're one year closer to death now. Be careful. ( ͡° ͜ʖ ͡°)
Wow! Captain P! I haven't heard from you for so long.
You were my early mapping mentor. Congratulations on your daughter. How old is she now?
But does "tutorial the osprey with command" was really hard or not work?
What do you mean, 'you're off by a factor of [RECORD SEPARATOR]'?
Sorry for my bad english
monster_ospreythat targets apath_corner(which needs to be part of a cyclic route of path_corners), and at least onemonster_human_grunt.