User talk:Cvoxalury: Difference between revisions
Jump to navigation
Jump to search
Archives
No edit summary |
SirYodaJedi (talk | contribs) |
||
| Line 8: | Line 8: | ||
Hammer++ is widely used for several games (in TF2 its almost universally used), and the wiki already document workarounds, bugs etc in Hammer++ vs Stock. On those older pages I didn't even add that information myself, that was from other users: ([https://developer.valvesoftware.com/wiki/Info_overlay], [https://developer.valvesoftware.com/wiki/Texture_alignment], [https://developer.valvesoftware.com/wiki/Non-FGD_features], [https://developer.valvesoftware.com/wiki/Func_instance], [https://developer.valvesoftware.com/wiki/Hammer_View_Menu#HDR]>. [https://developer.valvesoftware.com/wiki/Hammer_Face_Edit_Disps], [https://developer.valvesoftware.com/wiki/Hammer_Map_Tools_Toolbar#Hammer.2B.2B_Tools]). I think it's fair to mention it on wiki pages. Pages also document third-party tools that can workaround limitations or provide better convenience features (for example: [https://developer.valvesoftware.com/wiki/Instance#Precompiler]). A particular example is Wall Worms Tools which is by extent the same extension as Hammer++ for mapping. ([https://developer.valvesoftware.com/wiki/Non-FGD_features#Keyvalues], [https://developer.valvesoftware.com/wiki/Visleaf#Examination], [https://developer.valvesoftware.com/wiki/Collision_mesh#3DS_Max_with_Wall_Worm], [https://developer.valvesoftware.com/wiki/DMX#Model], [https://developer.valvesoftware.com/wiki/Wrinkle_maps#Wall_Worm_Model_Tools]), | Hammer++ is widely used for several games (in TF2 its almost universally used), and the wiki already document workarounds, bugs etc in Hammer++ vs Stock. On those older pages I didn't even add that information myself, that was from other users: ([https://developer.valvesoftware.com/wiki/Info_overlay], [https://developer.valvesoftware.com/wiki/Texture_alignment], [https://developer.valvesoftware.com/wiki/Non-FGD_features], [https://developer.valvesoftware.com/wiki/Func_instance], [https://developer.valvesoftware.com/wiki/Hammer_View_Menu#HDR]>. [https://developer.valvesoftware.com/wiki/Hammer_Face_Edit_Disps], [https://developer.valvesoftware.com/wiki/Hammer_Map_Tools_Toolbar#Hammer.2B.2B_Tools]). I think it's fair to mention it on wiki pages. Pages also document third-party tools that can workaround limitations or provide better convenience features (for example: [https://developer.valvesoftware.com/wiki/Instance#Precompiler]). A particular example is Wall Worms Tools which is by extent the same extension as Hammer++ for mapping. ([https://developer.valvesoftware.com/wiki/Non-FGD_features#Keyvalues], [https://developer.valvesoftware.com/wiki/Visleaf#Examination], [https://developer.valvesoftware.com/wiki/Collision_mesh#3DS_Max_with_Wall_Worm], [https://developer.valvesoftware.com/wiki/DMX#Model], [https://developer.valvesoftware.com/wiki/Wrinkle_maps#Wall_Worm_Model_Tools]), | ||
--[[User:Ficool2|Ficool2]] ([[User talk:Ficool2|talk]]) 02:02, 29 July 2024 (PDT) | --[[User:Ficool2|Ficool2]] ([[User talk:Ficool2|talk]]) 02:02, 29 July 2024 (PDT) | ||
:For context, I think he's referring to the edits to [https://developer.valvesoftware.com/w/index.php?title=Prop_static&diff=440305&oldid=440270 prop_static] and [https://developer.valvesoftware.com/w/index.php?title=Static_Prop_Combine&diff=440304&oldid=440271 Static Prop Combine]. | |||
:I undid the undo to static prop combine, as I was going to make the same edit if Ficool didn't. I do believe that H++'s lightmap atlas feature should be mentioned on the [[prop_static]] page (even though I prefer to do things a bit differently to avoid baking a new texture), as it's a feature that I see people getting a lot of use out of (if [https://discord.com/channels/111951182947258368/111951182947258368/1267300870765281310 bug] is fixed), but I do agree that the way it was mentioned deviates back into what we were trying to clean up with Cvox's rewrite.<br/>— [[User:SirYodaJedi|SirYodaJedi]] ([[User_talk:SirYodaJedi|talk]]) 10:05, 29 July 2024 (PDT) | |||
Revision as of 10:06, 29 July 2024
Archives
Hammer++ undo
Hammer++ is widely used for several games (in TF2 its almost universally used), and the wiki already document workarounds, bugs etc in Hammer++ vs Stock. On those older pages I didn't even add that information myself, that was from other users: ([1], [2], [3], [4], [5]>. [6], [7]). I think it's fair to mention it on wiki pages. Pages also document third-party tools that can workaround limitations or provide better convenience features (for example: [8]). A particular example is Wall Worms Tools which is by extent the same extension as Hammer++ for mapping. ([9], [10], [11], [12], [13]), --Ficool2 (talk) 02:02, 29 July 2024 (PDT)
- For context, I think he's referring to the edits to prop_static and Static Prop Combine.
- I undid the undo to static prop combine, as I was going to make the same edit if Ficool didn't. I do believe that H++'s lightmap atlas feature should be mentioned on the prop_static page (even though I prefer to do things a bit differently to avoid baking a new texture), as it's a feature that I see people getting a lot of use out of (if bug is fixed), but I do agree that the way it was mentioned deviates back into what we were trying to clean up with Cvox's rewrite.
— SirYodaJedi (talk) 10:05, 29 July 2024 (PDT)