[Micky C]

Really? wow thanks, I personally have no experience with scripts myself...

[Stabs]

Quote

gamevar i 0 0

include names.h
defstate grouphitag
for i selsprites ifactor XXX ifge .hitag 0 set .hitag 1

ends

put that code into a file called yourmap.m32

XXX is the name of the tile it is going to affect
You have to define these tiles in names.h
#define XXX 6000
If the tile your using this for is stock it may already have a name
#define TOILETWATER 921

When you get into mapster select the sprites and bring down the console (~) and type
include yourmap then type

do state grouphitags

it should transform all those sprites to the selected values

ifge .hitag 0 set .hitag 1

if they have a hitag of 0 they will be changed to hitag of 1, this works for xvel, pal, lotag, etc

[Micky C]

ok thanks, this will come in handy

[dukedude]

XThX2, on Oct 2 2009, 09:59 AM, said:

I have the same issue with KP5. I have to use the annoying slow panning which is time consuming.

Oh, gosh. With my computer, panning walls with KP2 and KP8 requires both Shifts to be held, and panning them with KP4 and KP6 is impossible. (I tried everything.) The only workarounds are to use the mouse and Shift (which is not very precise) or to use F8 in 2D mode (where it is very hard to get it right because you can't see it while you're editing it). Out of those two, I easily prefer the mouse method.

[dukedude]

Nfelli64, on Oct 4 2009, 06:16 PM, said:

I have a minor issue. When you are in mapster and the new feature is (T)est level but it doesnt seem to work? is it just me or is this common...

I have the same issue when Mapster32 is in fullscreen mode. It plays the sounds like you would expect, but you get a weird texture instead of the actual level, and I can't even see the menu when I press Esc. These problems don't seem to occur when Mapster32 has a regular window, but then it behaves even worse...

[dukedude]

Spiker, on Dec 29 2009, 03:20 PM, said:

You really have to do something with this poping window that appears in 2d mode on the bottom left side. It's really iritating and useless! My advice would be get rid of it entirely since it only makes mapping more difficult rather than helps. If I need to access this information I press F7 anyway. I think that other mappers would agree with me. Get rid of it or at least make it optional. Just do something with it, thanks!

I think it's a little helpful, but yes, it's a real pain sometimes because it gets in the way of the map when I try to do things down there. Ugh!

[The Commander]

Could we get something added to "mapster32.cfg" that allows us to set the default Grid size. the "G" key in 2D mode.

[Spiker]

From time to time I experience crashes in mapster. Should I upload the files that are created after this happens? Because mapster tells me to do that:P

[Helixhorned]

dukedude, on Apr 2 2010, 03:19 AM, said:

Oh, gosh. With my computer, panning walls with KP2 and KP8 requires both Shifts to be held, and panning them with KP4 and KP6 is impossible. (I tried everything.) The only workarounds are to use the mouse and Shift (which is not very precise) or to use F8 in 2D mode (where it is very hard to get it right because you can't see it while you're editing it). Out of those two, I easily prefer the mouse method.

Check the FAQ.

The Commander, on Apr 6 2010, 04:17 PM, said:

Could we get something added to "mapster32.cfg" that allows us to set the default Grid size. the "G" key in 2D mode.

Yes.

Spiker, on Apr 7 2010, 07:09 PM, said:

From time to time I experience crashes in mapster. Should I upload the files that are created after this happens? Because mapster tells me to do that:P

Definitely! If you think there's Mapster strangeness going on I'd very much like to see that. Can you attribute these crashes to something particular in your map or do they happen at random?

[The Commander]

Helixhorned, on Apr 12 2010, 01:32 AM, said:

Yes.

Quote

CIA-6: eduke32: helixhorned * r1621 /polymer/eduke32/ (4 files in 2 dirs): m32: have default grid size in configuration

Thank you.

[Gambini]

ehm. Talking about Mapster crashes. i get random crashes when panning wall textures (shift+KP). It does happen in more than one map and if i´m not wrong when moving up/down these textures (shift+KP8/KP2).

[Forge]

and I'm still getting random crashes while shading with numpad + and -


