Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: C.U.P. The Jet Age Advanced Mission Builder glitch  (Read 1311 times)

0 Members and 1 Guest are viewing this topic.

lennygo

  • member
  • Offline Offline
  • Posts: 16
    • SAS
C.U.P. The Jet Age Advanced Mission Builder glitch
« on: January 02, 2017, 04:26:54 AM »

So i already did a post yesterday and now its even weirder,

yesterday i couldnt get quick mission to work now it works fine and also all the planes do work fine but I used advanced before that which worked and there like 60% of the Planes dont actally work and when the mission is loaded it just says Mission:null(or Zero Null is for me i think because im german and null is pretty much Zero) if anyone can help me with this would be greatly appreciated cus in AdvancedMissionBuilder i can do way more complicated stuff than in the Quick one.
Logged

SAS~Monty27

  • SAS Team
  • member
  • Offline Offline
  • Posts: 3851
  • Action and Adventure!
    • SPEEDMACHINE
Re: C.U.P. The Jet Age Advanced Mission Builder glitch
« Reply #1 on: January 02, 2017, 05:42:17 AM »

It sounds like you have edited the Quick Mission Builder mission with Full Mission Builder.  This is entirely correct and the best way to get more of them working.  There are extensive discussions on QMB and FMB in the C.U.P. Manual and the new B.A.T. Manual.
Logged

lennygo

  • member
  • Offline Offline
  • Posts: 16
    • SAS
Re: C.U.P. The Jet Age Advanced Mission Builder glitch
« Reply #2 on: January 02, 2017, 12:24:18 PM »

No i did actally not edit any Quick missions with Full i just made a lot of missions myself
Logged

western0221

  • Modder
  • member
  • Offline Offline
  • Posts: 6790
  • Live in Japan
    • IL-2 itaki blog
Re: C.U.P. The Jet Age Advanced Mission Builder glitch
« Reply #3 on: January 02, 2017, 12:32:27 PM »

Some jets have FMB default loadout problem mismatching the text between "default" and "Default".
FMB may want it as "default" by all small letters.

In example, F-4 might have more problem with postfix _P4 ? (or something I forget) like "Default_P4".

I advised modders to keep "default" loadout name for all the planes, but still remain problems or rolled back my change solving the problem in projects.


But even those troublesome planes, you can easily avoid the problem only choose another loadout like AAM or bombs in FMB loadout dropdown menu.
Logged
Pages: [1]   Go Up
 

Page created in 0.034 seconds with 24 queries.