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!

[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

[AndyJWest]

Minor typo

No, this it TD following Oleg's standard practice. Without the typo's and iffy syntax, IL-2 would loose its charm...

I noticed the QMB bug, but otherwise the only problems I've had have almost certainly been down to my ancient PC - it was prone to CTD or reset completely for no obvious reason when running 4.09 and/or unmentionable mods, but then it did the same thing sometimes when running Firefox, so I can't say that the fact it did the same thing a couple of times running 4.10 is of any significance. I think its time to do the kind thing, and put it out to pasture...

[_RAAF_Furball]

Originally Posted by wildwillie

I have setup a 410m dedicated server (CRT=2), but when I connect I am getting a Timeout = 1 error.

Installation on the client was over a stock 4.09m installation (Built fresh and tested connection to a CRT=2 4.09m server before updating)

Installation on the server was over a stock 4.09m Dedicated server (Same one I tested above with)

Both client and server were updated. The problem I have is that only 50% of the players that have tried were able to successfully connect, and the rest all got Timeout=1 errors.

If I set CRT=0 then I can connect without any problems.

Thanks,
WildWillie

Originally Posted by _RAAF_Furball

I also have a 410m dedicated server set to CRT=2 in confs.ini and no-one can connect - they also receive the Timeout = 1 error.

CRT=1 won't allow them to connect either.

If I set CRT=0 then people can connect without any problems.

Originally Posted by 28_Condor

This problem is possibly due to a modded instalation, we had this problem trying crt=1 in our server and only, at this moment, work with clean installation in server and client side.

Negative on the MODs aspect .....
MODs have not touched the server nor my client installation at any time.
But thank you .......

A little more info to hopefully jog someone's grey matter ....
I have a vague recollection that CRT=2 wouldn't allow people to connect when I first installed DS 4.09 .... and then after an unknown period time (and making no other changes), CRT=2 did work ok.

Wait mode /ON

[dl-3b]

Originally Posted by Fall_Pink?

No hard evidence and need confirmation, but everytime when I'm on the runway and press auto pilot my Me262's engines get on fire. Other AI planes in my group don't have this feature/bug

Rgs,
Mark

Ps. edit: update, he162 has the same problem.

Confirmed.

[Genosse]

Folks!

Maybe somebody has already mentioned it but here're some "bugs" I've found after expanding a 4.09 DF mission with some of the latest 4.10 features ...



Everytime I re-edit the DF mission the previously assigned nations are gone ...



How does this work? There's no message appearing while flying the DF mission announcing how many aircraft are still left. Or ... have I missed something in the 4.10 guide?



Has this been done on purpose? Why then?



Maybe a saving bug in the FMB? Maybe some corruption while creating the .ntrk files? In the recordings of a flown DF mission the previously assigned skins to AI aircraft won't be shown for some reason ...


That's it for now ...

Don't be disencouraged by all the postings here, TD! Keep up the good work, folks!

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