Some bugs due to latest update ...

[TOViper]

few bugs rised:

 

when starting an user made mission:

.) p7/p2 is already at 1.22 when entering mission, not touching anything on the stick; have to move slider forward and then rearwards to set it to 1; never had this before.

.) trim is set to 7 nose up. always was near 0; why?

.) bombs in RR mode fall too far again (got better with last or the one before last update)

.) after exiting missions DCS crashes every time (every!)

 

what happend? :noexpression:

Edited June 27, 2018 by TOViper

[RagnarDa]

I’ve set the throttle to full mil on spawn now (that’s why you have to move it, I don’t have to move it much though). I’ve changed the trim to 3 degrees default now, will be in next update.

[TOViper]

few bugs rised:

 

.) after exiting missions DCS crashes every time (every!)

 

 

Thanks for the quick reaction!

 

 

Relating to the crashes:

 

After figuring out this and that I can report that I had crashes when flying the F-15 only as well. So it might not relate to the Viggen, but to DCS in general.

 

Just a side note:

I reverted back to 2.5.0 15365 meanwhile to figure out this and that.

[TOViper]

I’ve set the throttle to full mil on spawn now (that’s why you have to move it, I don’t have to move it much though). I’ve changed the trim to 3 degrees default now, will be in next update.

 

 

Hello RagnarDa,

 

the trim set to 3° is a very good idea I think if the aircraft is on ground.

Does this work for respawned situations in flight as well?

 

I'm just thinking about your idea: does it really make sense to implement 100% power for aircraft in flight and for aircraft on ground? If aircraft is on ground with 100% power, the aircraft will instantly move, ... I would rather prefer idle power. I loved the behaviour from the past and when entering a mission, where the aircraft is on ground with just idle power set ... it gave me the feeling of non-dramatic non-stressed behaviour of the aircraft. :smilewink:

 

Just a side note & question: In a level-D simulator I saw that the flight crew had to set the correct lever positions depending on the initial condition of the next lesson (in most cases they moved it back to flight idle), because the simulation takes into account the setting immediately after starting. It reads the setting, and then sets it in the simulation. This is not DCS behaviour, isn't it?

 

Other question: Is there a mechanism in your code for setting the correct trim for a given mass and airspeed?

Edited July 3, 2018 by TOViper

[RagnarDa]

Hello RagnarDa,

 

the trim set to 3° is a very good idea I think if the aircraft is on ground.

Does this work for respawned situations in flight as well?

 

I'm just thinking about your idea: does it really make sense to implement 100% power for aircraft in flight and for aircraft on ground? If aircraft is on ground with 100% power, the aircraft will instantly move, ... I would rather prefer idle power. I loved the behaviour from the past and when entering a mission, where the aircraft is on ground with just idle power set ... it gave me the feeling of non-dramatic non-stressed behaviour of the aircraft. :smilewink:

 

Just a side note & question: In a level-D simulator I saw that the flight crew had to set the correct lever positions depending on the initial condition of the next lesson (in most cases they moved it back to flight idle), because the simulation takes into account the setting immediately after starting. It reads the setting, and then sets it in the simulation. This is not DCS behaviour, isn't it?

 

Other question: Is there a mechanism in your code for setting the correct trim for a given mass and airspeed?

 

 

 

When starting on the ground the throttle is set to ground-idle. If not it is a bug.

 

About resetting the controls: the intended behavior in DCS is that it always starts the same way so you don’t need to reset controls. BUT, I unfortunately discovered quite late in the process of coding Viggen that I had to do this manually, so I had to go back and make sure hundreds upon hundreds of variables is properly re-initialized between spawns. It has been difficult to find all so sometimes you might notice like a switch or something being in the same position as your last flight. If you see this, please let me know.

 

There is a very simple mechanism to find the trim implemented but it isn’t working perfectly (just about close enough). In F-14 I believe Swither made it so that the autopilot is on for a few seconds when you spawn, thereby trimming the plane. I’ve considered it for Viggen, just hasn’t come around to trying it out.

[TOViper]

Thanks for your statements, I think I got a better feeling of what is going on in the simulation (just don't know how to say it better).

The idea of using autopilot for trim sounds good, and I think most users will have a good feeling when entering the cockpit if mission starts in-flight.

 

... difficult to find all so sometimes you might notice like a switch or something being in the same position as your last flight. If you see this, please let me know. ...

I think(!) the Impuls/Series switch might be one of these if I'm not wrong (if this is a DH you have to spend a coffee, since I can remember this one hardly :music_whistling:)

[TOViper]

...

.) bombs in RR mode fall too far again (got better with last or the one before last update) ...

 

RagnarDa, I am sorry, I used wrong QFE settings in RR mode. I will test this a few times again with newest DCS version (I always had to use 955 hPa, but now the kneeboard says 949 hPa).

 

...

.) after exiting missions DCS crashes every time (every!) ...

 

This is confirmed whenever using the Viggen in 2.5.2.19157. No problems with F-15 e.g.

 

Kind regards,

TOViper

[RagnarDa]

If you start the DCS updater the new open beta should contain fix for the Viggen crash.

[TOViper]

If you start the DCS updater the new open beta should contain fix for the Viggen crash.

 

did it 2 minutes ago :thumbup:

 

Would love to report that it works like a charm, but in my case it got a crash after flying around and firing rockets ... dcs.log-20180706-142607.zip

 

Unfortunately this happend a second time ...

Edited July 6, 2018 by TOViper