[DiscordArchive] <@!100246412050075648> Could you clear something for me ?
[DiscordArchive] <@!100246412050075648> Could you clear something for me ?
Original source
<@!100246412050075648> Could you clear something for me ?
rektbyfaith
01-06-2020, 01:44 PM #1Archived author: A2 • Posted: 2020-01-06T13:44:54.058000+00:00
Original source
<@!100246412050075648> Could you clear something for me ?
Original source
Found some time to dig again in those boxes of render batches from WMO groups
rektbyfaith
01-06-2020, 01:45 PM #2Archived author: A2 • Posted: 2020-01-06T13:45:24.586000+00:00
Original source
Found some time to dig again in those boxes of render batches from WMO groups
Original source
I thought that the box is just min - max values for X Y Z but Im seeing in lots of WMOs that some values are extremly high like 65529
rektbyfaith
01-06-2020, 01:46 PM #3Archived author: A2 • Posted: 2020-01-06T13:46:09.314000+00:00
Original source
I thought that the box is just min - max values for X Y Z but Im seeing in lots of WMOs that some values are extremly high like 65529
Original source
Now I thought that the value in box are just minimal/maximal values that are took from MOVT
rektbyfaith
01-06-2020, 01:46 PM #4Archived author: A2 • Posted: 2020-01-06T13:46:55.089000+00:00
Original source
Now I thought that the value in box are just minimal/maximal values that are took from MOVT
Original source
But MOVT contains only coordinates for vertices right ? so how comes so that values in batch box can be 65k high I mean vertices from MOVT barely hit 200 +/-
rektbyfaith
01-06-2020, 01:48 PM #5Archived author: A2 • Posted: 2020-01-06T13:48:05.367000+00:00
Original source
But MOVT contains only coordinates for vertices right ? so how comes so that values in batch box can be 65k high I mean vertices from MOVT barely hit 200 +/-
Original source
If i understand it correcty the MOVTs vertices coordinates are took from origin of model so in theory if you are doing iteration thru MOVT to took max and min values for box and in the end box ends up with 65k value would that mean that iteration found vertices that far away from origin ? or just some calculating error ?
rektbyfaith
01-06-2020, 01:50 PM #6Archived author: A2 • Posted: 2020-01-06T13:50:02.830000+00:00
Original source
If i understand it correcty the MOVTs vertices coordinates are took from origin of model so in theory if you are doing iteration thru MOVT to took max and min values for box and in the end box ends up with 65k value would that mean that iteration found vertices that far away from origin ? or just some calculating error ?
Original source
but then again im seeing same values in blizz models too ...
rektbyfaith
01-06-2020, 01:50 PM #7Archived author: A2 • Posted: 2020-01-06T13:50:42.116000+00:00
Original source
but then again im seeing same values in blizz models too ...
Original source
it is some calculating error in my addon
rektbyfaith
01-06-2020, 02:04 PM #8Archived author: Skarn • Posted: 2020-01-06T14:04:18.058000+00:00
Original source
it is some calculating error in my addon
Original source
I am working on fixing that
rektbyfaith
01-06-2020, 02:04 PM #9Archived author: Skarn • Posted: 2020-01-06T14:04:23.480000+00:00
Original source
I am working on fixing that
Original source
I noticed 65k values basicaly everywhere thats why im so confused
rektbyfaith
01-06-2020, 02:05 PM #10Archived author: A2 • Posted: 2020-01-06T14:05:47.395000+00:00
Original source
I noticed 65k values basicaly everywhere thats why im so confused
1 Guest(s)
1 Guest(s)