[DiscordArchive] <@213383518842126336> any plans to add UID syncing via DB to noggit?
[DiscordArchive] <@213383518842126336> any plans to add UID syncing via DB to noggit?
Original source
<@213383518842126336> any plans to add UID syncing via DB to noggit?
rektbyfaith
11-09-2022, 06:30 PM #1Archived author: intra • Posted: 2022-11-09T18:30:01.959000+00:00
Original source
<@213383518842126336> any plans to add UID syncing via DB to noggit?
Original source
You can use a Git repository as a workaround if you ensure map editors are constantly downloading the latest changes.
rektbyfaith
11-09-2022, 06:39 PM #2Archived author: Valaryon • Posted: 2022-11-09T18:39:26.275000+00:00
Original source
You can use a Git repository as a workaround if you ensure map editors are constantly downloading the latest changes.
Original source
that's the current approach, but it does occasionally happen that they're not synced up to latest version. also, multiple people simultaneously working can mess things up
rektbyfaith
11-09-2022, 06:42 PM #3Archived author: intra • Posted: 2022-11-09T18:42:30.257000+00:00
Original source
that's the current approach, but it does occasionally happen that they're not synced up to latest version. also, multiple people simultaneously working can mess things up
Original source
Yeah that doesn't work well for us when 2 people want to edit the same map at roughly the same time.
rektbyfaith
11-09-2022, 06:42 PM #4Archived author: Deleted User • Posted: 2022-11-09T18:42:58.497000+00:00
Original source
Yeah that doesn't work well for us when 2 people want to edit the same map at roughly the same time.
Original source
Our approach is ensuring editors work on different ADTs and if they are precise you can avoid conflicts. If there is conflicts, there are Git methods that you can pick and choose which ADTs to merge. Inefficient, but useful.
rektbyfaith
11-09-2022, 06:45 PM #5Archived author: Valaryon • Posted: 2022-11-09T18:45:25.420000+00:00
Original source
Our approach is ensuring editors work on different ADTs and if they are precise you can avoid conflicts. If there is conflicts, there are Git methods that you can pick and choose which ADTs to merge. Inefficient, but useful.
Original source
That doesn't really resolve the UID issue though no? We've had it where someone adds models to stranglethorn and someone else adds models to westfall and they're close enough that the client can crash due to the UID mismatch and noggit warns about it too. We find ourselves having to regen UID's for a whole map at least once a month.
rektbyfaith
11-09-2022, 06:48 PM #6Archived author: Deleted User • Posted: 2022-11-09T18:48:17.940000+00:00
Original source
That doesn't really resolve the UID issue though no? We've had it where someone adds models to stranglethorn and someone else adds models to westfall and they're close enough that the client can crash due to the UID mismatch and noggit warns about it too. We find ourselves having to regen UID's for a whole map at least once a month.
Original source
The edits are kept easily enough so we haven't lost any models but pushing 1gb of adt's that often sucks
rektbyfaith
11-09-2022, 06:48 PM #7Archived author: Deleted User • Posted: 2022-11-09T18:48:54.134000+00:00
Original source
The edits are kept easily enough so we haven't lost any models but pushing 1gb of adt's that often sucks
Original source
You need to Git sync UID too, revert if UID issues occur - but the issue of working on same ADTs can be resolved with Git merge management.
rektbyfaith
11-09-2022, 07:22 PM #8Archived author: Valaryon • Posted: 2022-11-09T19:22:15.419000+00:00
Original source
You need to Git sync UID too, revert if UID issues occur - but the issue of working on same ADTs can be resolved with Git merge management.
1 Guest(s)
1 Guest(s)