also when close to the max wall limit for eduke, adding walls or joining sectors will randomly crash or weird, random sprites sometimes appear that are only visible only in 2d mode. The sprite can have really high numbers like :20345,90876 or sometimes can have three numbers:2346,0,34865. They usually appear on an adjoining wall or vertice that is being worked on and can be easily deleted, but are also usually a sign that a crash is immanent. When viewing a wall aligned sprite in 2d mode, the sprite looks like a letter T with the orientation lines; sometimes these random sprite's orientation lines are dashed.

[Stabs]

stay away from the numpad

hold "shift + mouse1" to move around the textures

hold "ctrl + mouse1 " to resize textures

shade with the mouse wheel.

its much quicker once you get used to it and wont crash on you

[Forge]

I have a trackball, therefore I have no mouse wheel.

"stay away from the numpad" Is that supposed to be some kind of solution?

[Gambini]

Trackballs are for faggots. You know that thing about stroking balls...

I did never know about that mouse trick, it´s certainly cool but pretty unaccurate.

[Forge]

matter of fact I have two track balls....big, red, bouncy track balls that I like to hold in my hands and gently squeeze....

[Gambini]

Just discovered a new issue. Ctrl+PgUp doesn´t align sprites to top anymore in the latest build.

[Sobek]

I haven't been mapping for a while now, but I just got back into things again and for some reason on the latest snapshots (tried the last 3 or 4 including synthesis builds), trying to view my custom textures range in mapster causes it to crash with "CACHE SPACE ALL LOCKED UP!" in the log.

I can place a sprite and edit the tile number in 2d mode with f8 just fine, and I've yet to come across any problem textures or models... I also have a test map in which one of every single texture and model I have is placed in for reference, and that loads fine with no crashes. It just seems I can't view that tile range in mapster (which really gets in the way of placing textures and models that I don't recall the exact tile number of).

Anyone else getting something like this? I've cleaned all the texture caches and tried it in both polymer and polymost, but it's the same either way.

[Forge]

I swapped my trackball for my older one that has a wheel on it. Still have the same problems with random crashes when doing the shading.

[TerminX]

I'm having trouble reproducing the crash with shading... is there a reliable way to make this happen?

[Forge]

Since it's random I have no idea how to "make" it crash. The only consistency I noticed was it usually occurred when I was going from zero to something between 16 and 26. I'd hold the + or - down, not tap it one time for each increment. Same with the wheel, I'd roll it fast enough to match closely with the speed of holding a button down.

[Gambini]

Forge, on Apr 18 2010, 09:00 PM, said:

Since it's random I have no idea how to "make" it crash. The only consistency I noticed was it usually occurred when I was going from zero to something between 16 and 26. I'd hold the + or - down, not tap it one time for each increment. Same with the wheel, I'd roll it fast enough to match closely with the speed of holding a button down.

The same rule applies to panning textures. It happens when you hold the key until it starts moving fast.

[Stabs]

the other option is to use " ' + s " and enter shade values manually once you have done it with one texture press tab on it and copy its shade only to other surfaces via LENTER+Shift which will paste shade and pal to the selected wall

[Forge]

I think what may be happening is changing the shade or texture too fast or too much causes the fps to drop dramatically for some reason and results in a crash or a freeze.

My processor may not be the best, 2.0 mhz dual core & winxp 64bit, but I have four gigs ram and a 9800 gtx video card that should be able to handle mapster's demands.

[The Commander]

I have only been getting Mapster crashes if I try to run it in full screen mode.
2D mode works fine full screen, but 3D does not.

[Roma Loom]

same here, after several 2d-3d switching in fullscreen makes mapster32 crash, at least on ATI HD4330, I'd check how it goes on GF9600 at the office tomorrow.

[Gambini]

From the time i bought a widescreen monitor i began to use mapster in windowed mode, it works Waaaay better and more stable this way. Before it used to crash a lot more and to delete the desktop icons.

[The Commander]

I have always used Mapster in windowed mode at 800 x 600. (I still have an old cheap CRT so don't say shit about low res)
I was just reporting that it does crash in full screen mode, not that I would use it.

[Forge]

It is more stable in windowed mode, but it still randomly crashes. Just less often.

[Mark]

Same here. More stable in windowed mode. It crashes way more often if rendermode=4 so I set it to 3. I lose the ability to see the polymer lighting but I cut down the frequency of crashes by about 75%. I set it back to 4 only when I am actually placing and adjusting some light effects. Then its right back to 3.