Talk:Hammer Vertex Tool: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
Line 90: Line 90:


--[[User:Andreasen|Andreasen]] 08:20, 21 Oct 2007 (PDT)
--[[User:Andreasen|Andreasen]] 08:20, 21 Oct 2007 (PDT)
I'm able to reproduce this for manipulated wedges, but the compile process is masking the very small gaps.
--[[User:Molaughlen|Molaughlen]] 08:22, 13 Apr 2008 (PDT)


== Vertex Selection Bug ==
== Vertex Selection Bug ==

Revision as of 08:22, 13 April 2008

Does vertex scaling work on multiple solids simultaneously? I'm trying to manipulate the inside vertices of an arch and I keep getting a crash when I try to move the center circle. —Maven (talk) 16:01, 20 Oct 2005 (PDT)

it works fine for me...sept for the circle part lol—ts2do (talk) 17:34, 20 Oct 2005 (PDT)

  • A section explaining "merging" vertexes is missing.
Probably something that explains how/why a invalid brush is created would be nice, if somebody has a moment. I'm about going for bed. If I get a chance tomorrow though, I'll check on it. Hectate 19:27, 12 Nov 2007 (PST)


Vertices keeps moving when reloading the map

I vertex edited several box solids into a ring, but when I reloaded the map, some random vertices had moved less than half a unit in height (only). This is very strange, as the solids were all 8 x 14 x 17 units big, and convex. When does vertices move around like this, and how do I stop it/prevent it from happening again? --Andreasen 05:12, 21 Oct 2007 (PDT)

It is in the hammer bugs article, but it has't been fixed. I assume hammer has problems with saving vertexes in such positions. I can't make domes because of this bug. Solokiller 05:18, 21 Oct 2007 (PDT)
I scanned through the Source SDK Bugs/Hammer bugs article without finding this particular bug. However, the bugs associated with vertex editing are numerous. Sadly, I wouldn't recommend editing the standard solid shapes in Hammer to anyone. Edit: I've looked into the issue some more, and found that the vertex tool loses its precision when dealing with certain "complex" shapes, despite these shapes being convex. Below is such a shape, that you can recreate in your editor in order to try to determine the problem. Just paste the following into a .vmf file:
solid
 {
 "id" "311"
 side
 {
  "id" "1166"
  "plane" "(332 -30 80) (342 -23 80) (350 -31 78)"
  "material" "DEV/DEV_SLIME"
  "uaxis" "[-1 0 0 0] 0.25"
  "vaxis" "[0 -1 0 0] 0.25"
  "rotation" "0"
  "lightmapscale" "16"
  "smoothing_groups" "0"
 }
 side
 {
  "id" "1165"
  "plane" "(342 -23 72) (332 -30 72) (338 -40 72)"
  "material" "DEV/DEV_SLIME"
  "uaxis" "[-1 0 0 0] 0.25"
  "vaxis" "[0 -1 0 0] 0.25"
  "rotation" "0"
  "lightmapscale" "16"
  "smoothing_groups" "0"
 }
 side
 {
  "id" "1164"
  "plane" "(350 -31 72) (350 -31 78) (342 -23 80)"
  "material" "DEV/DEV_SLIME"
  "uaxis" "[0 1 0 0] 0.25"
  "vaxis" "[0 0 -1 0] 0.25"
  "rotation" "0"
  "lightmapscale" "16"
  "smoothing_groups" "0"
 }
 side
 {
  "id" "1163"
  "plane" "(338 -40 78) (338 -40 72) (332 -30 72)"
  "material" "DEV/DEV_SLIME"
  "uaxis" "[0 1 0 0] 0.25"
  "vaxis" "[0 0 -1 0] 0.25"
  "rotation" "0"
  "lightmapscale" "16"
  "smoothing_groups" "0"
 }
 side
 {
  "id" "1162"
  "plane" "(342 -23 72) (342 -23 80) (332 -30 80)"
  "material" "DEV/DEV_SLIME"
  "uaxis" "[-1 0 0 0] 0.25"
  "vaxis" "[0 0 -1 0] 0.25"
  "rotation" "0"
  "lightmapscale" "16"
  "smoothing_groups" "0"
 }
 side
 {
  "id" "1161"
  "plane" "(338 -40 72) (338 -40 78) (350 -31 78)"
  "material" "DEV/DEV_SLIME"
  "uaxis" "[-1 0 0 0] 0.25"
  "vaxis" "[0 0 -1 0] 0.25"
  "rotation" "0"
  "lightmapscale" "16"
  "smoothing_groups" "0"
 }
 editor
 {
  "color" "0 195 132"
  "visgroupshown" "1"
  "visgroupautoshown" "1"
 }

--Andreasen 08:20, 21 Oct 2007 (PDT)

I'm able to reproduce this for manipulated wedges, but the compile process is masking the very small gaps. --Molaughlen 08:22, 13 Apr 2008 (PDT)

Vertex Selection Bug

I'm reporting a bug: When attempting to select a single vertex that lies very close to another vertex on the same plane, both vertices will be selected. Likewise, they will both be unselected when presently selected.

This is a fairly annoying problem when attempting to merge the vertices. The current workaround is to move both vertices to ensure one vertex lands on a grid line, and then the other to drag onto first for the merge. If you drag one vertex towards the other vertex that lies just off the 1 unit grid line, then the merging does not occur. Once you are in this state, it's impossible to select a single vertex. My only workaround while in this state is to undo the action.

[I removed my previous post due to it being a newbie vertex editing problem (producing invalid shapes and not checking with Alt-P). My Kung Fu is getting stronger however. ]

--Molaughlen 07:47, 13 Apr 2008 (PDT)