*** SODEPlacer V0.6 ***

[kmanning]

Hi Ken,

The user in post #23 probably has/had the same problem.
The prerequisite is that Java is recognized correctly by Windows.

It looks to me like either Java is not installed correctly or it is Java 64bit.

Well, I fixed the problem several days ago and thought I would post it here. The problem was not rather I use the 32 bit or the 64 bit version. Every time I click on the SODEPlacer.jar file, it would never open the SODE Placer program. It would open another zipped file. I knew there was nothing wrong with my installation, and I was doing everything correctly. The fix was that I had to run a program called jarfix.exe to fix this problem. It's working fine now and I'm using the 64 bit version.

But I'm having a problem with the Initial State KeyFrame using the Edit Jetway SimObjects box. In the manual, it says that I should see my results live in the sim when I make changes here. But when I click on one of the KeyFrame to set the initial position, nothing happens and there is no change with the jetway in the sim. The manual says I would see these changes, but I'm not seeing any changes. Am I doing something wrong?

Ken.

 

[Bushpilot]

Hi Ken,

Well, I fixed the problem several days ago and thought I would post it here. The problem was not rather I use the 32 bit or the 64 bit version. Every time I click on the SODEPlacer.jar file, it would never open the SODE Placer program. It would open another zipped file. I knew there was nothing wrong with my installation, and I was doing everything correctly. The fix was that I had to run a program called jarfix.exe to fix this problem. It's working fine now and I'm using the 64 bit version.

It's great that you've found a solution to the problem.

But I'm having a problem with the Initial State KeyFrame using the Edit Jetway SimObjects box. In the manual, it says that I should see my results live in the sim when I make changes here. But when I click on one of the KeyFrame to set the initial position, nothing happens and there is no change with the jetway in the sim. The manual says I would see these changes, but I'm not seeing any changes. Am I doing something wrong?

It would only be important that SODEPlacer and the P3D are started and that you are at the gate with your aircraft where the jetway is to be processed.
Here is an example in ETNL.

Connect SODEPlacer with P3D (red 1.).
Now a small red aircraft symbol is displayed in the SODEPlacer (where your aircraft is currently located).
Here you can now see the already saved jetways from your newly created SODE-xml for your airport.

To see the changes in the P3D, you must activate the live preview (blue 2.).
Now double-click on the jetway (which is to be edited).
The edit window of the Jetway opens and you can edit the Initial State KeyFrame.
You can follow this editing live in P3D, provided you are at the correct gate with your aircraft.

 

[kmanning]

Hi Ken,



It's great that you've found a solution to the problem.



It would only be important that SODEPlacer and the P3D are started and that you are at the gate with your aircraft where the jetway is to be processed.
Here is an example in ETNL.

View attachment 94086

Connect SODEPlacer with P3D (red 1.).
Now a small red aircraft symbol is displayed in the SODEPlacer (where your aircraft is currently located).
Here you can now see the already saved jetways from your newly created SODE-xml for your airport.

To see the changes in the P3D, you must activate the live preview (blue 2.).
Now double-click on the jetway (which is to be edited).
The edit window of the Jetway opens and you can edit the Initial State KeyFrame.
You can follow this editing live in P3D, provided you are at the correct gate with your aircraft.

Hi Mike,

I already know how to use it and it works fine when I move the jetway and placing it, and I can see my results live in the simulator. Under Placement, I can set the heading and its position. Under Properties Static SimTitle, it just says Not Defined in the box but I don't know what that means. Under Initial State KeyFrames, there are 4 settings: Root Rotaion, Bridge Dip, Heading Rotation, and Bridge Extension. This is where I'm having the problem. Why doesn't the jetway in the sim not respond to my actions live in the sim when I click the arrows? For example, if I click Extend Bridge, the bridge does not extend live in the sim. If I click on Bridge Dip, it does not dip live in the sim. None of the 4 settings work live in the sim. The only time when I see my results is when I restart the simulator. But that means restarting over and over again until I get it right. They do make the changes, but I only see that after I restart the simulator. I do have SODE connected to the sim and Live sim turned on. From what I understand, the manual says I should see live results in the simulator when I make changes under the Initial State KeyFrame. Is that correct?

