ITO 1.07.0v Bugs
-
@vAiCon
i installed 4.37, then ITO
started the campaign it crashed, installed balkan worked, next day 4.37u1 was released, i updated to u1 tried again new ITO campaign, crashed same error code/stacktrace, balkan still workingcrash dump on 4.37 without u1 update if that helps you
https://mega.nz/file/DYNGTKDQ#K0iStHFH59KMQpQqLHB4yaDHjUgGpEXpRtL-FYtWbEg -
@MisterOutofTime said in ITO 1.07.0v Bugs:
@vAiCon
i installed 4.37, then ITO
started the campaign it crashed, installed balkan worked, next day 4.37u1 was released, i updated to u1 tried again new ITO campaign, crashed same error code/stacktrace, balkan still workingcrash dump on 4.37 without u1 update if that helps you
https://mega.nz/file/DYNGTKDQ#K0iStHFH59KMQpQqLHB4yaDHjUgGpEXpRtL-FYtWbEgok,
Can you try flying in the main 4 campaigns ? (the first upper 4s)
I want to know if you experiencing the same there
Please use BMS 4.37 ONLY when operating ITO 1.07.0 -
@vAiCon said in ITO 1.07.0v Bugs:
@MisterOutofTime said in ITO 1.07.0v Bugs:
@vAiCon
i installed 4.37, then ITO
started the campaign it crashed, installed balkan worked, next day 4.37u1 was released, i updated to u1 tried again new ITO campaign, crashed same error code/stacktrace, balkan still workingcrash dump on 4.37 without u1 update if that helps you
https://mega.nz/file/DYNGTKDQ#K0iStHFH59KMQpQqLHB4yaDHjUgGpEXpRtL-FYtWbEgok,
Can you try flying in the main 4 campaigns ? (the first upper 4s)
I want to know if you experiencing the same there
Please use BMS 4.37 ONLY when operating ITO 1.07.0okay i will wait for a ITO version which supports 4.37U1 to test further, downgrading U1 seems to be a hassle and other theaters work fine with it atm, but i did shortly try another campaign of ITO with u1 and there the same crash did not happen but after a hour of flight ish the game froze
-
Something weird I noticed.
Was flying some ITO80s on 37.1 (I know the theater hasn’t been updated yet, but it seems to be working fine). Chose Runway start to save some time but noticed my HARM table was wrong and decided to hit ESC + D to go back to 2D, fix it and commit again.
After doing that wingman took off normally and communicated instead of staying on the ground.
Don’t know if it helps in any way though.
EDIT : Did another flight and tried it again. Reproducible. Load in to 3D, discard the mission and recommit to the same flight. AI wingman will now join you on the runway.
-
@unkindled Interesting… not sure what the cause could be in the theater, since afaik HARM tables are only set in the CALLSIGN.ini.
Does the issue appear in a specific campaign or TE, or when departing from a specific airbase? -
@RUSHER0600 I might not have phrased it that well. I forgot to change my HARM table accordingly, so I went back to 2D to fix it and re-commited to the same flight. By doing so the persistent “wingman doesn’t take off” issue didn’t occur.
Ι didn’t mean to say that the HARM table didn’t load correctly in 3D, but that I seem to have found a workaround to wingmen not taking off.
-
First flight in ITO 1.07.2 and 4.37.2 and got instant CTD when requesting taxi back to ramp in ITO80s.
Crash dumps : https://drive.google.com/file/d/13FIB3c-CgTQciotTMNVSDJa5QbC59B_q/view?usp=sharing
-
I am getting the callsigns and bearing formated as dates instead of the actual values.
-
@javo Look for the file located in C/falcon 4.37/Data/add-on-israel/Sounds/F4Talk.csv in the lines number 2164,2331, 2337, 3245 may be your error.
When you clear the error respect every comma and every space, follow the pattern when typing or your atc will be absolute chaos -
@unkindled said in ITO 1.07.0v Bugs:
First flight in ITO 1.07.2 and 4.37.2 and got instant CTD when requesting taxi back to ramp in ITO80s.
Crash dumps : https://drive.google.com/file/d/13FIB3c-CgTQciotTMNVSDJa5QbC59B_q/view?usp=sharing
Hope you got it right,
Probably error with the Updater, try installing the full installation.@javo said in ITO 1.07.0v Bugs:
I am getting the callsigns and bearing formated as dates instead of the actual values.
Noticed that as well, Investigating
Thanks for the report -
@Apolo27 what do I have to look at that lines? I dont understand, did not touch that file previously.
-
@javo If you haven’t touched those lines, it means that everyone has the same problem, don’t worry, the developer of the theater is aware and knows how to fix that bug.
The solution to this bug is in the file and in the lines of code that I mentioned before, but if you are not sure about doing it, I recommend that you wait for the fix. Greetings
-
This post is deleted! -
SU-22/17 glitch
Guys, the afterburner on Su-22/17 seems to be “invisible” (the AB is ON but there is no visual on the burner).
Same thing with Landing gear and Flaps
-
@VDK said in ITO 1.07.0v Bugs:
SU-22/17 glitch
Guys, the afterburner on Su-22/17 seems to be “invisible” (the AB is ON but there is no visual on the burner).
Same thing with Landing gear and Flaps
will check asap
-
@vAiCon said in ITO 1.07.0v Bugs:
will check asap
Some other things…
Fly the Su-22 and let the aircraft go faster… You will notice also that the airbrake opens (but with no effect on speed), also the wings do not sweep back.Apply rudder and you will see that the left slat opens
The LOD model for Su-17/22 are GORGEOUS, but this details are a little hard to deal with
Anyway, thanks!
-
Missing Aircraft ITO 1980s mission editor (add squadron/add flight):
F-16C Blk 32 EAF (Aggressors)
MiG 19
MiG 23ML
-
@Bloodhound161 Thanks for reporting that, fixed in the next release
@unkindled Did it happen again and were you able to reproduce the CTD upon requesting taxi back to ramp in 80s?
-
@RUSHER0600 I haven’t managed to fly ITO80s lately as I’ve been mostly flying in UOAF, so I can’t help unfortunately.
-
@unkindled Gotcha, no problem. I guess it’s the same old bug that happens sometimes in the ATC brain, unfortunately hard to repro.