Ricebug on 18/6/2013 at 20:19
Got this strange error in my monolog:
[INDENT]Added 662 vertices
Max vertices post tjoint: 17
ERROR: degenerate portal in cell 3297 (vtx [96.333954 271.26834 6.75] nrm [-0.38293585 0.92377496 -0.]), engine can hang if not fixed
ERROR: degenerate portal in cell 3297 (vtx [95.641121 270.98114 6.75] nrm [-0.38293585 0.92377496 -0.]), engine can hang if not fixed
Portalized.[/INDENT]
Found nothing doing a search. Did a cam to cell but Dromed says "no such cell."
LarryG on 18/6/2013 at 20:56
What were you doing to get the warning? Portalizing? I would assume that a degenerate portal is one that collapsed to a single point or line instead of a plane. Remember that the Portalizing process is just a temporary "quick and dirty" generation of portals. The real portalization is called "optimization" and really should be used all the time. In my opinion, with the speed of NewDark's optimization, portalizing should be depreciated. What does optimization report? Does it have an issue? If not, I wouldn't worry.
Ricebug on 18/6/2013 at 22:58
I just use the Build Dialog. It doesn't say portalize or optimize. Running optimize gets the same error.
I thought that if you added or deleted brushes the map had to be re-portalized, and anything else you did fell under optimization.
R Soul on 18/6/2013 at 23:25
In the build dialog, you use WR Quality to choose. 'Draft' is portalize.
cam_to_cell may not work but it does give you a set of coordinates for each vertex.
The command vm_teleport x,y,z will take you there.
AntiMatter_16 on 18/6/2013 at 23:33
@Ricebug
The build_dlg command has an option to Portalize, or Optimize.
Portalize is a quick and dirty method of generating the terrain geometry. Optimize is the exact same process, but it also goes through a process that reduces cell and poly counts. For example, if you had two square air brushes next to each other in the shape of a rectangle, the Portalization process might create two separate cells, whereas the Optimization process would recognize that the two cells could be merged into one.
The optimization process also creates some temporary data called "Optimization hints" that the portalization process can also use to produce optimized terrain geometry. For instance, let's say you ran the Portalization process, you'd end up with unoptimized terrain. Then, if you ran the Optimization process, you'd end up with optimized terrain and a set of "optimization hints". If you ran the portalization process at this point, it would utilize the "optimization hints" data to create optimized terrain that's identical to the terrain produced through Optimization. However, if you CHANGED any of the terrain brushes, the "optimization hints" data would be outdated, and wouldn't produce fully optimized terrain, just mostly optimized terrain. Running the Optimization process again would create updated "optimization hints".
I usually just "Optimize," myself though. It doesn't take much longer. Optimized terrain is what you'd want to release, but it doesn't matter whether you optimize or portalize when you move, resize, delete or add brushes.
Ricebug on 19/6/2013 at 22:58
I tracked the degenerate cell to a solid brush that was sitting at legal angles and position. Deleted and re-optimized. The error disappeared. I'd say the monolog error is in "error...error...things to understand..."
