This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Scytheria23
1
« on: March 13, 2017, 06:33:22 am »
@Insanity
The project is still in development, somewhat slowed by my real life workload. At present, a volunteer is beta-testing some of the main features, but the whole thing is a way off completion.
I'm afraid I don't have any copies of the original tool, but trust me, it was crapola.
Scy
2
« on: March 02, 2017, 12:58:09 pm »
For a fleeting moment, after 3.3.5a and before Deathwing did his thing, the old world (Azeroth/Kalimdor) used the old maps (as found in 3.3.5a). Does anybody know if these maps are (1) obtainable and (2) useable in 4.3.4? Is there a way, for example, to patch a 3.3.5a client to turn it into a 4.0.1 client and pull out the maps manually?
Any help appreciated
Scy
3
« on: January 19, 2017, 10:54:07 pm »
Thanks for the suggestions. Indeed, the situation described is what I'm aiming for (using just the exterior geometry of some WMOs to fast-build lots of walls, walkways, etc). I think, on balance, custom M2s are the answer.
Scy
4
« on: January 18, 2017, 11:30:55 pm »
Thanks for the fast reply. OK, but I guess it's possible to convert a WMO into an M2... essentially all the needed data will be in there. I'll look into an automated way of doing this when my current project is done.
5
« on: January 18, 2017, 10:12:58 pm »
Probably a stupid question,
I know you can easily make the client spawn WMOs as if they were M2s (Amaroth's pack allows you to do this well enough) but can you spawn WMOs in Noggit in the same way? I would like to be able to scale, rotate and otherwise transform WMOs, but Noggit only seems to allow these actions to be performed on M2 objects.
Any easy answer?
Thanks
Scy
6
« on: December 08, 2016, 03:59:33 am »
@ Skarn
As much as possible is already multithreaded, but the problem is that most operations cannot run in parallel, each being totally dependent on the result of the last. The issue is simply one of bytes. One ADT requires 37120 floating point heights, 4194302 bytes of alphamap information, other data besides. For 12x12 ADTs this came to over 625 million bytes being manipulated or stored for each layer of work (I had five per ADT). Few machines can cope with that.
I am working on a code cleanup, which is freeing quite a lot of memory, some compression of data, moving a few routines around, and this is all helping. I don't think I'll get back to 12x12, but 8x8 is working well and quickly.
7
« on: December 05, 2016, 01:25:25 am »
 Ok, some success with alphamap support, but there is a major snag... The immense quantity of data held by the tool for 12x12 ADTS (4.8 million heights per ADT, 4 million alpha values, AreaIDs, GroundEffects, etc) has resulted in a very slow tool that only works on high-spec machines. Even with a monster PC, it grinds to a crawl. As such, I have been forced to reduce the map size to a more manageable 4x4 ADTS (one ninth of the original area). Of course, it will remain possible to tile multiple sets of 4x4 to make larger maps (although there may be seam problems between maps if heights are not carefully managed), but the working area had to be scaled down. Edit: OK, got it back up to 8x8, which is much more useful. I did this by reducing the 'undo' steps to just one (the last operation) and by squeezing some data that was stored in multiple integers as flags (a single byte).
8
« on: December 01, 2016, 04:48:04 am »
Bumping because of big edit to the first post
9
« on: November 24, 2016, 09:50:21 pm »
Is there any way this tool may get alphamap support any time in the future. As in, to create a base alphamap which would be copied over all ADTs. The answer is kind-of. The base-layer textures, yes. You're about two weeks away from seeing a MAJOR overhaul of this tool. The new version, now renamed ADTForge, has a proper Windows interface, many more tools, and is flexible (e.g. you can add as many layers of height info in whatever ways you want). You can set the primary layer textures, set AreaIDs, impassible flags, animate the textures, do cube-maps, add ground effects and so on. You can also rip height info from existing ADTs, manipulate it, and merge it into your own height data. I'm now in the final testing phase and writing the manual/tutorials. Watch this space! Scy
10
« on: November 03, 2016, 02:20:25 am »
@ Songen
Good to hear. Do give feedback on your results (pics would be nice). If you think something could be improved or think of a missing feature, there's still time for me to fix/add into the more substantial sequel.
11
« on: November 02, 2016, 11:15:35 pm »
@ Songen
Most likely cause is wrong kind of bitmap. They MUST be 1537*1537 greyscale with .bmp suffix. Check exact size of your file. It should be identical to that of the examples. My guess is that you have edited them and then saved without making sure they are the correct type. Gimp (which is free) will save in the correct format. Just select Image > Mode > Greyscale and export with .bmp, refusing any offer to add transparency. Resulting file should be exactly 2,368,126 bytes. I'm afraid I'm not likely to improve the app by allowing different file formats or sizes - it's too much fuss when these things can be done by the users.
12
« on: October 30, 2016, 10:20:48 pm »
@ Sinkhile: I'm not sure I could explain it on YouTube any better than the coverage in the documentation. Which part is giving you trouble?
I'm currently building a second version of the app, which will offer a lot more flexibility and power. That, however, comes with a cost - it's considerably more difficult to use. You'll be able to apply as many masks as you like, manipulating each in whatever ways you want. This will allow you to add successive layers of fine detail to the terrain, and give much greater control over the output. Because it's much harder to use (you have to specify the operations and their order in a special scripting language), I'll certainly come up with a few user-guide videos.
BTW, the 'promised' auto-texturing is a dead end. Although some preliminary trials gave reasonable results, they were no substitute for painting by hand in Noggit. The effort needed to set up the auto-texturing was substantially greater than that needed to wave a mouse around in Noggit, so the tool would be kind of redundant. The human touch is often better.
Scy
13
« on: October 27, 2016, 02:21:03 pm »
ADT Guru v1.2 RELEASE!This will be the last release for a while unless a major bug is found. I'm spent. Added a third user mode. When you generate the procedural terrain, it is dumped as a raw data file (dump.txt) into the output folder. If you choose user mode 2, this is read instead of running through the lengthy generation routine. This saves a hell of a lot of time when testing masks.
Added a trap in the main generation routine that exits when the terrain is completed, even if this happens before the cycle ends. This seldom happens, but it’s a nice surprise when it does.
Added an additional output bitmap – renderview.bmp – which shows the terrain in a (very) rough 3D view. It’s aligned south to north along the x axis (yeah, I know), and heights are grossly exaggerated to make them more visible.
Fixed the file pathing issues. ADT Guru now runs wherever you put it as long as the folders are kept the same and not renamed.
Fixed the anomalous wall around the edge of some maps.
Fixed the scaleup routine, which now behaves properly and doesn’t create silly columns.
Changed the order in which scaleup/scaledown and elevate occur, making it easier to predict the heights and position of generated terrain. Scy
14
« on: October 26, 2016, 03:52:19 pm »
Version 1.2 imminent. Sorry about the rapid update rate. Sharing is the best way to identify bugs. Thanks for the PMs. - fixed anomalous walls around edges of map when elevate used - fixed scaleup and scaledown so they behave as described (e.g. Properly) - fixed scaling and elevating order to make it easier to predict final heights - added function to dump and import terrain data as a binary file, so masks can be used without having to generate it all over again No joy solving the install path thing  Coming very soon Scy
15
« on: October 25, 2016, 11:40:10 pm »
@ Nupper
Have you placed the ADT Guru folder directly onto your C drive? Have you renamed any folders? ADT Guru will not work if you put the folder anywhere else or rename the folders.
Path should be: c:/ADT Guru/ADT Guru v1.1.exe
|
Show Posts