---

Uh, is it just me, or does this version seem to crash more often than 10.20 does?

---

---

Got that email from "nobody" address from the above (must be if they reply from here), but that address can't be replied to.

Anyway, my guess is that they are drawing lines that exceed the DOOM coordinate values of +/-32k. The lines are 4000+units but that's not a problem (Lut has 7000+ lines in his level). IOW, if you start drawing at coordinate x=32000, y=0 and extend to X=36000, y=0 you have just overflowed the maximum value.

Internally, most things in DeePsea don't care about this, but there may be some places where an 2 byte coordinate value is used. For sure the final PWADt saved has to use the actual size (values) as used by DOOM, in which case the level will not work and/or the nodes will turn to mush.

So if you could please send me the level I can see what you are doing.

---

---

Ok - I'll check the levels. In my testing, the long lines don't cause any problem to DeePsea. Overflow just flips directions. However, it -MAY- be an issue with your video driver. It's not the first time a video driver has caused problems. So be sure to get the latest driver(s) (ATI has been notorious in this regard.)

---

---

DeePsea clips long lines when zoomed (since Windows will otherwise not draw them - (a 16 bit windows api problem), but there is some overdrawing beyond the actual screen boundaries to make sure they always show up (edge-to-edge).

The 32k line will REALLY cause an issue and won't work. You have to break that one up. Long lines are not a good idea since it brings out drawing and other problems in DOOM (see below).

The longest line should be around 8k. Longer than this and you will also run into BLOCKMAP size problems. Typically, the maximum level dimensions are 16k x 16k and more like 12k x 12k with any amount of detail inside (assuming you are running a newer port that can handle a 128k blockmap - otherwise it's about 1/2 that).

---

---

I'm interested in seeing what your startup modules are via MSCONFIG. Also press ctrl+alt+del and tell me what tasks are running. Also what exactly is the error message you are getting?

---

---

Did you play test any of the ports and then edit? Some of the ports will mess up your system after you play them - especially if the large blockmap is not supported:)

---

---

What happens from a clean boot: NO other programs have run (no IE, no email, IOW nothing) and NO DOOM testing. If you have anti-virus software, temporarily turn it off too.

11.3 is 11.2 with an integrated linedef dialog for faster editing. Other than that, the code is the same. There's always the possiblity you did something I'm not thinking of and need to make allowance for:)

Thanks

---

---

That's an idea - aside from that the newer ATI drivers for my video setup are LESS stable than the older ones. Dunno why.

---

---

Never had a chance to playtest it, aside from with ZDoom, and I usually quit DeepSea first. Go figure.

---

---

Haven't had a chance to try a clean boot - and there's a fair number of things that come up even with a clean standard boot

---

---

Deep sucks badly. Plain and simple.

---

---

The values are 4001 - 4004 in the BOOM, ZDOOM, ZDOOMHEXEN, SKULLTAG, ETERNITY, EDGE & LEGACY default projects as shipped.

---

---

One thing I noticed that was strange was that the first category appears under "enemies" in the middle of the list,

---

---

To keep the OPT file simpler (meaning I didn't have to delete a bunch of existing entries), that "hole" is there so a new ZDOOM/HEXEN category -Specials- appeared where I wanted it. IOW, the first new category always appears there:)

---