Forums WoW Modding Support Archives TrinityCore Discord Archives [DiscordArchive] basically consteval same as constexpr but it cant be called runtime? or also some other difference?

[DiscordArchive] basically consteval same as constexpr but it cant be called runtime? or also some other difference?

[DiscordArchive] basically consteval same as constexpr but it cant be called runtime? or also some other difference?

rektbyfaith
Administrator
0
03-19-2024, 01:46 PM
#1
Archived author: moJIto_ice • Posted: 2024-03-19T13:46:13.105000+00:00
Original source

basically consteval same as constexpr but it cant be called runtime? or also some other difference?
rektbyfaith
03-19-2024, 01:46 PM #1

Archived author: moJIto_ice • Posted: 2024-03-19T13:46:13.105000+00:00
Original source

basically consteval same as constexpr but it cant be called runtime? or also some other difference?

rektbyfaith
Administrator
0
03-19-2024, 02:02 PM
#2
Archived author: Tea • Posted: 2024-03-19T14:02:49.330000+00:00
Original source

unfortunately you arent right here, intersectPoint is a specialized (optimized?) version of intersectRay that has hardcoded ray direction = { 0, 0, -1 } and infinite maxDist
rektbyfaith
03-19-2024, 02:02 PM #2

Archived author: Tea • Posted: 2024-03-19T14:02:49.330000+00:00
Original source

unfortunately you arent right here, intersectPoint is a specialized (optimized?) version of intersectRay that has hardcoded ray direction = { 0, 0, -1 } and infinite maxDist

rektbyfaith
Administrator
0
03-19-2024, 02:05 PM
#3
Archived author: shelby • Posted: 2024-03-19T14:05:04.435000+00:00
Original source

Right, then the problem is mostly the bounding box of the sub model
rektbyfaith
03-19-2024, 02:05 PM #3

Archived author: shelby • Posted: 2024-03-19T14:05:04.435000+00:00
Original source

Right, then the problem is mostly the bounding box of the sub model

rektbyfaith
Administrator
0
03-19-2024, 02:07 PM
#4
Archived author: shelby • Posted: 2024-03-19T14:07:35.322000+00:00
Original source

But i'm not sure its the only problem because as i understand, inside the BIH we use the bounding box of the whole WMO, created in groupTree.build
rektbyfaith
03-19-2024, 02:07 PM #4

Archived author: shelby • Posted: 2024-03-19T14:07:35.322000+00:00
Original source

But i'm not sure its the only problem because as i understand, inside the BIH we use the bounding box of the whole WMO, created in groupTree.build

rektbyfaith
Administrator
0
03-19-2024, 02:10 PM
#5
Archived author: shelby • Posted: 2024-03-19T14:10:48.238000+00:00
Original source

I removed the groupTree.intersectPoint, call the callback manually for all models inside the group and changed the bounding check inside GroupModel::IsInsideObject to be containsXZ instead of contains to remove the z-axis check and it seems to works.
However i probably decreased the peformance by alot and it may cause other issues
rektbyfaith
03-19-2024, 02:10 PM #5

Archived author: shelby • Posted: 2024-03-19T14:10:48.238000+00:00
Original source

I removed the groupTree.intersectPoint, call the callback manually for all models inside the group and changed the bounding check inside GroupModel::IsInsideObject to be containsXZ instead of contains to remove the z-axis check and it seems to works.
However i probably decreased the peformance by alot and it may cause other issues

Recently Browsing
 1 Guest(s)
Recently Browsing
 1 Guest(s)