Neo - A WoW Development Suite

[Kadzhamit]

You can compile the software with Visual Studio 2013 now.

Awesome, I tested it a moment ago and it runs really smooth so far! And that's on a 7 year old i7 920 and a 4 year old Radeon HD 6950.

Cool! Tell me how to run the program please?)

[Marlamin]

You can compile the software with Visual Studio 2013 now.

Awesome, I tested it a moment ago and it runs really smooth so far! And that's on a 7 year old i7 920 and a 4 year old Radeon HD 6950.

Cool! Tell me how to run the program please?)

It's not ready for real release yet as Cromon and others have said but if you want a quick preview to how fast this project is progressing you can download Visual Studio 2013 for free (and legal!) here and grab the latest zip of the project here open the solution and press F5.

If you have issues following these instructions you should probably wait for a release.

[MountainLion]

The new name is fine. Neo fits great to what it's living up to be and what it'll become. Also patience, let the one walk it's path.... NeoDev :?:   :lol:

[Valkryst]

Just did a quick compile to take a look around.

Everything seems to work fine, there were no issues or lag. It took me a while to figure out how to get into the menu to select whether I wanted to raise/lower terrain, paint on the terrain, etc... and after I found the menu it was no problem to edit with although I still can't figure out how to lower terrain.

Tested using Windows 8.1 x64.

[Kaev]

Just did a quick compile to take a look around.

Everything seems to work fine, there were no issues or lag. It took me a while to figure out how to get into the menu to select whether I wanted to raise/lower terrain, paint on the terrain, etc... and after I found the menu it was no problem to edit with although I still can't figure out how to lower terrain.

Tested using Windows 8.1 x64.

Can't test it right now, but if i remember right, Shift or CTRL will always do the opposite of the normal function, e.g. instead of make the terrain higher, it will lower it.

[TheBuG]

Just did a quick compile to take a look around.

Everything seems to work fine, there were no issues or lag. It took me a while to figure out how to get into the menu to select whether I wanted to raise/lower terrain, paint on the terrain, etc... and after I found the menu it was no problem to edit with although I still can't figure out how to lower terrain.

Tested using Windows 8.1 x64.

Can't test it right now, but if i remember right, Shift or CTRL will always do the opposite of the normal function, e.g. instead of make the terrain higher, it will lower it.

You don't really point and click with the function, you simply press eithe Shift or CTRL to use the function. The mouse pointer is just to aim at the moment it seems. That said, you can customize your keybinds already!

[Cromon]

Today we hade quite a few updates. To show some of the neater ones:

MCLV and MCSH are now displayed correctly. MCLV is additive lighting as you can see near the brazier inside the brush, MCSH is the predefined shadows for example near the trees.


M2 models are now properly positioned and animated all around the world.

All of the old UI and some new stuff like the log is now integrated into the docking ui

The appropriate flags get set in the wdt if you enable vertex shading.

aaand my personal favorite: The brush now features anti-aliasing and animation, see:
https://www.dropbox.com/s/kiohi23xt5ssn ... 4.mp4?dl=0

[phantomx]

Loving the progress and innovation.

[majorcyto]

Wow great job so far, was able to compile and use it without any issue. Was able to raise and lower terrain in a WoD map. Im guessing other than the shading feature, that there is not much else available just yet right? (Not to sound ungrateful, great progress so far!!) Just want to make sure im not missing anything, such as object selecting/placing/rotating i don't seem to see a way to do that just yet, or for instance creating a map from scratch and applying textures.

Keep up the great work, im happy that someone is working on a new editor its already so smooth!


===========

Edit - This vertex shading is fun! Also, im in absolute love that i can separate the sculpting tool into a floating dock that can float OUTSIDE its window. I have triple monitors.. and this is perfect. Im in love lol.

Edit 2 - Even editing at 2560x1440 Resolution works really smooth:!:  :!:

Edit 3 - Tunnels are weird lol, If something is supposed to be a tunnel the ground covers the entrance to the tunnel but the camera can fly through it and the tunnel is still there its just the terrain texture goes over the doorway. :O

