I was hunting a solution for retrieving brush data, more exactly geometry problems.
It's not like you can do anything in UScript even if you can iterate through objects not actors or I could not figure what's doable.
I quit trying to gain geometry errors and I hit another try in the other side which I could manage due to last XC works as they are type XCGEv24.
This requires XC_Engine v24+ (or only 24) which has to be in editing assets not exactly set as game extension.
I think soon I will show in public the builder returned from initial purpose into another Paths worker using UScript through Editor. It's not Unreal227 - it's UnrealTournament this time...
What's the point of another way of building paths ?
#1 Range option - not only in v21 and v25b - XC builders in stage;
#2 Paths charge control - prevent over-loaded nodes connected in 8 directions to other nodes connected each-other and all that useless spam eye paths-lines;
#3 Two build types which original UT is not really having: Monster-Paths - Titans in stage capable to roam or do whatever patrols, Bot paths known in fake news from tutorials as Heavy paths - original UT out of XC_EditorAdds is drawing them in RED;
#4 It does a valid log where "Scout did not fit" or else we won't know where is the spot with possible issues;
#5 It is excepting paths created for items hidden in Editor for preventing any over-load;
#6 It logs reachSpecs created and other several data for having a clue what paths are suitable, even if final build option sorted by mapper is original build if doesn't like this way or it's too complex;
#7 It won't mess with bOneWay paths - such points are left alone letting user to connect this point where wants and how wants using human eye;
#8 Extra control in adjusting ReachSpecs - enlarging default ones - creating new specs where Editor is "forgetting" them;
#9 Completing Paths after building paths using other builder or Editor itself - exactly - you can polish a bit missing paths or hijack reachSpecs. This is a bit complex but... we have manual control for doing this. Different said, Path from PathNode0 to PathNode1 is evil. We need a Path from PathNode3 to InventorySpot1. We can "move" evil path into missing path and adjusting Paths List from nodes involved. At this moment reachSpec adjusted must be moved manually in Paths lists, perhaps in future it will be automated, these are rare needs, we can reduce range or doing things different and such an option it's not widely used, but right now it's possible to do some stunts this way.
I won't bet that I found the most great ever solutions due to iterations limit from UE1 and then all things/checks must be minimized while Builder is working.
Technically it is moving pretty fast, it draws paths at certain interval - so to speak it's updating ViewPort during working stage.
Not yet implemented: Automated Air routes - perhaps not needed because there it is advisable user control with human eye and not scripted predictions.
This is the tool in current stage:
- UT99_PathsWorks.PNG (9.46 KiB) Viewed 8932 times
You can imagine the mystery haunting me: Why would not be welcomed such a builder boosted by it's own natives like that MP3 OGG support for newer audio drivers ? It's when I don't get why would not have all editing options for slapping down bugs as much as possible...
The known problems - perhaps bugs:
- XC doesn't offer support for wiping bad path but making null - not really deleting junk data.
- No great power of new XC iterators because they are refusing to work in Editor - or I cannot put them on the right way, and then original UT ones are not the best.
Builder contains a template, a dummy reachspec where user can demand what wants as path for certain spot, this is like that red brush template from which Editor is building a room. Here is build/created a future Path/ReachSpec using this dummy formula. Point nodes A and B can be completed by builder as well. We don't need too much names writing, builder is writing these for you. What is needed as data: navigation flags and collision accepted, the rest is calculated automatically.
I have to track well in various tests if something need corrected before any release.
I doubt that this will have more users because here is needed some experience, you need to know well what you want or else your paths won't help with anything.
I think here is needed attaching a tutorial well explained. Perhaps technical UE1 terms not well combined in english might be causing headaches for users. I don't think everyone will figure how to do these... but maybe somebody from this planet will say "Thanks" or... "Give me a break, this it's destroying my brain" or whatever... Not all works for UT are are aiming every single user in end.
