Forums WoW Modding Discussion Level Design [Archive] A bit in a struggle here.

[Archive] A bit in a struggle here.

[Archive] A bit in a struggle here.

Pages (2): 1 2 Next
rektbyfaith
Administrator
0
11-26-2015, 02:43 PM
#1
Archived author: Poisonleaf • Posted: 2015-11-26T14:43:56+00:00
Original source

Hiya,

So for the past couple of weeks/months I'v been trying to alter Nagrand in a way that I find it fitting it would look like after the Burning legion was defeated. Meaning bring it back to the state of beauty it once was.

Now the texturing and all goes fine. I get to edit all the texture I want, Re add the water or recreate it. That all works fine.
The problem starts when I want to go ahead and start with adding Objects in the form of WMo's or m2's.

Than stuff goes missing that was originally in the map like waterfalls and rocks etc.
There some parts that just have huge lag and i'm unable to move, Not even trying to work there.
There also some original objects that are spawned 20 times ontop of eachother not sure whats the deal with that.
I had it before but than I redo the whole thing with the following tip.

Amaroth gave me the tip on Modcraft to only save once every noggit launch and that's what I'm doing but still these things are occurring.

So now I've been thinking to do this a whole other way.
Ill leave the map how it it with the missing tree's and rocks since it's still in an okay state.

