4.10 Support & Bug Reporting

[Ian Boys]

Correction to previous bug report:

NDB do work with DGen but only those within about 30km of your flight path, so you need to set more than you otherwise might.

ian

[TheGrunch]

Depends on the terrain, I think, Ian.

[Ian Boys]

Originally Posted by TheGrunch

Depends on the terrain, I think, Ian.

No, I mean the NDB only EXIST within 30km or so of your flightpath. You can put them elsewhere but Dgen won't bring them into your mission unless they lie along your route.

[TheGrunch]

Originally Posted by Ian Boys

No, I mean the NDB only EXIST within 30km or so of your flightpath. You can put them elsewhere but Dgen won't bring them into your mission unless they lie along your route.

Ahhh, I see. Yeah, DCG has a similar feature with the action radius setting. Unfortunately it's very doubtful that DGen will be updated any time soon.

[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.