Ken.

 

[Bushpilot]

Hi Ken,

I do have SODE connected to the sim and Live sim turned on. From what I understand, the manual says I should see live results in the simulator when I make changes under the Initial State KeyFrame. Is that correct?

Yes, that is correct.
And this works for me without any problems.

The Initial State KeyFrames are used to align the Jetway in the rest position.
So that it fits certain aircraft models.
This is because the gates are designed for specific aircraft models.

To test the new position of the jetways, the P3D must be restarted so that all data is correctly recorded by SODE.
It is sufficient to execute SODE Reload all in P3D via Add-ons so that the SODE objects are reloaded.

I have noticed one more thing.
The static jetways should only be added once the dynamic jetways have been adjusted.
Otherwise it's just confusing, as the jetway jumps when activated.

If you change the Initial State KeyFrames for the dynamic jetways, the existing static jetways will no longer fit (jetways jump to docking on takeoff) and you will have to create new static jetways.


The aircraft.cfg of the respective aircraft or the AircraftExits.ini in the SODE folder determines that the Jetway docks at the correct position.

 

[kmanning]

Hi Ken,



Yes, that is correct.
And this works for me without any problems.

Then why am I'm not seeing the jetway getting longer or dipping down live in the sim as I'm making these changes using the Initial Stare KeyFrame? I only see that change after I restart the sim. But that is setting the jetways by trial and error.

To test the new position of the jetways, the P3D must be restarted so that all data is correctly recorded by SODE.

I'm confused here. You said above that I was correct that I should see the changes live in the sim as I'm making changes using the Initial State KeyFrame. Here, you're saying to test the new position of the jetways, I have to restart PD3 to see those changes. I'm confused here. Why is there a line running across the sentence - "the P3D must be restarted so that all data is correctly recorded by SODE." Are you saying that the sim must be restarted before I see the changes? If that's the case, then it's a trial and error in making these changes when it seems to me I should see these changes live in the sim as I'm making the changes so that I don't have to keep restarting the sim and just making trial and error settings.

I have noticed one more thing.
The static jetways should only be added once the dynamic jetways have been adjusted.
Otherwise it's just confusing, as the jetway jumps when activated.

If you change the Initial State KeyFrames for the dynamic jetways, the existing static jetways will no longer fit (jetways jump to docking on takeoff) and you will have to create new static jetways.

The aircraft.cfg of the respective aircraft or the AircraftExits.ini in the SODE folder determines that the Jetway docks at the correct position.

I don't use static jetways, nor static airplanes because I want them all to work. Is the box Initial State KeyFrame just for static jetways only or are they used to set the start position of the dynamic jetways?

Ken.

 

[Bushpilot]

Hi Ken,

I'll have to go into a little more detail.

I assume that you are using the SODE Jetways objects from Drzewiecki Design.
Every designer of jetways uses dynamic and static ones.
Because simply using dynamic jetways would overwhelm the simulator (whether FSX or P3D) and bring it to its knees.

Every single SODE object is an AI object for FSX/P3D.
And AI objects place a particularly heavy load on the simulator.

Therefore, AI objects should be used with caution, whether AI traffic (airplanes, cars, boats) or SODE objects.

For this reason, the developer of SODE has made it so that you only see static jetways in FSX/P3D, which reduce the load on the simulator.
Only at the moment when an airplane is at the gate and the jetway is docked,
only then does the static jetway become a dynamic jetway.

I don't use static jetways, nor static airplanes because I want them all to work. Is the box Initial State KeyFrame just for static jetways only or are they used to set the start position of the dynamic jetways?

The Initial State KeyFrame is for the dynamic jetways to set the take-off position/exit position.

Then why am I'm not seeing the jetway getting longer or dipping down live in the sim as I'm making these changes using the Initial Stare KeyFrame?

If you are using the SODE jetway objects from Drzewiecki Design, the designer could also have built in protection here (similar to his SODE xml).
So that you cannot set the jetways directly.

If you send me the SODE jetway objects, I can try this out on my site.

So far I have tried it with the jetway objects from ImagineSim_KATL, AS_PANC and the jetway from the SODE Demo SimObjekts.
With all these Jetways, the Initial State KeyFrame setting works for me as it should.