Edit 4 - The "Assign Keyboard Shortcuts" button in the sculpting dock doesn't seem to do anything for me.


---------------------
Hope To See List |
---------------------/

Undo / Redo Options for the future
Better Terrain Texturing Options like actual Wow Edit (Cant they do 6 layers now i thought?)
A way to get back to the map select list without closing Neo completely and re-opening.
A way for it to remember my options? It doesnt seem to remember that i uncheck Invert Axis on the camera.  
Proper water support when editing/adding and doing so from within Neo. <3

-------------------

I mean there is more.. but from a technical stand point those are quality of life things i see being important. Aside from the obvious things like supporting the rest of the functions needed in actually viewing the map itself.

[Kaev]

Edit - This vertex shading is fun! Also, im in absolute love that i can separate the sculpting tool into a floating dock that can float OUTSIDE its window. I have triple monitors.. and this is perfect. Im in love lol.

Yeah, our plans for the UI is, that you can move every window/tab/whatever to the place where you want and work from there. So you can work with multiple monitors. Afaik Steff even plans to make it usable for Tablets. And what team projects would love to see: Some sort for team functions like someone is editing a map and it gets locked for everyone else while he's doing it. (Sounds kinda like an SVN repository with lock function o: )

Edit 3 - Tunnels are weird lol, If something is supposed to be a tunnel the ground covers the entrance to the tunnel but the camera can fly through it and the tunnel is still there its just the terrain texture goes over the doorway. :O

Afaik holes aren't implemented yet, that's why you see the normal terrain texture.

---------------------
Hope To See List |
---------------------/

Undo / Redo Options for the future
Better Terrain Texturing Options like actual Wow Edit (Cant they do 6 layers now i thought?)
A way to get back to the map select list without closing Neo completely and re-opening.
A way for it to remember my options? It doesnt seem to remember that i uncheck Invert Axis on the camera.  
Proper water support when editing/adding and doing so from within Neo. <3

Not sure if WoD maps can have 6 textures, but WotLk supports only 4. Atleast i never heard that before, thanks for the information!
Everything else you mentioned is already planned.

[majorcyto]

Hmm, i can't remember where i read about the 6 texture layer thing either though so for the sake of it unless someone else can confirm lets just discredit my statement and assume its 4 still lol.

Glad to hear about the other options, i actually have a Surface Pro 3 as well that comes with the N-Trig pen (very similar to Wacom) and i would love to be able to use it to "paint" textures. The SP3 supports most of the Pen API's as far as i know except for Wacom specific ones.

Edit - The team functions would be very much welcome!

[Steff]

I have 2 days time this weekend and will get a gfx tablet tomorrow. So i can implement my basic UI ideas and try if all also fits to tablet input.

First I will implement the basic project managment parts. To open a new project, load one. Implement the application settings and the file and project view. Then integrate the map editor as first possible editor.

The editing of ground has only rais up implemented jet. So lower simple dont work. In the moment the main focus ist planing how all should work out and cromon gives 200% to implement all the wow data stuff and rendering properly.

[majorcyto]

I have 2 days time this weekend and will get a gfx tablet tomorrow. So i can implement my basic UI ideas and try if all also fits to tablet input.

First I will implement the basic project managment parts. To open a new project, load one. Implement the application settings and the file and project view. Then integrate the map editor as first possible editor.

The editing of ground has only rais up implemented jet. So lower simple dont work. In the moment the main focus ist planing how all should work out and cromon gives 200% to implement all the wow data stuff and rendering properly.

Ok, that sounds good! The Surface Pro 3 pen actually has 2 triggers on the pen itself that can be used, and I know the Wacom pens usually have at least 2 as well, so there might be a way to implement for instance raise and lower into the triggers of the pens themselves, Of course this could be done at a later time and wouldn't need to be researched right away.

The main thing is to have a UI format that's easy to use with a mouse, or a drawing pen. (Or implement a second UI mode in the settings for pen mode.) One thing you might want to look into is the general WinTab API the drivers are available on the surface series, and I think Wacom as a generate interface for pens. You can do some special detection methods, such as for instance.. when the pen is being used on the screen ignore the palm/hand input. So you can use the pen across the screen without accidently activating other buttons.

