simpit1 Posted November 29, 2019 Posted November 29, 2019 Anyone who can tell me the reason of the following error message after starting one of my missions (made by mission editor). At the end of the loading screen I get a CTD with this message:
Habu Posted November 30, 2019 Posted November 30, 2019 There is a script which is missing. On that error, you can't do anything. Only dev can fix that. I'll check today, and report.
simpit1 Posted November 30, 2019 Author Posted November 30, 2019 Perfect, thanks! Do you know anything else concerning the RRR-bug (repairing-bug in case of oil-system-repairing)?
Habu Posted November 30, 2019 Posted November 30, 2019 (edited) I saw something about that but i don't remind if it was in the closed forum (if yes, it means that it's reported to the dev), or on the public forum. Do you have a process which can reproduce easily the problem ? Edited November 30, 2019 by Habu
Habu Posted November 30, 2019 Posted November 30, 2019 16 hours ago, simpit1 said: Anyone who can tell me the reason of the following error message after starting one of my missions (made by mission editor). At the end of the loading screen I get a CTD with this message: Checked and reported.
simpit1 Posted December 3, 2019 Author Posted December 3, 2019 (edited) Problem solved: I saved a mission with changed parameters (changed nations) in an other folder. I already noticed in the past that the mission editor don´t likes saving changed missions in other (new) folders (perhaps due of missing groups or else). Edited December 3, 2019 by simpit1
Alonzo Posted December 12, 2019 Posted December 12, 2019 @Habu I have had a similar problem with the 190-D9 static model, the WillySMB static model, the A20-RAF static model, and maybe the Tempest static model. I'm not sure of the cause. I have decided to avoid these static models for the moment.
CCG_bexhausted Posted December 13, 2019 Posted December 13, 2019 On 12/3/2019 at 8:39 PM, simpit1 said: Problem solved: I saved a mission with changed parameters (changed nations) in an other folder. I already noticed in the past that the mission editor don´t likes saving changed missions in other (new) folders (perhaps due of missing groups or else). I don't know if I understood your problem correctly, which seems to be solved. Does the mission saved in the new folder keep the same name as in the old one? In my case I have a working folder in the Dogfight folder in which my missions are being developed. When a mission is finished I do "SAVE AS", change the name of the mission and save it to the root of the Dogfight folder to share it. Same groups but different locations and mission names. Never encountered any difficulties.
simpit1 Posted December 13, 2019 Author Posted December 13, 2019 (edited) The difference is that I changed an existing mission (with goups etc.) and than saved the changed mission in an other folder(with an other name!). There seems to be any reasons why BOX don´t accept this methode. Edited December 13, 2019 by simpit1
Habu Posted December 13, 2019 Posted December 13, 2019 19 hours ago, Alonzo said: @Habu I have had a similar problem with the 190-D9 static model, the WillySMB static model, the A20-RAF static model, and maybe the Tempest static model. I'm not sure of the cause. I have decided to avoid these static models for the moment. I confirm for the static FW 190D9 and A20 (already reported), but it's ok for static WillySMB and static tempest. I report the static FW 190d9.
CCG_bexhausted Posted December 14, 2019 Posted December 14, 2019 18 hours ago, simpit1 said: The difference is that I changed an existing mission (with goups etc.) and than saved the changed mission in an other folder(with an other name!). I do this all the time. Just to make sure I don't make any mistakes about what you say (English is not my mother tongue): the names of the new folder and the mission are different both and not just the name of the folder? If this is the case I'm sorry I can't help you.
simpit1 Posted December 14, 2019 Author Posted December 14, 2019 No problem - I don´t need help any more. All works fine!
GOA_Walter_Nowotny Posted December 27, 2019 Posted December 27, 2019 (edited) On 11/30/2019 at 12:51 PM, Habu said: Checked and reported. Thank you. Same problem here. With this same airplane (A20) and with object FW 190D9 too At this time for records, He111, Hs.129, P38, A20 (no raf), B25, Lagg, P39, P40, Ju88, Me 262, FW 190 A8, Ju87 no problem Edited December 27, 2019 by GOA_Walter_Nowotny Add words
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now