4.10 Support & Bug Reporting

[robtek]

@SkyFan

To be clear, the bomb must NOT TOUCH ANYTHING, water, earth whatever, before the arming time, 2 sec., is over, to be active.

[SkyFan]

Originally Posted by robtek

@SkyFan

To be clear, the bomb must NOT TOUCH ANYTHING, water, earth whatever, before the arming time, 2 sec., is over, to be active.

Thank you again, I understand everythihg already and even edit my previous answer
http://forum.1cpublishing.eu/showpos...&postcount=147

[baronWastelan]

I did a search on every post I could find about "visibilitydistance=3" and didn't find any new info in the past year. Can a dev please list the changes in the function of this config setting "visibilitydistance=3" from 4.09b1m to 4.09m to 4.10m?

Thanks for all your great work TD!

[EJGr.Ost_Caspar]

Originally Posted by baronWastelan

I did a search on every post I could find about "visibilitydistance=3" and didn't find any new info in the past year. Can a dev please list the changes in the function of this config setting "visibilitydistance=3" from 4.09b1m to 4.09m to 4.10m?

No changings were made to that feature.
Some objects got a different entries to pop up earlier or later, but thats all.

[crucislancer]

So, perhaps someone here can help clear this question up regarding the YE & YG beacons. I content that they work exactly as instructed in the 4.10 guide. I haven’t had any problems. However, check out this link from mission4today, the post by KrashanTopolova on January 17th and after that:

http://mission4today.com/index.php?n...wtopic&t=11697

He’s saying that he hears Morse code letters from the YE beacon that are not part of the random code generated for carriers, and they these extra letters are used for more advanced navigation that wasn’t documented in the 4.10 guide. I’ve used the YE beacon quite a few times, and other then the sector code and the ID code that is generated every 10th time, I haven’t heard anything different.

Can anyone (particularly Team Daidalos folks!) shed some light on this?

[Viikate]

Originally Posted by crucislancer

So, perhaps someone here can help clear this question up regarding the YE & YG beacons. I content that they work exactly as instructed in the 4.10 guide. I haven’t had any problems. However, check out this link from mission4today, the post by KrashanTopolova on January 17th and after that:

http://mission4today.com/index.php?n...wtopic&t=11697

He’s saying that he hears Morse code letters from the YE beacon that are not part of the random code generated for carriers, and they these extra letters are used for more advanced navigation that wasn’t documented in the 4.10 guide. I’ve used the YE beacon quite a few times, and other then the sector code and the ID code that is generated every 10th time, I haven’t heard anything different.

Can anyone (particularly Team Daidalos folks!) shed some light on this?

This sounds like a case of

misheard lyrics

Letter "J" never exists in the code since it is one of the long 4 beep letters. However if pilot is right at the middle of two sectors, he might hear for example E (dot) and O (dash dash dash) from the two sectors and it is very easy to interpret this as J (dot dash dash dash) if you ignore the pause between the two letters.

[basola]

minor bug.

with a multiengines throttle, not some pitch and power values are showed into monitor.
They are changed but not showed in monitor.


engine2 pitch and same in 3 or 4.

idem in engine power 3 (or4, don't remember as well)

[crucislancer]

Originally Posted by Viikate

Letter "J" never exists in the code since it is one of the long 4 beep letters. However if pilot is right at the middle of two sectors, he might hear for example E (dot) and O (dash dash dash) from the two sectors and it is very easy to interpret this as J (dot dash dash dash) if you ignore the pause between the two letters.

Yeah, it’s pretty much my thinking, that he’s hearing something that isn’t there either because he’s mixing two letters together or he’s not translating the dots and dashes to the correct letter in the first place. His vague answers just made me think he was blowing smoke. He dropped his claims so I’ll leave it alone.

[bolox]

compass bug in JU87- all models

in old style navigation mode all is well, but on using realistic navigation option the 'wet' compass on lower left panel becomes tied to compass heading keys- displaying the reciprocal of course set

one other point wrt realistic navigation is that devicelink still displays the waypoint information- tho you could call this a feature

[Goanna]

Minor typo