Soldat PolyWorks v1.4.0.17 with source code

[Predator0520]

Polyworks - The best soldat map making program!

[Alex_DeLarge]

How can I enlarge the size of the background??

[Krillious]

ignore the background and just draw the map, then when you are done press f5 (refresh) and the background would have become bigger to fit the map

[Alex_DeLarge]

Thanks

[[/awesty]]

when i test my maps the guy falls through some of the polys... but he only falls through some parts of them. what do i do?

[Toumaz]

when i test my maps the guy falls through some of the polys... but he only falls through some parts of them. what do i do?

Compile to PMS.

[Mistercharles]

when i test my maps the guy falls through some of the polys... but he only falls through some parts of them. what do i do?

Compile to PMS.

Indeed. Think of the compile to PMS button as the save button.

[[/awesty]]

I did compile it to PMS... o_O... Im not that dumb.

[Toumaz]

Yeah, but you have probably saved or in some way overwritten the compiled file. Just press Compile to PMS, and nothing more.

Also... you might wanna check if it's so silly that your polygons are set to Only bullets collide/Doesn't collide.

[[/awesty]]

they are set to normal. thanks for your help. i will try it out now.

EDIT: Thanks, it works now. 

[jrgp]

2. My scenery window is not displaying any scenery, even when I click "reload scenery list". When I open a map I have previously made, the scenery of that map will appear in the list but again, I cannot reload the scenery and when I try and use any currently on the list I get an error: "Error clicking scenery. Element not found". I've checked all my folders and everything looks to be where it should be, but it still does not work.

I have the same exact problem and doing what VirtualTT said doesn't do anything.
I re-extracted and re-downloaded the zip file several times, but no success.

Any suggestions?

[Horve]

this updated version is sweet and all, but the only thing to complain about is the lack of simplicity towards the scenery organisation.

[MFO]

Can you change the size of coliders?

[Eagles_Arrows]

Can you change the size of coliders?

Yes you can.

[offtopic]Horve, your sig breaks the rules.[/ot]

[Horve]

[offtopic]Horve, your sig breaks the rules.[/ot]

no it doesn't. Its dimensions are: 300x125

[Toumaz]

[offtopic]Horve, your sig breaks the rules.[/ot]

no it doesn't. Its dimensions are: 300x125

[offtopic]
Yeah, now it doesn't. But when Eagles_Arrows posted it indeed broke the rules.
[/ot]

[Wolf_Man]

Pw should work now.... i got a new computer

(yay)

[Anna]

It looks like I'm rewriting PolyWorks in C# and I'd like to take this opportunity to redesign some of the interface. I already have a good idea of how it will be but I also want to hear everyone's complaints and suggestions on what changes to make.

[Skorp]

Hmmmm, I wont help you Ania because I were download a polyworks 10 sec ago.

Hmm I have a question for you. Are you from Poland?

[Mistercharles]

It looks like I'm rewriting PolyWorks in C# and I'd like to take this opportunity to redesign some of the interface. I already have a good idea of how it will be but I also want to hear everyone's complaints and suggestions on what changes to make.

Keron was lame and showed me a screenshot. Not looking bad, not at all. My main suggestion though, which I've been thinking about for a while, is programmable brushes / paint bucket tools.Programmable Brushes could affect vertexes by applying a math function to the current R, G, and B colours. The functions could be stored in a text file that could be edited at any time. Function variables:

r: The new red value that the brush assign to the vertex.
g: The new green value that the brush will assign to the vertex.
b: The new blue value that the brush will assign to the vertex.
h: The new hue value that the brush assign to the vertex. If it goes above 255, it will loop back to 0, and vice versa.
s: The new sat value that the brush will assign to the vertex.
l: The new lum value that the brush will assign to the vertex.

or: The old red value.
og: The old green value.
ob: The old blue value.
oh: The old hue value.
os: The old sat value.
ol: The old lum value.

pr: The red value of the active colour in the pallete window.
pg: The green value of the active colour in the pallete window.
pb: The blue value of the active colour in the pallete window.
ph: The hue value of the active colour in the pallete window.
ps: The sat value of the active colour in the pallete window.
pl: The lum value of the active colour in the pallete window.
po: The opacity in the pallete window. Can be used like a variable, because it will not be used as it normally is in regard to the programmable brushes.

Example of a function that shifts the hues. Should be used with the dynamic shader. Opacity controls the speed of the shift.

h=oh+po

Another example, this one adjusts the vertex brightness without harming its colour saturation. Opacity above 50 brightens, below 50 darkens.

r=or*(po/50)
g=og*(po/50)
b=ob*(po/50)Programmable Paint Bucket does the same thing as the brush, and has the same variables, except each of the old and new variables have v1_, v2_, or v3_ in front of them. For instance, this function averages the vertex colours together, with the opacity tool doing what opacity tools do:

v1_r=(((v1_or+v2_or+v3_or)/3*po)+(v1r)*(100-po))/100
v2_r=(((v1_or+v2_or+v3_or)/3*po)+(v2r)*(100-po))/100
v3_r=(((v1_or+v2_or+v3_or)/3*po)+(v3r)*(100-po))/100
v1_g=(((v1_og+v2_og+v3_og)/3*po)+(v1g)*(100-po))/100
v2_g=(((v1_og+v2_og+v3_og)/3*po)+(v2g)*(100-po))/100
v3_g=(((v1_og+v2_og+v3_og)/3*po)+(v3g)*(100-po))/100
v1_b=(((v1_ob+v2_ob+v3_ob)/3*po)+(v1b)*(100-po))/100
v2_b=(((v1_ob+v2_ob+v3_ob)/3*po)+(v2b)*(100-po))/100
v3_b=(((v1_ob+v2_ob+v3_ob)/3*po)+(v3b)*(100-po))/100I hope you take my suggestions seriously, as I put a lot of thought into them.