I'm confused here. You said above that I was correct that I should see the changes live in the sim as I'm making changes using the Initial State KeyFrame. Here, you're saying to test the new position of the jetways, I have to restart PD3 to see those changes. I'm confused here. Why is there a line running across the sentence - "the P3D must be restarted so that all data is correctly recorded by SODE." Are you saying that the sim must be restarted before I see the changes?

I didn't mean to confuse you with the crossed out sentence, Ken.
I had edited my post a bit later and didn't know if you had read it yet.
That's why I crossed out the sentence (like they used to do at school when something wasn't quite right) and rewrote it underneath.
Because the sentence below is decisive.
It is sufficient to execute SODE Reload all via Add-ons in the menu bar and the SODE entry so that the SODE objects are reloaded.

This is because when the Jetway is changed in the Live Preview, the original Jetway and the changed Jetway are superimposed in the sim.
If you switch off the live preview, you will only see the original jetway.
The modified jetway has then disappeared.
To see only the new jetway, you have to save the xml and then reload SODE in the sim.
Do not restart the sim.
After SODE has loaded the new Jetway, you can let it dock.

 

[kmanning]

Hi Ken,

I'll have to go into a little more detail.

I assume that you are using the SODE Jetways objects from Drzewiecki Design.

Yes.

Every designer of jetways uses dynamic and static ones.
Because simply using dynamic jetways would overwhelm the simulator (whether FSX or P3D) and bring it to its knees.

Every single SODE object is an AI object for FSX/P3D.
And AI objects place a particularly heavy load on the simulator.

Therefore, AI objects should be used with caution, whether AI traffic (airplanes, cars, boats) or SODE objects.

For this reason, the developer of SODE has made it so that you only see static jetways in FSX/P3D, which reduce the load on the simulator.
Only at the moment when an airplane is at the gate and the jetway is docked,
only then does the static jetway become a dynamic jetway.

I find this very interesting. The reason is because lately, my P3D sim has been crashing to the desktop for no reason. It has not been doing that. But it seems that every since I started doing this project, the sim has been crashing to the desktop. I don't know if I did something that could cause this problem. There is a file called KLGA_STAT.bgl, which I assume is the static file for the jetways or parking spots. The original airport scenery did have some static jetways. I removed that file because I wanted these parking spots to be available. Should I replace the KLGA_STATIC.bgl file back in the scenery folder or is it okay to remove it? Last night I was doing a flight and I was parked at the gate with APU running. While I was loading the FMC, the sim just crashed for no reason. I loaded the same flight again and in about 20 later, the sim crashed again, and I can figure out why it's doing that because it has never done that before. Since you explained some of this, It appears that what I'm doing has created this problem. Could this be causing my crash to desktop?

If you are using the SODE jetway objects from Drzewiecki Design, the designer could also have built in protection here (similar to his SODE xml).
So that you cannot set the jetways directly.

That's probably what has happened but I don't understand why the designers find it necessary to protect their SODE jetway files, unless it's for the reasons explained above regarding the crash to desktop. I have the Imaginesim KATL airport and I have all jetways working but it has never crashed on me. Last night, I was at KORD and the sim crashed to the desktop after about 20 minutes or so.

If you send me the SODE jetway objects, I can try this out on my site.

Okay, I'll do that.

So far I have tried it with the jetway objects from ImagineSim_KATL, AS_PANC and the jetway from the SODE Demo SimObjekts.
With all these Jetways, the Initial State KeyFrame setting works for me as it should.

Maybe I should try the SODE Jetways using the ImagineSim_KATL.

This is because when the Jetway is changed in the Live Preview, the original Jetway and the changed Jetway are superimposed in the sim.
If you switch off the live preview, you will only see the original jetway.
The modified jetway has then disappeared.

Yes, I have noticed that.

To see only the new jetway, you have to save the xml and then reload SODE in the sim.
Do not restart the sim.
After SODE has loaded the new Jetway, you can let it dock.

Okay, I see now. I just reload the SODE Jetway in the sim using the SODE, Reload All, from the Addon menue. I've tried that and I see the change. So apparently, one does not see the changes being made why making changes using the Initial State KeyFrome until after the SODE is reloaded in the sim.

