[Stabs]

 Helixhorned, on 28 April 2011 - 12:28 PM, said:

Just a bit patience . How does LEBuild handle that feature in not so clear-cut cases, for example when a sloped ceiling/floor intersects the z limit? After all, it's not only the drawing that needs to be modfied, but certain editing operations should then also be impossible on the invisible portions of the map.

I think it just draws by wall instead of sector, not sure about that mathy x yz stuff craig would best to ask in that regard

[Jan Satcitananda]

 DanM, on 28 April 2011 - 02:33 PM, said:

I think it just draws by wall instead of sector, not sure about that mathy x yz stuff craig would best to ask in that regard

In regard to the Z-range, the sector slopes are ignored as it's usually sufficient to consider floorz/ceilingz parameters to decide whether a sector is belonging to the range selected. Cutting sloped sectors precisely would make things way too complicated...

[Helixhorned]

Well, you might want to try out the feature now. Instructions are in the commit log. As Lezing remarked, slopes would complicate matters even more, so only the sector[].{ceiling,floor}z values are taken into account.

[Forge]

r1877
32bit (works in 8 bit fine)
Polymost
windowed

Nvidia GeForce 9800 GTX+
Driver 270.61
512 MB GDDR3

OpenGL Information:
Version: 3.3.0
Vendor: NVIDIA Corporation
Renderer: GeForce 9800 GTX+/PCI/SSE2

the screen is also blurry in addition to the mouse trails, but print-screen doesn't capture it (still)

since I seem to be the only one having this issue, do you think it might be a directdraw problem? I believe this windows 7 machine came stock with directx11, but I had to install directx9c because of other non-related program errors

Dxdiag still says the directx version is 11


also: why is a _crash.map generated every time mapster is exited from 3d mode? (no error boxes appear, but the mapster.log generates a Fatal Signal caught: SIGSEGV. Bailing out message)

[Stabs]

 Helixhorned, on 07 May 2011 - 10:39 AM, said:

Well, you might want to try out the feature now. Instructions are in the commit log. As Lezing remarked, slopes would complicate matters even more, so only the sector[].{ceiling,floor}z values are taken into account.

thanks so much for that helix, I just tried it and while it may not be as functional as LeBUILDs i am sure it will be in time

[VinsaneOne]

 Forge, on 07 May 2011 - 01:36 PM, said:

r1877
32bit (works in 8 bit fine)
Polymost
windowed

Nvidia GeForce 9800 GTX+
Driver 270.61
512 MB GDDR3

OpenGL Information:
Version: 3.3.0
Vendor: NVIDIA Corporation
Renderer: GeForce 9800 GTX+/PCI/SSE2

the screen is also blurry in addition to the mouse trails, but print-screen doesn't capture it (still)

since I seem to be the only one having this issue, do you think it might be a directdraw problem? I believe this windows 7 machine came stock with directx11, but I had to install directx9c because of other non-related program errors

Dxdiag still says the directx version is 11


also: why is a _crash.map generated every time mapster is exited from 3d mode? (no error boxes appear, but the mapster.log generates a Fatal Signal caught: SIGSEGV. Bailing out message)

SFAIK, installing an older version of DX over a newer one don't work. You must have either an older version to overwrite/upgrade, or none at all.

[Forge]

SFAIK that wasn't helpful or informative

but FYI I installed directx9c sdk and dxdiag still reported version 11

[Gambini]

Dxdiag reports DX11 because you have a mess with files. VinsaneOne´s post is helpfull because it helps you to realize that your setup is fucked up and is bound to cause problems.

What I would do is try to uninstall all DirectX stuff if it´s possible, and reinstall DX11.

[Forge]

Gambini, on 08 May 2011 - 12:50 PM, said:

Dxdiag reports DX11 because you have a mess with files. VinsaneOne´s post is helpfull because it helps you to realize that your setup is fucked up and is bound to cause problems.

What I would do is try to uninstall all DirectX stuff if it´s possible, and reinstall DX11.

