This program generates arcs and ramps from Goldsource map files, or extrudes them along paths made from path_corners.
Website
Online-Documentation
Latest Update May 2024:
CLI v0.81
- Added new gridsize command for rounding aka snapping vertices to grid.
- Fixed an issue with precise path_corner extrusions where the first curve section would always be recognized as facing inside.
- Adjusted auto-triangulation of brushes.
- Added another return value for Warnings instead of just critical errors.
GUI v0.1.1.0
- Added result dialog to GUI to make it more clear when warnings and critical errors occured.
- Added textboxes for new gridsize command on tab general curve settings II.
Main features:
- Now comes with a GUI
- Turns map files into arcs or ramps or extrudes them along paths
- Preserves original texture shifts and alignments
- Exports into *.rmf, *.map and *.obj file format
- Obtains texture informations from WAD files
- Processes any kind of entity (solid and point)
- Triangulates brushes automatically
- Snaps vertices to grid.
BUG REPORTS
Please report any bugs and feature request to my email (totacATwebDOTde), including the specific files
(map and config file) and other relevant information (e.g. Operating System).
Apparently JACK exports vertices in a different way to Hammer, which created problems during the generation process sometimes, but not always. Hopefully this has been fixed now.
Looking forward to further feedback.
Apparently you're running M2C without using any information from WAD files.
Check out this tutorial I made recently:
http://gibshooter.com/map2curve/tutorial-01-create-a-simple-curved-hallway-in-map2curve/
But really it's no big deal, just go to the M2C WAD folder and add your WAD file paths to the WADList.txt file.
Without looking at the file myself I can't say if those perpendicular errors are a real problem and why they appear but maybe they resolve themselfs when you're using WAD information.
Furthermore I don't know about Proton and usually I am not testing M2C under linux to make sure everything works there. It is designed to work under Windows, which it does well mostly, at least for myself. The interest this app gets is usually too small for me to put more effort into testing it in different environments.
The skip brush is working as a bounding box and is being generated as an example in this template file. You can remove it by setting bounds to "0" for that particular curve object inside of the presetfile "hallway.txt".
There's no brush limit for the tool itself, although the maximum number of curve-sides is 384, which is already pretty high for most cases. Usually you wouldn't use the whole object then, but just a small section.
In the end it is up to you how much wpoly you want to use (or rather how much you are able to use because of the various engine limits, which is probably what you meant by "un-compilable map").