Developer's Backdoor > GSX Backdoor

some questions

<< < (6/6)

virtuali:

--- Quote from: mroschk on October 13, 2018, 01:31:19 pm ---Ahhh, now it is a tollerance problem or my fault because i stopped too late ???? Ohhh yes, the fault was on my side ... for sure it was not.
--- End quote ---

Was your parking rated as "Very Good" ?

As I clearly explained, we still consider a parking within 50 cm of the Stop Position to be Very Good. That doesn't obviously mean GSX calculated the position in the wrong way, only that we allow some slack in the evaluation.

But if you park perfectly (distance readout at 0.0), the Nosewheel WILL be in the stop position you set earlier.


--- Quote ---But as i say, i will also record a video specially for you.
--- End quote ---

I already have (see above), and I parked perfectly.

mroschk:
Ok, i had the time to record a video.
Sory, i stopped 2 times to reach 0.1 Marshaller distance readout.



That says all now

I dont know, why it is not working here.

virtuali:

--- Quote from: mroschk on October 15, 2018, 11:10:42 am ---That says all now
--- End quote ---

Doesn't say anything, if you don't say which airplane you used to customize the parking. Was the same one you used to park ?

If not, the only thing your video shows, is the stop parking positions drawn on the texture on that scenery, don't use the same different offsets we used at KLAX. We cannot possibly know anything about offsets in a texture. How you do expect GSX could do that ? Recognizing the marks ?

Different airports/gate might require different sets of offsets. Or, they might be simply inaccurate on that scenery. How GSX is supposed to know that ?

And yes, before you start launching yourself in another unfunded "you don't know how it works" nonsense, GSX CAN support something like this internally.

We can specify a custom-made table of offsets, depending on the airplane type, that can OVERRIDE the default strategy of trying to place the preferred exit in the same place (resulting in the nosewheel stopping in different positions), but this feature is not accessible to users, because we always find it was *very* complex to use.

Users found the jetway editor complex and the custom pushback even more complex, but they are nothing compared to what would be required to do something like this. On a 3rd party scenery, for *EACH* different custom texture with stop markings on ground, the user would have to customize a different offset for ALL the airplane types listed on that texture, and this would be in addition to the Stop Position, which would be like a "zero" reference. So, a table would be created, with the airplane type and its offset, and this would have to be applied to all parkings that use the same texture. If a scenery used more than one texture (for example, one for heavy gates, one for medium, etc. ), this process would have to be repeated for each different set of markings.

Yes, GSX CAN do that, internally, but are you sure you would like to do THAT ?

mroschk:
it is enough now.
I did not post any NONSENSE , you are not alowed to say something like that about a user who payd for your app.

It is one video and you see all the actions i did and i did not chnge the aircraft, if you mean that.
So first you see, i have correct set up the Stop position and the i used SHIFT+P to move the airplane a little bach to call the Menü for parking.Then i just roll forward into the position and did not end up at the Stop position.

So, it has nothing to do which arcraft i use ( B737-800 by the way ) because i set up the Stop position.
So what has the aircraft to with that, i did not change the aircraft!

So, the video explains all you need. Thats the reason why i did a video and did not a lot of screenshots.
I dont want to waste any more tie with you stupid guy

virtuali:

--- Quote from: mroschk on October 15, 2018, 12:21:18 pm --- it is enough now. I did not post any NONSENSE , you are not alowed to say something like that about a user who payd for your app.
--- End quote ---

Yes, you have. You posted nonsense, by continuing to repeat I "don't know how it works", and you are not allowed to say that, without knowing all the facts.


--- Quote ---It is one video and you see all the actions i did and i did not chnge the aircraft, if you mean that.
--- End quote ---


--- Quote ---So first you see, i have correct set up the Stop position
--- End quote ---

No, you haven't.

I saw your video again, and you HAVE NOT set the Stop position, you set the position of the PARKING itself, which is NOT used to set the Stop position but, instead, is used to fix any possible errors (misplaced or not aligned parkings in the scenery AFCAD).

I assumed from your previous post you knew the difference between the STOP position and the position of the parking itself but, after seeing your video, is seems you don't. The Parking position has an icon which resembles the AFCAD parking. The STOP position, instead, has a icon that looks like a STOP sign.

So, you know what you are editing, by looking at the icon. And, the thing you are editing is highlighted in Orange. In your video, the only thing you edited, at 1:17, was the position of the parking, NOT the Stop Position, which was still in Blue, meaning it wasn't the object currently edited.

Nowhere in your video it shows you ever edited the STOP position.


--- Quote ---So, it has nothing to do which arcraft i use ( B737-800 by the way ) because i set up the Stop position.
--- End quote ---

No, you haven't, you confused the Stop position with the parking position.


--- Quote ---I dont want to waste any more tie with you stupid guy
--- End quote ---

I knew that, after being repeatedly proven wrong, over and over, you didn't had anything left other than resorting to insults. This just gained you a week of ban from the forum. Topic is closed.

Navigation

[0] Message Index

[*] Previous page