Khopa

Hello, thanks for reporting this, it is the same error for both of you. It will indeed happen when "No night mission" is selected. (and when the current time is the middle of the day.) I fixed it for the next version, sorry for the inconvenience. Just disable the "no night missions" when it doesn't work. Yes, it's an issue right now. I'll try to make the factions files editable in the future; currently they are packaged in the exe, which is not practical. You are right. On the Western Georgia map, the airbases are really close to each other. For modern conflict, it's too close. Especially when the nearby airbase has an S-300. If you have the Persian Gulf map, the spacing on the "Iranian Invasion" campaign makes it way more manageable. But i'll definitely make a new "map" for Caucasus with more spacing, that's a good idea. Yes, using late activation trigger would improve performance over the current delay method i'm using for now in the generated mission. (It was just more straightforward to do it this way, but i intend to improve that). Regarding performance, I've also added a small menu with a few performance oriented settings coming in the next release, it's not much for now, but maybe it'll help a bit :

Thanks ! I managed to reproduce the issue. I hadn't tested in a while and it's due to recent modifs i made to awacs generation. Since the third reich had no AWACS in 1944 it's causing a crash. I will fix for next version. There is no way to workaround it in the current build... :/ Thanks, I'll think about it, maybe it'll make more sense to make a new thread, since it's quite different from the original DCS liberation. I don't know.

Thanks to everyone for the feedback and kind words. In fact it is not needed for single player. As this is a pre-release, and i'm doing all my test from launching from the ME, i prefer to advise people to do the same for now. But it is needed for multiplayer. In fact, if you try to host the mission on a server, if you have not opened it and saved in the mission editor before, all the flights that are supposed to appear later will spawn immedialty. Which results in .. chaos, to say the least. Destroyed SAM units should not appear in the generated mission that you see in the editor. (units are tracked individually, so for instance if you destroy the radars for a SAM site, the site will spawn without them, and will be almost useless) For strike target buildings, they are also tracked individually, but they will still appear in the ME and in the mission as the destroyed version of the same Static object. Make sure to close/reload the mission in the ME if it looks exactly like the previous mission. (When you close the mission, and the end game screen in DCS after laucnhing from the editor, it will reload the mission editor with the same mission that has been played, even if the mission file has changed on disk.) Yes, you should see them, that's weird. Do they appear in the Mission Editor ? But i've also noticed a possible issue in the Mission Planning UI. When you add a new flight, it does not select it immediatly, so if you go the waypoint tab immediatly, you'll end up editing another flight waypoints. Maybe that's what happened ? I'll fix that so that the created flight is immedialty selected. That's weird as well. Have you created custom payloads in the ME in the past ? I believe it should not, but maybe your custom payloads are conflicting with the one provided in DCS Liberation. I'll try to reproduce. Right now, to avoid issues with taxi/atc all the AI units will start in the air. This is current limitation. However your flight should start as you decided. Which airbase was it ? You can try the Normandy map with US (1944) vs Germany (1944), it is kind of working, and will generate FLAK site and use the WW2 units. But i have not heavily tested it, i'm not really proficient in WW2 aircrafts. However the support is not the best right now, and there is a bug where Shilka will appear near enemy objective in RC5. It is also missing the latest units that were added in WW2 asset pack. It is very kind of you, but I would not be confortable taking donations. The code is still based on the work shdwp did before. I did rewrite a lot of things, and the philosophy behind the mission generator is now really different from the original vision, but it is still shdwp orignal project. And it also rely heavily on the pydcs library, and also a bit on the Lua MIST framework. So, really it would not have been possible without these libraries, and the work of shdwp on the original DCS Liberation.

Are you sure ? You should be able to see them, can you provide a save file ? My bad, there is an issue in RC5, the predefined frontline waypoint is not exactly where it's supposed to be, it's probably why you are unable to see it. It will be fixed in next pre-release version.

Hello guys, finally got my ED forum account to work. So, there is a lot of questions, i'll try to answer them. It is because the flight you have selected is not supposed to start immediatly. If you want to avoid this message, put Departure time at "T + 0 minutes" in the flight planner : Otherwise you may indeed have to wait a while. Can you provide a screenshot ? Are you sure you are not using the old version ? (It was a common issue in the old UI) And there is now a scrollbar for the flight list on the new version : Not yet, sorry. But you can run from source and edit the "factions" files if you want. But it's bit more complicated, and i'm not sure the dev guide is up to date. Be sure to check out QT_UI branch on github, the master is still on the old tkinter UI. Github repo is there : https://github.com/shdwp/dcs_liberation/tree/qt_ui For the A4,it's a plane i'd like to include, but it will have to be done in the "pydcs" library, which is the main dependency for this project that provide the airplane datase and such. Thanks, it means a lot. But let's not exagerate, it's nowhere close to the greatness of Falcon BMS campaign. :D I will eventually add performance settings, it is on my todo-list. It can indeed get really busy, and this is why, the "recommended" maps are rather small. In the old version, RED were defence mission iirc. It is not done this way anymore in the new UI. Coming soon :) But you can already set up your own, see : https://github.com/Khopa/dcs_liberation/wiki/Tutorial-04-:-Setting-up-a-custom-%22Strike%22-mission The first number (15) is the number of aircraft on the base, the second one (17) is the number of frontline ground units. I want to improve the base information screen in the future, it's far from perfect right now. I'd say add a CAP flight, departing a bit before yours, with it's waypoint on the frontline, then another on the nearby friendly airbase, then a new one to the frontline. And so on, so it loiter around for a while. There is not really a clean method yet, it needs improvement. Or just trust the already planned AI CAP flights, most of them will take off, and loiter around for a while, engaging all ennemy targets in range. Maybe i will add an Escort flight generator in the future, because i want it to be really simple for the user. Are you sure ? You should be able to see them, can you provide a save file ? Do the AI planes spawns with inappropriate loadout as well ? What was your flight "TASK", and what the payload you got if you did not check "use custom loadout" ? Basically,an F/A-18 BARCAP should have a Spamraam config, CAS should have Mavericks, and STRIKE should have bombs. You can see the default loadout files in "resources/customized_payloads" folder and modify them if required (but it can be really tedious, believe me ).