Southern Region map v13 [1.51]
Re: Southern Region map v.9.0 [1.38.x]
Thank you slider for the link.
Re: Southern Region map v.9.0 [1.38.x]
@Sergey061
Please, tell me the logic behind calling the development of SRMap for ETS2 v1.40 for 10.1beta
and then when finally releasing it's called 10.0 final. Then when checking the manifest it says
10.0beta!!! Is this an Aprils fool joke?
Пожалуйста, расскажите мне логику вызова разработки SRMap для ETS2 v1.40 для 10.1beta, а затем,
когда она наконец выпускается, она называется 10.0 final. Тогда при проверке манифеста написано
10.0beta !!! Это дурацкая шутка в апреле?
Please, tell me the logic behind calling the development of SRMap for ETS2 v1.40 for 10.1beta
and then when finally releasing it's called 10.0 final. Then when checking the manifest it says
10.0beta!!! Is this an Aprils fool joke?
Пожалуйста, расскажите мне логику вызова разработки SRMap для ETS2 v1.40 для 10.1beta, а затем,
когда она наконец выпускается, она называется 10.0 final. Тогда при проверке манифеста написано
10.0beta !!! Это дурацкая шутка в апреле?
Re: Southern Region map v.9.0 [1.38.x]
I asked the developer the same question, he replied - " everything is new, I just forgot to update the manifest"
Re: Southern Region map v.9.0 [1.38.x]
@valyta2
Yes, but still, why calling the development phase 10.1 and then release a final version numbered 10.0,
that is no logic to me. I'm 76 years old, senile, blind on one eye, crippled from not being active physically
during this horrible pandemic, but mind you I CAN COUNT still!
Yes, but still, why calling the development phase 10.1 and then release a final version numbered 10.0,
that is no logic to me. I'm 76 years old, senile, blind on one eye, crippled from not being active physically
during this horrible pandemic, but mind you I CAN COUNT still!
Re: Southern Region map v.9.0 [1.38.x]
Hello guys, after I load the newest final version of SRM v10.0, I found a problem, which will make the time of profile loading very long. In order to find out the problem, I only use promods, rusmap and SRM. If I use beta version of SRM, the loading time is very short. My friend also mentioned this issue. By viewing the log file, I found out what may caused the problem, this problem also appeared in Version 1.2.1 of the red sea map, and now it was fixed. The error information has been put in the screenshot. If I remember correctly, Sochi belongs to SRM. I hope this problem can be fixed as soon as possible. Thank you very much.
Re: Southern Region map v.9.0 [1.38.x]
@altria1
I can tell you that TGS v2.0 has the same problem, it generates a red cross where the problem is
in the World Map view, so this may be a conflict with a third map, Promods anyone?
I can tell you that TGS v2.0 has the same problem, it generates a red cross where the problem is
in the World Map view, so this may be a conflict with a third map, Promods anyone?
Re: Southern Region map v.9.0 [1.38.x]
Yes, the same as above.. That the developers conspired, or what ? :)
Re: Southern Region map v.9.0 [1.38.x]
@valyta2
No definitely NOT, but Promods has had problems with FLD prefabs this version too,
and those have impact on other maps causing troubles.
No definitely NOT, but Promods has had problems with FLD prefabs this version too,
and those have impact on other maps causing troubles.
Re: Southern Region map v.9.0 [1.38.x]
Hello BenganJ, I'm sorry I don't know the error code very well. But this problem does exist. With SRM V10.0 final version, the game builds a new nav-cache on every start. And every time I load the profile without change any mods I loaded before, the game will show "Content change detected, Updating navigation data, Please wait" But if I use beta version of SRM, it has no problem and the profile loads very fast. I'm almost sure that the new version of SRM has caused a long time to load the profile.
Re: Southern Region map v.9.0 [1.38.x]
@altria1
It could still be an impact from another map mod, but stay tuned, I'm sure the problem will be solved!
It could still be an impact from another map mod, but stay tuned, I'm sure the problem will be solved!