Mission Commander beta release
-
@white_fang said in Mission Commander beta release:
@LorikEolmin best I can do is show him how is done. teach a man fishing better then give him the fish,
I he/she is interested , but experience showed that learning works best on your own ass , hard way. - with number of iterations.
It is the only truly Eureka state of mind. When you feel the joy of excellence and achievement after period of pain, then you remember it for good.Cheers
Yep. What I did and said way above.
-
@white_fang,
I did not ask about campaign conversion, or savegame (from campaign conversion).I asked if you have successfully converted any user-created Tactical Engagement (TE) scenario that was created in the KTO theater in BMS 4.35U3 to a TE that will function properly in KTO under BMS 4.36.
I donāt want you to do it for me.
I have not been able to successfully convert any TE from 4.35U3 to 4.36 in any theater (KTO or Balkans) without error by just following the 5 steps listed by Falcas in the MC conversion tab.
I have been able to convert some TEs from 4.35U3 to 4.36 in KTO, but only using a modification of the workaround first proposed by @LorikEolmin above.
I am very curious to know if any other Falcon user (aside from Falcas) has been able to properly convert any KTO TE created using BMS 4.35U3 into a functioning KTO TE in BMS 4.36 using Mission Commander Conversion Tab ā5 stepsā without receiving an āIndexOutofRangeExceptionā as described above.
There are many reasons one would want to convert/transition Tactical Engagements from a previous BMS version to the current version, mostly so anyone can play them under the new BMS version 4.36.
Regards,
Tomcattwo -
My post was before the update so the update fixed the 3D issue. Basically everything you said is irrelevant because of the new update on the 24th (day of release).
For some of us MC was pulling the database from TvT because of Alt Launcher (AL has an update now). Not sure why you are so upset. Basically everything you just said was pointless because of the update of MC and the fact you do not use Alt Launcher.
-
Calm down everyone. There have been wrong usage and there have been things fixed or sorted out in this thread.
But just for the track record, thereās still 5 people having reported the same issue of not being able to convert a TE/Cam from 4.35U3 to 4.36, despite following instructions on the Convert tab to the letter, and it is NOT resolved in the 5.20.685 update.
@LorikEolmin, @Logic, @Tomcattwo, @jayb, @Rouge1512 -
hi
is there any possibilty to change count of the store max ammo in MC -
does the latest version makes up a Falcon BMS 4.35 folder by itself?
-
@yavuz said in Mission Commander beta release:
hi
is there any possibilty to change count of the store max ammo in MCThis is not defined thus not changed in MC, but in the database, reached through the Editor. Use at your own risk.
-
Yes , unfortunately there is something bugged in conversion ā¦
Iāve tried TE_15_harm , and it throws index out of boundsā¦
But, the problem is somewhere in $tring naming scheme , so it is not drastic /// as MC cleanly loads that TE and db from 4.35 when opened for editing.
So problem is only in CONVERSION of NAMING SYNTAX ā¦ there is buffer overrun as it donāt like some names probably in āTranslateObj.txtā in MCās directory// as error clearly says that names of OBJECIVE(S) throw exception.
until buffer fills itself with garbage.BUT! . instead of crying , you could have investigate that and pinpoint it to the @Falcas ā¦ HE IS here for US , so ā¦ yes ā¦
Again sorry for screaming at you but would you please be more specific in error and bug reporting and not just like little girslā¦ itās broken daddy can you fix it .
There is a theread for proper BUG-reports , I suggest to read it and behave like that. , It makes lives easier for anyone.
Cheers eh ā¦
-
@white_fang said in Mission Commander beta release:
Yes , unfortunately there is something bugged in conversion ā¦
Iāve tried TE_15_harm , and it throws index out of boundsā¦
But, the problem is somewhere in $tring naming scheme , so it is not drastic /// as MC cleanly loads that TE and db from 4.35 when opened for editing.
So problem is only in CONVERSION of NAMING SYNTAX ā¦ there is buffer overrun as it donāt like some names probably in āTranslateObj.txtā in MCās directory// as error clearly says that names of OBJECIVE(S) throw exception.
until buffer fills itself with garbage.BUT! . instead of crying , you could have investigate that and pinpoint it to the @Falcas ā¦ HE IS here for US , so ā¦ yes ā¦
Again sorry for screaming at you but would you please be more specific in error and bug reporting and not just like little girslā¦ itās broken daddy can you fix it .
There is a theread for proper BUG-reports , I suggest to read it and behave like that. , It makes lives easier for anyone.
Cheers eh ā¦
A bit more respect please.
-
@LorikEolmin
No problem with that.But it goes to you also. Please show some respect to BUG-reporting thread
Did you file a proper bug report here, in last 10 pages? , else , then āit doesnāt workā
-
@white_fang said in Mission Commander beta release:
@LorikEolmin
No problem with that.But it goes to you also. Please show some respect to BUG-reporting thread
Did you file a proper bug report here, in last 10 pages? , else , then āit doesnāt workā
Iām not certain you should go deeper into this. If you wanted to say youāre sorry, one word is enough. If itās too hard, better say nothing.
-
@LorikEolmin Look here,
Yes it goes a bit deeper then that.Iām sayin that in 10 pages you havenāt moved from a dead spot, wasted effort, maybe a bit harsh , but its just a way it is ā¦ like women in bazar ā¦
There is no sense in commenting on a dead horse. It wont get you anywhere.On the other hand Iāve found YOU a reason in 20 minutes .
Now while you keep waiting till its fixed , you can comment further, be my guest.Iām done being āthe sameā .
Cheerio,. old bugger.
-
Timeout guysā¦
Iāve done that conversion for Baltic and Georgiaā¦ If my busy schedule allows it, Iāll try to make a video demonstrating itā¦
Cheers
-
You must be kidding us?!
What if not reporting bugs is this thread for?
First mention of the problem with screenshot: https://forum.falcon-bms.com/post/341696
Exception details here: https://forum.falcon-bms.com/post/341774
and here: https://forum.falcon-bms.com/post/342425 (screenshot)
Falcas did show up (I dropped him a PM too), so perfectly aware of the issue, he just did not see a problem with it. -
@MaxWaldorf
Video would be much appreciated.
Iād suggest starting simple with converting TE_15_harm. -
@MaxWaldorf said in Mission Commander beta release:
Timeout guysā¦
Iāve done that conversion for Baltic and Georgiaā¦ If my busy schedule allows it, Iāll try to make a video demonstrating itā¦
Cheers
Yes, as Logic said. Iām not sure a video about converting Baltic would be worth your time, as I just converted your Baltic campaign 35 to 36 within a minute with the 5 steps without any of the problems I have with a 35 TE.
-
This is your error. Good Luck
YES , it is only Korea KTO specific.ā¦ but have a thought 'bout it ā¦ THINK that someone already mentioned THIS in those previous ā10 pagesā - so Thank that āunknownā hero! for diZcovery
-
@white_fang said in Mission Commander beta release:
This is your error. Good Luck
YES , it is only Korea KTO specific.ā¦ but have a thought 'bout it ā¦ THINK that someone already mentioned THIS in those previous ā10 pagesā - so Thank that āunknownā hero! for diZcovery
I already did there.
https://forum.falcon-bms.com/post/342776Now, please, stop stirring things up. Youāre not helping anyone.
-
@LorikEolmin OH YES IT ISā¦
-only thing I didnāt do is select RIGHT differences between databases, I didnāt feel like as i donāt need it, just to prove it can be done
Presents, right from the oven: āTE_BMS_15_HARM_Planconverted.tacā
-v108 wherre availableHere you are and thank you and welcome. So you don have to bother, anymore .
Next time try harder.
Cheers ā¦/ā¦/ā¦/ā¦
-
Wow, I do hope threads like this never get leaked out to a behavioral psychologist. Reading through this from the sidelines is eye-opening and a bit scary.
But thank you to everyone that kept focusing on the issue and tried to calmly restate the problem as best they could (and those that rationally tried to debug / replicate the issue as best they could).
Thank you @Falcas for wading through this and releasing updates as well.