PolyWorks
From wiki.soldat.nl
| PolyWorks | |
|---|---|
| | |
| Developer: | Anna Zajaczkowski |
| Curr. Vers.: | 1.3 |
| Releasedate: | 09/03/06 |
| OS: | Windows |
| Category: | Tools |
| Website: | http://www.soldatforums.com/index.php?topic=174.0 |
General Information
Polyworks is a MapMaker created by Anna in Visual Basic. It significantly improves upon the Official MapMaker while reintroducing many of the novelties found in the old Edit Pro program by Meitzi.
Contents |
Links
Download the latest version of Polyworks
PolyWorks FAQ
01. What is PolyWorks?
PolyWorks is a map editor for Soldat.
02. Where can I get the latest version of PolyWorks?
'The latest test version can be found on irc in the #soldat.polyworks channel on quakenet.
03. Why is there no help file?
There is now :D
05. Can you make polys go behind the player?
No, this isn't possible in Soldat.
06. The Palette/Scenery/Display window doesn't show, and it's checked off in the Window Menu.
Try Window -> Workspace -> Reset Window Locations.
07. Can you make the controls like in MapMaker?
No. You'll get used to it.
08. How do I put multiple textures in my map?
Put two or more textures into a bitmap and use the texture tool to manipulate the texture coordinates.
09. I get this error when I try to run PolyWorks: System Error &H8007007E (-2147024770). The specified module could not be found.
Make sure these files exist in your Windows\System32 folder: MBMouse.ocx, COMDLG32.OCX, mscomctl.ocx, msvbvm60.dll, dx8vb.dll, scrrun.dll. The first three are included in the PolyWorks zip, the others can be found with google. If putting them in the Windows\System32 folder doesn't work try resistering the missing files: start -> run, type in regsvr32 name_of_file.dll_or_ocx.
10. I get a runtime error when I start PolyWorks.
Try changing the Dir entry in the Preferences section in polyworks.ini to your Soldat directory.
11. Are there poly bugs in maps made with PolyWorks?
In PolyWorks the "bouncy poly" bug has been eliminated (where polys would randomly turn bouncy along the edge after compiling). Poly bugs associated with vertices still occur, but they are easy to prevent with correct poly placement. Read the Map Maker Manual for more info.
12. I get a Direct3D initialization error when I start PolyWorks.
Make sure your colour setting is either 16-bit or 32-bit (control panel -> display -> settings tab).
Version History
Changes in 1.3:
- customizable fonts
- texture window
- changes to texture panel in properties window
- gdi+ for png support (requires gdi+ dll on non-windows xp systems)
- fixed scenery timestamp
- fixed scenery file name (case sensitive)
- horizontal flip on waypoints changes left<->right
- colours picked from map are selected in the palette
- save/load workspace
- various bug fixes
Changes since v1.0
- create poly with selected vertices function
- better skin support
- import function
- keyboard input with directinput
- loads png and jpg scenery and textures
- load compiled map from Soldat Maps folder
- select vertices by colour function
- waypoint support
- fixed some maps causing errors when loading
- choose uncompiled maps dir and prefabs dir
- check boxes and option boxes have clickable labels
- hotkeys for waypoints
- hotkeys for display layers
- changed prefabs format and extension to .PFB
- fixed undo making invisible polys visible
- properties window shows number of polys/scenery/spawns/colliders/waypoints/connections
- properties window shows element name of scenery when single scenery is selected
- disabled recent files when empty
- creating something sets that layer to visible if it is not
- can only colour polys/scenery when visible
- experimental textured quad function
- pressing F1 or the ? button opens the help file
- turned off vsync
- various bug fixes
Changes since first release:
- fast compile, no bouncy polys
- [ and ] cycle through tools
- custom hotkeys
- gfx.bmp split up into two files
- automatic directory detection
- colour picker tool
- show vertex colour radius
- compile progress bar
- type in zoom level
- map options
- spawn points
- colliders
- scaling
- rotation
- scenery
- constrained transformations (hold shift)
- flip/rotate
- scenery/polys snap to grid while creating/scaling
- tab cycles through vertices/polys/scenery
- gostek object
- actual size function
- fit to screen function
- properties window
- recent files
- ini files
- hex code in colour picker window
- arrow keys move texture coords with texture tool
- undo/redo
- run soldat with last compiled map
- move/texture tools work when no vertices are selected
- fixed lighten, darken, difference blend modes
- help file
- lots of bug fixes and improvements