Telling me I can't do something I already did is not very helpful. I'm fully aware that there might be a problem with DirectX, or I wouldn't have mentioned it. Mapster works fine with r1853 and before. I'm wondering if DirectX is causing the issues with later snapshots. From what I've read, nVidea cards are not DirectX 11 compliant, but I mentioned what I did in case the powers that be might recognize what the issue is.
DirectX 11 is not available for download yet ( and isn't un-installible) and DirectX 9c SDK is stand alone, so it didn't mess with the DX 11 drivers as far as I can tell (at least dxdiag is reporting no problems)

[Forge]

I got this off some computer geek website:

"Yes, you can install DirectX 9 with no problems. The files already present in DirectX 11 are not replaced but only missing files are installed. "

use the webinstaller version of directx 9c and it will check your system files. It will either install the missing files or inform the user that all files are newer and up to date and no installation is needed (which is what it does now when I run it)

[Helixhorned]

Forge, on 07 May 2011 - 01:36 PM, said:

also: why is a _crash.map generated every time mapster is exited from 3d mode? (no error boxes appear, but the mapster.log generates a Fatal Signal caught: SIGSEGV. Bailing out message)

Dunno, that's one thing I'm not getting either. Anything specific that triggers it, or is it every time you quit through 3D?

[Forge]

Helixhorned, on 09 May 2011 - 02:09 AM, said:

Dunno, that's one thing I'm not getting either. Anything specific that triggers it, or is it every time you quit through 3D?

Every time I quit through 3D.

I've tried rolling back my video driver
I've tried a clean install
the only two non-native files in the build folder is the duke3d.grp and tiles.cfg
I've tried removing the tiles.cfg file

the problem still occurs

I do not get a _crash.map when exiting 3D mode when using the mapster.debug, but I still have the visual problems with the tile selection screen

[Forge]

What are the functions of these files?

nedmalloc.dll
backtrace.dll
libiconv2.dll
libintl3.dll

When I remove them from the build directory, the texture selection screen still has mouse trails, but I can actually see the tiles instead of a blurry screen (it still blurs some when I scroll, but it's usable)

I removed them and re-added them one by one and found that the _crash.map is only generated when the nedmalloc.dll is present in the build directory

[Mike Norvak]

I think i have the same problem in tile selection.

I read in other threats but i don't found a clear reply, i hadn't realized because i was mapping for WGR so far that comes with r1848 ( and no probs with that revision)

[Forge]

Norvak, on 09 May 2011 - 08:47 PM, said:

I think i have the same problem in tile selection.

I read in other threats but i don't found a clear reply, i hadn't realized because i was mapping for WGR so far that comes with r1848 ( and no probs with that revision)

r1853 will work with no problems, or map in 8 bit

[bullerbullerseven]

When i zoom in, in 2d mode mapster32 crashes. Will post log later.

[Helixhorned]

Forge, on 09 May 2011 - 04:26 AM, said:

What are the functions of these files?

nedmalloc.dll
backtrace.dll
libiconv2.dll
libintl3.dll

http://forums.duke4....dpost__p__81120

[fgsfds]

This happens when I often press ctrl+z to undo changes.

Attached thumbnail(s)

• 

[Forge]

empy, on 12 May 2011 - 01:20 PM, said:

This happens when I often press ctrl+z to undo changes.

try "esc" then "u"

[Gambini]

Helixhorned, on 11 May 2011 - 02:24 PM, said:

http://forums.duke4....dpost__p__81120

So that means i can delete them all in simple instalations that wont use debug executables?

[TerminX]

I would keep nedmalloc.dll around since it's used by the non-debug executables, but otherwise yes the rest of them can be removed.

[Gambini]

Great. thanks!

[Plagman]

Yeah, you can delete all of them is you wish; however nedmalloc.dll is supposed to boost loading times, it's not only for the debug executable.

[Helixhorned]

Forge, on 10 May 2011 - 03:56 AM, said:

r1853 will work with no problems, or map in 8 bit

How about the recent revision?

[Forge]

Helixhorned, on 15 May 2011 - 03:20 PM, said:

How about the recent revision?

no change with r1888. still blurry and un-useable texture screen with mouse trails on 32 bit

[Forge]

no change with r1889

[Helixhorned]

OK, r1890 adds an option 'lazytileselector' to the cfg. If disabling it here doesn't fix it, I don't know what will.

[Forge]

Helixhorned, on 18 May 2011 - 03:06 PM, said:

OK, r1890 adds an option 'lazytileselector' to the cfg. If disabling it here doesn't fix it, I don't know what will.

r1890.

lazytileselector = 0

works like a charm

you da man

[Mike Norvak]

Thanks Helixhorned!!!

[Micky C]

Mapster32 crashed twice when I was editing a map today, so the third time I used mapster32.debug.exe and surely enough it crashed again and produced a crashlog.

It's fairly short so forgive me for not using pastebin or attaching it.

0x4e9db6 : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : Z:\var\www\synthesis\eduke32\eduke32\build/src/quicklz.
c (695) : in function (qlz_decompress_core) 
0x4e9fec : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : Z:\var\www\synthesis\eduke32\eduke32\build/src/quicklz.
c (826) : in function (qlz_decompress) 
0x40220c : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : Z:\var\www\synthesis\eduke32\eduke32/source/astub.c (465) : in function (map_undoredo) 
0x41b0d9 : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : Z:\var\www\synthesis\eduke32\eduke32/source/astub.c (6699) : in function (Keys2d) 
0x423ccc : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : Z:\var\www\synthesis\eduke32\eduke32/source/astub.c (9853) : in function (ExtCheckKeys) 
0x447701 : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : Z:\var\www\synthesis\eduke32\eduke32\build/src/build.
c (1854) : in function (overheadeditor) 
0x444a11 : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : Z:\var\www\synthesis\eduke32\eduke32\build/src/build.
c (1223) : in function (editinput) 
0x423cb4 : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : Z:\var\www\synthesis\eduke32\eduke32/source/astub.c (9850) : in function (ExtCheckKeys) 
0x442a89 : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : Z:\var\www\synthesis\eduke32\eduke32\build/src/build.
c (584) : in function (app_main) 
0x4d0f1c : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : Z:\var\www\synthesis\eduke32\eduke32\build/src/winlayer.
c (494) : in function (WinMain@16) 
0x5253a6 : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : main.c 
0x4010db : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : crt1.c 
0x401158 : C:\Users\Alan\Desktop\Duke Nukem\mapster32.debug.exe : crt1.c 
Failed to init bfd from (C:\Windows\syswow64\kernel32.dll)
0x75bd3677 : C:\Windows\syswow64\kernel32.dll : BaseThreadInitThunk 
Failed to init bfd from (C:\Windows\SysWOW64\ntdll.dll)
0x772c9d42 : C:\Windows\SysWOW64\ntdll.dll : RtlInitializeExceptionChain 
Failed to init bfd from (C:\Windows\SysWOW64\ntdll.dll)
0x772c9d15 : C:\Windows\SysWOW64\ntdll.dll : RtlInitializeExceptionChain