Ken.

 

[Bushpilot]

Hi Ken,

You can reactivate the KLGA_STAT.bgl and see what happens.
You can also check which jetways still work with SODE and which don't.

I have the feeling that we have talked past each other with the static jetways.

I'll try to explain it a little differently:

1.)
There are jetways as pure 3-D objects.
They are placed in the scenery at the airport, just like a building.
They are in the scenery folder, look good but don't work.

2.)
Then there are the jetways from FSX/P3D.
For performance reasons, these are only visible from a set level of detail of “DENCE”.
Only from “EXTREMELY_DENCE” are they all visible.
They are also difficult to redesign and look the same everywhere.

3.)
And then there are the SODE jetways.
The developer has to build and design these himself (hence perhaps the protection).
For performance reasons, only static jetways are shown here at first.
Even if you are standing at the GATE and the jetway is still in its home position.
Only when the jetway is docked does the static jetway become a dynamic jetway.

The SODE Developer Guide under SODE Placer Workflow Step 6A states the following:
"For large projects with many jetways, it is a good idea to provide static jetways. The dynamic jetway has all the bone animations data included and placing lots of them hurts performance in the sim. A static jetway is the solution.
SODE will switch from the static version to the dynamic jetway once the user selects the parking stand through the menu or via GSX. Therefore, the static variant of the dynamic jetway must match the pose you have set for your initial state of the dynamic jetway (initial Keyframes).
In order to keep the number of objects low, it is better to re-use the same pose of the dynamic jetway and place that multiple time. You can add variation by playing with the main “heading” property to turn the entire jetway.
Remember, every different pose of a dynamic jetway needs a matching static variant!"

Here are a few pictures for better illustration.

SODEPlacer started and connected to sim in the LIVE preview.
Here you can see the Jetway as it is in the SODE xml.

Here you can see the changes via Initial State KeyFrame in comparison to the existing Jetway in the LIVE preview.

The changes were saved and SODE was reloaded.
Here you can now see the new position of the Jetway in the sim.

Here you can see the entry of the static SODE Jetway in the SODEPlacer, which belongs to the dynamic Jetway.

And here is the static jetway in the sim.

This picture shows the dynamic jetway after activation for docking.
As you can see from the previous image, the static jetway has a completely different position to the dynamic jetway.
This causes the jetway to jump from static to dynamic.

ImagineSim is very user-friendly with its jetways in KATL.
They have one dynamic jetway in three paint schemes (as you can see from the existing texture folders) and four static jetways (as you can see from the model folders) in the same paint scheme.
If you now open a static model folder, you will see the mdl name and this contains the Initial State KeyFrame entries for the dynamic jetway.
So that static and dynamic Jetway are congruent.

AS in PANC only uses a static jetway,
You only change the appearance by changing the heading of the entire jetway.

What about the jetways from Drzewiecki Design?

You can also experiment with the jetways from ImagineSim to see whether you also see changes in the LIVE preview when you change the Initial State KeyFrame, even before you reload SODE.

 

[kmanning]

Hi Mike,

I'm about to forget to send you this file. I think this is the one you're referring to:

 

[kmanning]

Hi Ken,

You can reactivate the KLGA_STAT.bgl and see what happens.
You can also check which jetways still work with SODE and which don't.

I problem did not make this clear but this file only allows a static aircraft to show up at some of the parking spots. That means if there's a static aircraft parked at gate B23, you would not be able to use that jetway parking spot. It's not a SODE static jetway file.

The thing I've noticed regarding the KLGA SODE is that there is no static jetway file in SimObjects. But the ones for ImagineSim KATL has the static jetways. I've imported the KLGA AFCAD file, selected the SODE KATL Static Jetway SimObject file and saved it as an XML. It basically does the same thing as the SODE KLGA SimObject Jetways. The problem with KALT Jetway is that it does not have a pod underneath as the KLGA jetway has. What I don't understand is that why does the Properties Static Sim Title box keep saying "Not Defined"? Why doesn't it have a file name like yours?

Ken.

 

[Bushpilot]

Hi Ken,

