Base/Path/Universe Issue?
-
Hi folks.
I added a couple of new systems in today, and now both FLEC and FLScan are starting to spit their dummys out for strange errors. Such as this (from FLEC):
Line #47094 - MBase's base entry no01_01_base was not found in any system ini (check in UNIVERSE\SYSTEMS\)I know for a fact it is there, I checked it. The entries are correct in universe.ini, the system file itself, the actual system base entries/files and mbases.ini. It is all there. Hell, I even went back and re-did all the proper casing on the letters too. Same problem. It seems to have started doing this after I generated new system paths with Chips’ utility.
It doesn’t do anything like crash when going around systems, but why would they throw errors? Is there a typo somewhere or is it a known problem with paths. Just so you know, my new systems are connected in series (that is, in a chain, like one after another), and connect with the vanilla system Ew02. It all seems to have done this since I have done these new links or generated new paths.
I actually read somewhere (on here?) about someone saying they had to create ‘legal’ paths, ie. those with a jumpgate, even it is unused, to an existing vanilla system to prevent said errors. Is there any mileage in me doing this? In any case, please help; this crap gets stranger for me I swear!
-
Ooo, yeh good idea. I’ll check for duplicates
I honestly do think I have an issue with paths now though, as I crash when entering one of my new(er) systems. All vanilla jumps work perfect though… strange huh…
All other ‘obvious’ errors have been taken care of, and I generated path info with Chips’ tool, like I said above. Not sure if this structure has anything to do with it. Perhaps the tool doesn’t like it? All jumps work great except the jump into the new system from… Ew02 (where it starts to branch out from).
I checked the path files manually, and I don’t really know how it works exactly, but it seems to be how you get from one system to another, and every eventual path through each… I noticed my very edge (tail) system doesn’t have an entry at all in those path files… not even in the ‘illegal’ one. They are all using jumpholes you see, not gates if that makes any odds. Perhaps I need to add entries manually at this stage. If so, is there anything I can refer to? Sorry to be a pain if I am
-
Ok for anyone who might come across this in the future…
I feel like I massive d#;'head now. I was pointing FLPathGen to my working/mod directory and not the game folder after activating the mod files. Thus, my jump objects weren’t getting parsed properly, and the paths to certain areas were not made properly… resulting in the crash. Haha ;D
I’ll report back on the bases stuff if this doesn’t fix…
![😕](https://the-starport.com/forums/assets/plugins/nodebb-plugin-emoji/emoji/android/1f615.png?v=mhmq9j4qrjg ":-\")
-
What that error is telling you is that the entry eists in the mbases.ini but does not exist in the no01_base.ini, coule be something simple like a typo.
-
Nope, it does exist in there. And it’s all correct. I even copied and pasted to cross-reference to rule out a typo
This is strange… i’ll probably just redo the base from scratch for completeness… -
Question. Would invalid paths result in FLScan saying that a base is invalid… or that destination jump locations are invalid. I have entries in ‘all’ necessarry files… yet I crash when entering the system, or when undocking from a base in that system. There are no typos or anything… this is screwed…
-
I wouldnt have thought so, the only thing to my knowledge that that would do is crash your server.
It may be a good idea to post all your ini entries for the base such as the system,mbase and universe.ini entries. Maybe one of us will see something you missed.
-
Yeah…
I created new legal paths, by adding jumpgates rather than holes… and that cleared up all FLScans errors about invalid bases etc… so obviously that was related to the paths I suppose. But I still have crashes in my new systems… sometimes, the client goes… sometimes the server and client go… I will defo post up if I don’t solve this
-
sorry tripleJH, ifg you have beef with a forum user, please take it to PM’s your post has been edited.
-
Keep crap out of my thread!!! grrr
;DFor anyone who was following this, I created legal paths with the path gen tool, once I had added in jumpgates to all the necessary places (ie. in every new system). Once that was done, I removed the gates. It doesn’t crash at all now, and as far as the scanner apps are concerned all my bases are valid. So it must have been a pathing issue after all, although why I don’t now.
I know roughly what each of the universe files are for, and I now that the rough idea is “<source>, <destination>, <route-through>”, but further to that I’m not sure why it was crashing. To be honest, why did they come up with such a system? If you enter a new system, that’s what you do right… no need for all this pathing rubbish ;)</route-through></destination>
-
These files are mainly used by the waypoint system to give you the shortest path from point A to point B; back in the day, I guess the calculations required to figure this path in real-time would’ve been too costy (or maybe the code would’ve been too complicated), so they decided to just dump the paths in files.
I’m pretty sure they are used elsewhere, too. Your crashes apparently indicate one way, but maybe AIs also use it.
-
Yeah that certainly is one way of interpreting it
I fixed that issue, although I didn’t address it ‘directly’, rather re-did a bunch of crap to eliminate as much as possible as the issue. Got fed up by a certain point
The paths seemed to be ok once running the path gen. I’m thinking it was more along the lines of a zone issue… probably an exclusion zone(s), as they were present in both the systems that seemed to be problematic