Ill finish Nagrand in noggit pure on texture and water, preparing it for objects.
Ill than patch it and work on it In-game with adding all the objects
(I think i've seen somewhere that you can patch your game and add (any) objects to spawn in-game)

Once that is finished I will go back to noggit and finish it off with the roads and some minor texture work.

Is that something that could work or what do you guys propose?

At this point any help or advice is welcome.
Poisonleaf

Edited November 26, 2015 by Poisonleaf
rektbyfaith
11-26-2015, 02:43 PM #1

Archived author: Poisonleaf • Posted: 2015-11-26T14:43:56+00:00
Original source

Hiya,

So for the past couple of weeks/months I'v been trying to alter Nagrand in a way that I find it fitting it would look like after the Burning legion was defeated. Meaning bring it back to the state of beauty it once was.

Now the texturing and all goes fine. I get to edit all the texture I want, Re add the water or recreate it. That all works fine.
The problem starts when I want to go ahead and start with adding Objects in the form of WMo's or m2's.

Than stuff goes missing that was originally in the map like waterfalls and rocks etc.
There some parts that just have huge lag and i'm unable to move, Not even trying to work there.
There also some original objects that are spawned 20 times ontop of eachother not sure whats the deal with that.
I had it before but than I redo the whole thing with the following tip.

Amaroth gave me the tip on Modcraft to only save once every noggit launch and that's what I'm doing but still these things are occurring.

So now I've been thinking to do this a whole other way.
Ill leave the map how it it with the missing tree's and rocks since it's still in an okay state.

Ill finish Nagrand in noggit pure on texture and water, preparing it for objects.
Ill than patch it and work on it In-game with adding all the objects
(I think i've seen somewhere that you can patch your game and add (any) objects to spawn in-game)

Once that is finished I will go back to noggit and finish it off with the roads and some minor texture work.

Is that something that could work or what do you guys propose?

At this point any help or advice is welcome.
Poisonleaf

Edited November 26, 2015 by Poisonleaf

rektbyfaith
Administrator
0
11-26-2015, 03:19 PM
#2
Archived author: Skarn • Posted: 2015-11-26T15:19:59+00:00
Original source

First of all, what Noggit version do you use? It is very important in finding out the source of a problem.
rektbyfaith
11-26-2015, 03:19 PM #2

Archived author: Skarn • Posted: 2015-11-26T15:19:59+00:00
Original source

First of all, what Noggit version do you use? It is very important in finding out the source of a problem.

rektbyfaith
Administrator
0
11-26-2015, 03:44 PM
#3
Archived author: Amaroth • Posted: 2015-11-26T15:44:50+00:00
Original source

Always restarting noggit after saving is the first thing you need to do, but it applies only to SDL 1.4. And there is also a seond thing you need to keep doing - saving the whole area you are editing together. Which means that you should always make sure before saving that all ADTs your project is containing were edited and will be saved. Things like "now I will edit and save just western Nagrand, tomorrow just northern part"... and so on should not happen, because those make those duplication (and probably also disappearing) bugs happen, too.
rektbyfaith
11-26-2015, 03:44 PM #3

Archived author: Amaroth • Posted: 2015-11-26T15:44:50+00:00
Original source

Always restarting noggit after saving is the first thing you need to do, but it applies only to SDL 1.4. And there is also a seond thing you need to keep doing - saving the whole area you are editing together. Which means that you should always make sure before saving that all ADTs your project is containing were edited and will be saved. Things like "now I will edit and save just western Nagrand, tomorrow just northern part"... and so on should not happen, because those make those duplication (and probably also disappearing) bugs happen, too.

rektbyfaith
Administrator
0
11-26-2015, 05:22 PM
#4
Archived author: Poisonleaf • Posted: 2015-11-26T17:22:37+00:00
Original source

I'm mostly use 1.4. But I did use 1.22 earlier today because it was less lagging than 1.4 for some reason.

 saving the whole area you are editing together. Which means that you should always make sure before saving that all ADTs your project is containing were edited and will be saved. Things like "now I will edit and save just western Nagrand, tomorrow just northern part"... and so on should not happen

Do you mean i have to edit something at a all parts of nagrand every single time i work on it and save it?

Edited November 26, 2015 by Poisonleaf
rektbyfaith
11-26-2015, 05:22 PM #4

Archived author: Poisonleaf • Posted: 2015-11-26T17:22:37+00:00
Original source

I'm mostly use 1.4. But I did use 1.22 earlier today because it was less lagging than 1.4 for some reason.

 saving the whole area you are editing together. Which means that you should always make sure before saving that all ADTs your project is containing were edited and will be saved. Things like "now I will edit and save just western Nagrand, tomorrow just northern part"... and so on should not happen

Do you mean i have to edit something at a all parts of nagrand every single time i work on it and save it?

Edited November 26, 2015 by Poisonleaf

rektbyfaith
Administrator
0
11-29-2015, 04:00 PM
#5
Archived author: Poisonleaf • Posted: 2015-11-29T16:00:56+00:00
Original source

Quote:Always restarting noggit after saving is the first thing you need to do, but it applies only to SDL 1.4. And there is also a seond thing you need to keep doing - saving the whole area you are editing together. Which means that you should always make sure before saving that all ADTs your project is containing were edited and will be saved. Things like "now I will edit and save just western Nagrand, tomorrow just northern part"... and so on should not happen, because those make those duplication (and probably also disappearing) bugs happen, too.
I don't understand, so I have to edit something at all the ADT's inside my project before each save?
rektbyfaith
11-29-2015, 04:00 PM #5

Archived author: Poisonleaf • Posted: 2015-11-29T16:00:56+00:00
Original source

Quote:Always restarting noggit after saving is the first thing you need to do, but it applies only to SDL 1.4. And there is also a seond thing you need to keep doing - saving the whole area you are editing together. Which means that you should always make sure before saving that all ADTs your project is containing were edited and will be saved. Things like "now I will edit and save just western Nagrand, tomorrow just northern part"... and so on should not happen, because those make those duplication (and probably also disappearing) bugs happen, too.
I don't understand, so I have to edit something at all the ADT's inside my project before each save?

rektbyfaith
Administrator
0
11-29-2015, 05:08 PM
#6
Archived author: Amaroth • Posted: 2015-11-29T17:08:40+00:00
Original source

Lets say you want to edit Howling Fjord in Northrend.:

[Image: image.jpg]

So, you open Northrend map, go to Howling Fjord and then you should mark all ADTs you will want to work on as edited by doing whatever in them. You can just click with flatten tool somewhere, or move some object a little bit to do so. When you are done, when all ADTs you will want to mod are edited, you can save. By that way you will mark area you will want to work on. So your Northrend will look somehow like this lets say:
[Image: image.jpg]

And now, EVERYTIME you are working on ANY of these ADTs, you should mark ALL ADTs as edited. So ALWAYS before you save, your Northrend map will look like this.:

[Image: image.jpg]

Do not save your map if all "orange" ADTs are not white-bordered. And always restart Noggit after saving. 2 simple rules - and no there should be no objects which disappear or are duplicated.
rektbyfaith
11-29-2015, 05:08 PM #6

Archived author: Amaroth • Posted: 2015-11-29T17:08:40+00:00
Original source

Lets say you want to edit Howling Fjord in Northrend.:

[Image: image.jpg]

So, you open Northrend map, go to Howling Fjord and then you should mark all ADTs you will want to work on as edited by doing whatever in them. You can just click with flatten tool somewhere, or move some object a little bit to do so. When you are done, when all ADTs you will want to mod are edited, you can save. By that way you will mark area you will want to work on. So your Northrend will look somehow like this lets say:
[Image: image.jpg]

And now, EVERYTIME you are working on ANY of these ADTs, you should mark ALL ADTs as edited. So ALWAYS before you save, your Northrend map will look like this.:

[Image: image.jpg]

Do not save your map if all "orange" ADTs are not white-bordered. And always restart Noggit after saving. 2 simple rules - and no there should be no objects which disappear or are duplicated.

rektbyfaith
Administrator
0
11-29-2015, 05:25 PM
#7
Archived author: Skarn • Posted: 2015-11-29T17:25:40+00:00
Original source

Amaroth, do you mind me copying that to my Noggit FAQ? Because a lot of people have no idea how to get rid of disappearing models.
rektbyfaith
11-29-2015, 05:25 PM #7

Archived author: Skarn • Posted: 2015-11-29T17:25:40+00:00
Original source

Amaroth, do you mind me copying that to my Noggit FAQ? Because a lot of people have no idea how to get rid of disappearing models.

rektbyfaith
Administrator
0
11-29-2015, 09:57 PM
#8
Archived author: Poisonleaf • Posted: 2015-11-29T21:57:25+00:00
Original source

Quote:Amaroth, do you mind me copying that to my Noggit FAQ? Because a lot of people have no idea how to get rid of disappearing models.
You should do that for sure.
Alot of people will need that advice.
Quote:Lets say you want to edit Howling Fjord in Northrend.:

[Image: image.jpg]

So, you open Northrend map, go to Howling Fjord and then you should mark all ADTs you will want to work on as edited by doing whatever in them. You can just click with flatten tool somewhere, or move some object a little bit to do so. When you are done, when all ADTs you will want to mod are edited, you can save. By that way you will mark area you will want to work on. So your Northrend will look somehow like this lets say:
[Image: image.jpg]

And now, EVERYTIME you are working on ANY of these ADTs, you should mark ALL ADTs as edited. So ALWAYS before you save, your Northrend map will look like this.:

[Image: image.jpg]

Do not save your map if all "orange" ADTs are not white-bordered. And always restart Noggit after saving. 2 simple rules - and no there should be no objects which disappear or are duplicated.
Thanks for the advice. This is surely help.

What about the lag on some parts. It's prolly due objects being spawned 10+ times?
Shall I just start over... again?
rektbyfaith
11-29-2015, 09:57 PM #8

Archived author: Poisonleaf • Posted: 2015-11-29T21:57:25+00:00
Original source

Quote:Amaroth, do you mind me copying that to my Noggit FAQ? Because a lot of people have no idea how to get rid of disappearing models.
You should do that for sure.
Alot of people will need that advice.
Quote:Lets say you want to edit Howling Fjord in Northrend.:

[Image: image.jpg]

So, you open Northrend map, go to Howling Fjord and then you should mark all ADTs you will want to work on as edited by doing whatever in them. You can just click with flatten tool somewhere, or move some object a little bit to do so. When you are done, when all ADTs you will want to mod are edited, you can save. By that way you will mark area you will want to work on. So your Northrend will look somehow like this lets say:
[Image: image.jpg]

And now, EVERYTIME you are working on ANY of these ADTs, you should mark ALL ADTs as edited. So ALWAYS before you save, your Northrend map will look like this.:

[Image: image.jpg]

Do not save your map if all "orange" ADTs are not white-bordered. And always restart Noggit after saving. 2 simple rules - and no there should be no objects which disappear or are duplicated.
Thanks for the advice. This is surely help.

What about the lag on some parts. It's prolly due objects being spawned 10+ times?
Shall I just start over... again?

rektbyfaith
Administrator
0
11-29-2015, 10:03 PM
#9
Archived author: Amaroth • Posted: 2015-11-29T22:03:49+00:00
Original source

There might be another reasons for having lags in map edited by Noggit, but mot of them were gone with newere versions of app. Still, duplicated objects are the most common case. If you had about lets say 10000 objects on original ADTs and your duplications turned them into 20000-30000, then yes, you surely will have lags because of that, and quite likely only because of that.

About deleting duplicated objects... SDL 1.4 has in Assist menu function Clear duplicate models. I was told it is slightly bugged and I saw it sometimes clearing also models which were not duplicated, but you can give it a try. Anyway, don't use it more than once on a map.
rektbyfaith
11-29-2015, 10:03 PM #9

Archived author: Amaroth • Posted: 2015-11-29T22:03:49+00:00
Original source

There might be another reasons for having lags in map edited by Noggit, but mot of them were gone with newere versions of app. Still, duplicated objects are the most common case. If you had about lets say 10000 objects on original ADTs and your duplications turned them into 20000-30000, then yes, you surely will have lags because of that, and quite likely only because of that.

About deleting duplicated objects... SDL 1.4 has in Assist menu function Clear duplicate models. I was told it is slightly bugged and I saw it sometimes clearing also models which were not duplicated, but you can give it a try. Anyway, don't use it more than once on a map.

rektbyfaith
Administrator
0
11-30-2015, 01:18 PM
#10
Archived author: Skarn • Posted: 2015-11-30T13:18:40+00:00
Original source

Quote:There might be another reasons for having lags in map edited by Noggit, but mot of them were gone with newere versions of app. Still, duplicated objects are the most common case. If you had about lets say 10000 objects on original ADTs and your duplications turned them into 20000-30000, then yes, you surely will have lags because of that, and quite likely only because of that.

About deleting duplicated objects... SDL 1.4 has in Assist menu function Clear duplicate models. I was told it is slightly bugged and I saw it sometimes clearing also models which were not duplicated, but you can give it a try. Anyway, don't use it more than once on a map.
It has only one bug. It removes also the models that share exactly the same coords. Like to model spawned inside each other.
rektbyfaith
11-30-2015, 01:18 PM #10

Archived author: Skarn • Posted: 2015-11-30T13:18:40+00:00
Original source

Quote:There might be another reasons for having lags in map edited by Noggit, but mot of them were gone with newere versions of app. Still, duplicated objects are the most common case. If you had about lets say 10000 objects on original ADTs and your duplications turned them into 20000-30000, then yes, you surely will have lags because of that, and quite likely only because of that.

About deleting duplicated objects... SDL 1.4 has in Assist menu function Clear duplicate models. I was told it is slightly bugged and I saw it sometimes clearing also models which were not duplicated, but you can give it a try. Anyway, don't use it more than once on a map.
It has only one bug. It removes also the models that share exactly the same coords. Like to model spawned inside each other.

Pages (2): 1 2 Next
Recently Browsing
 1 Guest(s)
Recently Browsing
 1 Guest(s)