- Messages
- 6
- Country
Hello guys,
this question was often asked in this forum but I couldn't find a solution for my specific problem.
So I'm trying to make a shared cockpit... First I tried to sync only the position/alt/heading/pitch/bank with 30 Hz. This caused big stutters and was not what I wanted. Then I read that it should be better to sync the velocity. That was a much better way and it run pretty smooth after I figured out that the rotation velocity has a unit measure problem. I read the vel. in feet per second and if I set a value it is set in meters... So I had to multiply it by 0.3048. Strange but it works.
Then I started to sync the exact position in a 1 Hz interval to correct small deviations. All of this works pretty good on ground. But then I started to lift the aircraft into the air and the next problem began that I couldn't solve until now.
So the main problem is the altitude of the aircraft. I will show that later in the videos but the aircraft climbs to much. So I decided to look exactly at the VELOCITY BODY Y variable. The values where very strange and didn't show what I expected. If I climbed I got sometimes negative values! The values changed that fast in one or the other direction (up or down) that I couldn't see any connection to the current vertical speed. I also tried the variable VELOCITY WORLD Y which worked much better but was not settable (it didn't change anything). If I insert the WORLD Y into the BODY Y it worked okay but also pitched up.
I decided to simply disable this variable and only sync velX,Z/rotX,Y,Z. This worked better (I'll show that later in the videos). But again the aircraft climbed too much. And this is now the point where I don't know what I should do. At some point the aircraft pitches up even more and more and more. I logged also the rotationZ I think (don't remember exactly but I think Z was the axis for aircraft pitch). These values looked good. Even if I have a pitch of 60° up and the rotation showed a negative value (so pitch down) the aircraft increased the pitch even more.
Video with velocity Y sync: https://drive.google.com/file/d/1EA9pPFCXh_wGOlrDftClBcByetKUao6f/view?usp=sharing
Video without velocity Y sync: https://drive.google.com/file/d/1EAQ0TR5JEdlT2d1JkMJdUHaz8q5m8jkz/view?usp=sharing
To explain it: I flew with my C172 and recorded all parameters. Then I read the recorded parameters and set them into the sim. So I'm not flying in the videos. This is all done by the program. And yeah my lineup was not good in the beginning. It's exactly how I rolled as I recorded the params. You can see in the first video that the aircraft begins to lift at about 30 kts. This is not correct and shows the strange behaviour of the velY. Later the aircraft pitches even more up than in the second video.
The second video looks a way better. The syncing on the runway is perfect. The aircraft rotates at about 70 kts which is exactly what I did. Also the left turn directly after it is perfect. The problem begins at second 40. That was the point where I pitched down the aircraft to fly very low over the terminal. But the aircraft starts to pitch up. The trim was not changed! Not in the recording of the params and also not in the video. I checked that.
The only way I could explain that to me is that the sim continues to calculate the physics and that the calculated lift or pitch is added to the inserted velocity. This could be possible because I saw the following: if I make any control inputs while my program inserts the velocity data the aircraft moves in this direction. So I can overwrite or influence the aircraft by moving my joystick. And I think that this should not be possible because the inserted velocity should be followed by the sim and not changed if I give a input and cause different calculations. So if thats right my question would be how to disable these calculations. In the P3D docs I saw the event "SIM_DISABLED" but that didn't changed anything and I couldn't find it in the MSFS docs... I also tried the freeze events FREEZE_LATITUDE_LONGITUDE_SET, FREEZE_ALTITUDE_SET, FREEZE_ATTITUDE_SET but they changed also nothing.
So yeah maybe someone can help me. Maybe I'm approaching a completely wrong way to sync the position.
And sorry for my bad English.
Thanks for your answer!
this question was often asked in this forum but I couldn't find a solution for my specific problem.
So I'm trying to make a shared cockpit... First I tried to sync only the position/alt/heading/pitch/bank with 30 Hz. This caused big stutters and was not what I wanted. Then I read that it should be better to sync the velocity. That was a much better way and it run pretty smooth after I figured out that the rotation velocity has a unit measure problem. I read the vel. in feet per second and if I set a value it is set in meters... So I had to multiply it by 0.3048. Strange but it works.
Then I started to sync the exact position in a 1 Hz interval to correct small deviations. All of this works pretty good on ground. But then I started to lift the aircraft into the air and the next problem began that I couldn't solve until now.
So the main problem is the altitude of the aircraft. I will show that later in the videos but the aircraft climbs to much. So I decided to look exactly at the VELOCITY BODY Y variable. The values where very strange and didn't show what I expected. If I climbed I got sometimes negative values! The values changed that fast in one or the other direction (up or down) that I couldn't see any connection to the current vertical speed. I also tried the variable VELOCITY WORLD Y which worked much better but was not settable (it didn't change anything). If I insert the WORLD Y into the BODY Y it worked okay but also pitched up.
I decided to simply disable this variable and only sync velX,Z/rotX,Y,Z. This worked better (I'll show that later in the videos). But again the aircraft climbed too much. And this is now the point where I don't know what I should do. At some point the aircraft pitches up even more and more and more. I logged also the rotationZ I think (don't remember exactly but I think Z was the axis for aircraft pitch). These values looked good. Even if I have a pitch of 60° up and the rotation showed a negative value (so pitch down) the aircraft increased the pitch even more.
Video with velocity Y sync: https://drive.google.com/file/d/1EA9pPFCXh_wGOlrDftClBcByetKUao6f/view?usp=sharing
Video without velocity Y sync: https://drive.google.com/file/d/1EAQ0TR5JEdlT2d1JkMJdUHaz8q5m8jkz/view?usp=sharing
To explain it: I flew with my C172 and recorded all parameters. Then I read the recorded parameters and set them into the sim. So I'm not flying in the videos. This is all done by the program. And yeah my lineup was not good in the beginning. It's exactly how I rolled as I recorded the params. You can see in the first video that the aircraft begins to lift at about 30 kts. This is not correct and shows the strange behaviour of the velY. Later the aircraft pitches even more up than in the second video.
The second video looks a way better. The syncing on the runway is perfect. The aircraft rotates at about 70 kts which is exactly what I did. Also the left turn directly after it is perfect. The problem begins at second 40. That was the point where I pitched down the aircraft to fly very low over the terminal. But the aircraft starts to pitch up. The trim was not changed! Not in the recording of the params and also not in the video. I checked that.
The only way I could explain that to me is that the sim continues to calculate the physics and that the calculated lift or pitch is added to the inserted velocity. This could be possible because I saw the following: if I make any control inputs while my program inserts the velocity data the aircraft moves in this direction. So I can overwrite or influence the aircraft by moving my joystick. And I think that this should not be possible because the inserted velocity should be followed by the sim and not changed if I give a input and cause different calculations. So if thats right my question would be how to disable these calculations. In the P3D docs I saw the event "SIM_DISABLED" but that didn't changed anything and I couldn't find it in the MSFS docs... I also tried the freeze events FREEZE_LATITUDE_LONGITUDE_SET, FREEZE_ALTITUDE_SET, FREEZE_ATTITUDE_SET but they changed also nothing.
So yeah maybe someone can help me. Maybe I'm approaching a completely wrong way to sync the position.
And sorry for my bad English.
Thanks for your answer!