Page 13 of 14

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Tue Apr 17, 2018 11:51 pm
by Switeck
I'm pretty sure older versions didn't have this problem, so I may ditch the looks and just keep the logic of the new one.

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Wed Apr 18, 2018 5:29 am
by another_commander
cbr wrote:
Tue Apr 17, 2018 10:13 pm
It could be that what we see ( the distance we see ) and the actual collision detection are two different things.
Try checking what the actual bounding boxes and octrees for collision detection look like and see if something seems out of place. You can display those using the debug console and executing the command

Code: Select all

console.debugFlags = 0x40 | 0x80

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Wed Apr 18, 2018 8:13 am
by jackiebean
is the dock an untextured model of some sort? i think it is. could the solution be to make the dock box larger? or maybe center it a bit better?

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Wed Apr 18, 2018 4:24 pm
by cbr
I think the docking is related to being in a certain place which initiates the procedure, just like those refueling stations.

Here is a picture with the actual bounding boxes as per another_commanders code.

Image

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Thu Apr 19, 2018 2:44 pm
by jackiebean
hmmm, well it doesnt look like there is anything physically there to hinder a ship.

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Sun Apr 29, 2018 4:33 am
by Switeck
Then the most likely explanation is the model's graphics are simply not lined up with where the game thinks the "solid" parts are.

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Mon May 28, 2018 7:46 pm
by Switeck
Superhub v1.5 OXP does not have this problem.

It seems to use the smaller textures and lacks a defined docking port piece.

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Wed Dec 05, 2018 3:40 pm
by Svengali
The easist fix would be to scale down the model for the dock along the z-axis (e.g. to a length of 100 instead of 2000).

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Sat Dec 08, 2018 8:02 am
by MarchHare
So this is a really stupid question, and maybe off topic. How do I actually get docking clearance approved? Whenever I request it, I always get a denied response.

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Thu Dec 20, 2018 9:59 pm
by Svengali
MarchHare wrote:
Sat Dec 08, 2018 8:02 am
So this is a really stupid question, and maybe off topic. How do I actually get docking clearance approved? Whenever I request it, I always get a denied response.
Are you fugitive?

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Fri Dec 21, 2018 1:10 am
by Nite Owl
Are you using the Super Hubs for Extra Planets OXZ ?

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Thu Oct 01, 2020 7:32 am
by Cholmondely
MarchHare wrote:
Sat Dec 08, 2018 8:02 am
So this is a really stupid question, and maybe off topic. How do I actually get docking clearance approved? Whenever I request it, I always get a denied response.
This is a recurring problem for others, too. I discovered this anomaly both before I added in Superhubs for extra planets - and after that too! And no, I'm not a fugitive (never having had to live in a communist or a fascist state, thank heavens!).

Also, the superhubs markets do not show up on Market Enquirer - even when they are the sole orbital station around the second planet in the solar system.

So why do these perverse peculiarities appertain to solely to Superhubs?

Benedict has hypothecated that these Superhubs might actually be emergent independent states and that the poor benighted solar systems which contain them are verging on a breakdown to anarchy. Their utter refusal to respond to gentlemen of quality and provide suitable accommodation to moderate requests indicates extremist political leanings, which need treating with a hefty dosage of disinfectant before things get worse. Why have Galcop not intervened and put an end to such shenanigans? WHERE IS GALCOP?

But why is it just superhubs which display these perverse tendencies? Benedict has argued that it is the psychological effect of living poised around an abyss - that the vacuous nature of such cylindrical habitation affects the corpus collosum in such a fashion as to stimulate the search for a supremely strong bedrock of fanatical devotion to a fundamentalist political creed such as one finds in Bolshevist and Fascist tyrannies. The sempiternal revolution of the cylinder induces an affectation for similar revolutions in one's socio-political circumstances in the existential search for certainty, inhibiting one's appreciation of more stable gubernatorial arrangements such as feudalism.

Presumably, if one can inhibit the revolutions of these superhubs, then despite the engendered tendencies towards political extremism, the desires for these highly inconvenient unilateral declarations of independence will be inhibited and they will again be available for trading and docking.

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Thu Oct 01, 2020 10:38 am
by Nite Owl
In Super Hubs for Extra Planets there is a missing subentity_key in each of the four Super Hubs listed in its shipdata.plist. This prevents those Super Hubs from accepting docking requests. It also generally prevents docking should you have Docking Requests set to being required. Naturally it is the "Dock" subentity_key that is missing hence the problems. If you are handy with a bit of .plist editing add the following subentity_key to each of the four Super Hubs listed in the aforementioned shipdata.plist. That is you have to add the following code four times in four different places. Reads as being complicated but if you have a look at it you will find it rather easy. Just look at the other subentity_key entries and you will find where and how it should go.

Code: Select all

{ 
subentity_key = "pagroove_superhub_dock";
type = "standard"; 
is_dock = true;
},
If you want to take it one step further then read on. In the original Super Hub OXZ (not Extra Planets) shipdata.plist at around line 100 (notepad++) you will find an entry for pagroove_superhub_dock that reads as follows.

Code: Select all

 ai_type = "dumbAI.plist"; 
What you want that line to read is the following.

Code: Select all

 ai_type = "dockingAI.plist"; 
This second change is not really necessary to get the docks to accept your Docking Requests but it is a nice thing to have since the dockingAI.plist was added to the game after the initial release of this OXZ. Just to be clear the original Super Hub OXZ is needed in order for the Super Hubs for Extra Planets OXZ to be functional.

There really should be an updated release of these OXZs with the needed changes but my license foo is not what it should be so how to proceed is unclear to me. Advice on how to proceed or someone else doing said release would be much appreciated. Could do a new release myself but there is a lot of other tweaking that has been done to these OXZs for my Ooniverse and where to stop between functionality and tweaked stuff might become an issue. Nobody ever said the life of a code tweaker was an easy one. Just enough knowledge to get myself into trouble but not enough knowledge to actually make stuff from scratch.

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Thu Oct 01, 2020 11:51 am
by Cholmondely
I'll have a stab at this - thank you for the instructions!

Personally speaking, I'd be perfectly happy with your own personally tweaked versions (unless they come emblazoned with swastikas or hammer & sickle logos - I don't think that I could cope with Benedict's smugness at having one of his theories proven correct)!

Re: [UPDATED RELEASE 03-07-2014] Superhub V1.6 OXZ

Posted: Thu Oct 01, 2020 2:49 pm
by Cholmondely
It rather looks as though my stab backfired.

Editing the original Pagroove .oxp was a doddle, whilst with Norby's extra planets .oxp the dastardly deed required some inspired guesswork.

When I'd finished stowing everything away where it was supposed to go, I got the following message on firing up: that neither had a valid manifest.plist and that neither could be loaded.

I'm stumped. But then I was stumped before. But at least this time I got to unzip and rezip prior to restumping!

Whither next, O Magnificent Maestro of the Machiavellian Marmalisation of .oxps?

And, on a minor note - why is the manifest.plist involved in all this malarky?