Anyways some of these things are kinda more specialized and I would understand if they weren't looked at or implemented I am just throwing the ideas out there in general. General Pen Support would be just as nice.

------

Going back to team features for a minute, it would be cool if we could some how have synced multi-map editing. All though the logistics of making sure the map chunks don't corrupt between the wow edit clients would be problematic, just the locking of the map at least (and showing it locked) would for sure be a massive helpful feature. But I have seen a few editors allow up to 8 people to edit or change the same map. But then you would have to have something like a sync-server that the user would need to run for their team to make sure the data and editor positions stay up to date.

Anyways, just talking at this point. I haven't actually used the NEO WoW Edit tool on my surface pro 3 yet, only on my beefy desktop I will download VS 2015 today on my Surface and try it out and let you know its performance. It will probably be fine though.

Keep up the good work.  

[Kaev]

I have 2 days time this weekend and will get a gfx tablet tomorrow. So i can implement my basic UI ideas and try if all also fits to tablet input.

First I will implement the basic project managment parts. To open a new project, load one. Implement the application settings and the file and project view. Then integrate the map editor as first possible editor.

The editing of ground has only rais up implemented jet. So lower simple dont work. In the moment the main focus ist planing how all should work out and cromon gives 200% to implement all the wow data stuff and rendering properly.

Ok, that sounds good! The Surface Pro 3 pen actually has 2 triggers on the pen itself that can be used, and I know the Wacom pens usually have at least 2 as well, so there might be a way to implement for instance raise and lower into the triggers of the pens themselves, Of course this could be done at a later time and wouldn't need to be researched right away.

The main thing is to have a UI format that's easy to use with a mouse, or a drawing pen. (Or implement a second UI mode in the settings for pen mode.) One thing you might want to look into is the general WinTab API the drivers are available on the surface series, and I think Wacom as a generate interface for pens. You can do some special detection methods, such as for instance.. when the pen is being used on the screen ignore the palm/hand input. So you can use the pen across the screen without accidently activating other buttons.

Anyways some of these things are kinda more specialized and I would understand if they weren't looked at or implemented I am just throwing the ideas out there in general. General Pen Support would be just as nice.

------

Going back to team features for a minute, it would be cool if we could some how have synced multi-map editing. All though the logistics of making sure the map chunks don't corrupt between the wow edit clients would be problematic, just the locking of the map at least (and showing it locked) would for sure be a massive helpful feature. But I have seen a few editors allow up to 8 people to edit or change the same map. But then you would have to have something like a sync-server that the user would need to run for their team to make sure the data and editor positions stay up to date.

Anyways, just talking at this point. I haven't actually used the NEO WoW Edit tool on my surface pro 3 yet, only on my beefy desktop I will download VS 2015 today on my Surface and try it out and let you know its performance. It will probably be fine though.

Keep up the good work.  

Don't forget that you don't need VS 2015 anymore. 2013 will work too.

[stoneharry]

Just compiled it to take a look at it, my thoughts:

• The text on the left tabs looks blurred (see here: http://i.imgur.com/4K6R5ip.png )
• The text on the welcome screen should be in column(s), not wide screen. It is very hard to read text that goes across the entire screen.
• If you close the tabs on the left by opening them then pressing the 'x', I could not see a way to bring them back without restarting the app.
• When I pressed on Scott Test the program became very slow, almost not responding, and tested all ADTs. This should not happen, some sort of verification to see if this will happen and warn the user and say do they want to proceed, or something.
• Loading screen was very nice, making it fit the full window would be better.
• The default key bindings are intuitive. I didn't need to look them up.
• Holding down some key to move faster would be nice.
• Square brush or circle brush would be handy (I don't know if this is how they do post-wotlk mountains).
• Tooltips on the different algorithm types would be handy.
• The title of the application needs to be updated from WoWDev to Neo.
• There is no way to return to map selection.
• The icon for each map should be it's minimap if feasible.

I realise this is still early stages but these were my initial thoughts.