Many thanks for the file.
The dynamic SODE jetway from KLGA can be set with the SODEPlacer via the Initial State KeyFrame and I can also see these changes in the LIVE preview (as in my example images from post #48).
I only had to create a sim.cfg for the Jetway and place a texture in the texture folder.
The only thing that is very strange is that there are no static SODE jetways.
Or Drzewiecki Design has found a way to install the static SODE jetways in a different location.

In my opinion, the SODE jetways from Drzewiecki Design are completely unsuitable for conversion.
Your only option is to find a suitable jetway and use it.
Or to use the original jetways and the original AFCAD from Drzewiecki Design.

Here, for example, you can download the SODE jetways from AS as an alternative.
https://sode.aerosoft.com/?lang=en

Perhaps you should take a look at these and maybe there are some that you like more.
You do not have to install these Jetways.
Just unzip them and copy the folder in the SimObjects folder to ProgramData/12bPilot/SODE/SimObjects.
Then update the SODEPlaser library (see post #32) and then the Jetways can be used with SODEPlacer.
To just look at the jetways and make a selection, you only need to look at the static jetways (mdl file) with ModelConverterX after unpacking.

What I don't understand is that why does the Properties Static Sim Title box keep saying "Not Defined"? Why doesn't it have a file name like yours?

In the Properties Static Sim Title field you will still see “Not Defined” for a simple reason.
You have to enter the corresponding static SODE jetway in this field yourself.
To do this, you must open the corresponding sim.cfg, select your static jetway, copy it and paste it into the Properties Static Sim Title field.
You must copy the part after titel= of the static Jetway from the sim.cfg that you want to use.

Here is an excerpt from the sim.cfg of ImagineSim_KATL as an example.

Or you can copy the name of the static Jetway from the SODE Placer.
There you will find the static Jetway under Tools/Library manager/SODE Add-Ons.
You can also find this way in the SODE Developer Guide under SODEPlacer Workflow Step 6B and Step 6C.
https://sode.12bpilot.ch/?document=tutorials/sode-placer-workflow

Can you show me in two pictures what you mean by the pod under the Jetway?
A picture of the Drzewiecki Design Jetway and a picture of the ImagineSim Jetway.

 

[kmanning]

Hi Mike,

First of all, I want to thank you for all the help and information you've provided. I guess you recall a few weeks back regarding the issues I had with the double jetways at KATL. Well, I did a flight from KBHM to KATL and when I arrived at the gate, there were no jetways whatsoever. They were gone. This was caused from removing the ImagineSim_KATL3_PD4 SimObject folder and the ImagineSim_KATL3_PD4_Stands.xml file from the SODE Folder. I had to replace these files back into ProgramData\12bPilot\SODE folder in order for them to show up in the P3D. But this time, there were no double jetways as before. If you recall, there was one ImagineSim KATL for FSX and the other for P3Dv4. So, both versions must be installed in the SODE folder. So far, I'm not seeing multiple jetways as I did before.

The other problem I'm seeing now is that when I dock the jetway to the aircraft using GSX at the ImagineSim KATL, the jetway snaps and slightly rotates into a new position before docking to the aircraft, and it has never done that before. It appares that the initial state has changed slightly, but I have not placed any updated xml files into the SODE folder. This started only since I started using the SODEPlacer. I haven't made any changes to the ImagineSim KATL jetways, other than trying out the jetway files for the Drzewiecki Design KLGA. When trying the jetways out, I've cancelled those placements and made sure my updated xml files were not installed in the SODE folder. The only files remaining are the original files. Why are the jetways snapping and rotating slight into a new position when I dock the jetway using GSX?

Ken.

 

[Bushpilot]

Hi Ken,

I have recompiled the SODE files from KATL for FSX.
I have changed all relevant names in the different files.
Now there should be no more conflict between FSX and P3D.

The files in the attachment only work in FSX due to the <TargetSim ID=“FSX”/> entry right at the beginning of the xml file.
The xml for P3D already has this entry, so I changed it for FSX.
Unzip the zip file and replace it with the original SODE FSX files.

Please check the docking again in FSX and P3D.
In FSX and P3D there seem to be different parking positions in the AFCAD.
This is because the “Jetway InitialState=” entries in the xml files are different.
These are responsible for the initial position of the Jetway.