cuervo111

That's cool! So I will try again after that, just in case.:thumbup:

Thanks again. No luck. I checked the hardcoded path is the same one as the one I have it installed. Everything looks the same as in the Desert tiger campaign. The path structure is the same. The logFile line where it fails is the same, so they look for the log in similar places. However it works with the F5 but not the Mig29. Am I really the only having this issue?

That's great news! Any idea about an approx release date? I might put my campaign on hold until it is updated.

Thanks ataribaby but that is not the issue. I did that. I just checked just in case and the two sanitize lines are commented out as usual.

Mission script error attempt to index local logfile (a nil value) Hey guys, I tried the Fulcrum over PG campaign and I got this mission script error about a logFile after the first mission. It happens every time. I haven't tried other DCE campaigns lately but this didn't happen in the past with others.

Glad to hear the Mig is getting some much needed love. I really hope you guys end up having a stellar aircraft.

Hey! I just flew M07 and I must say it was one of my favorites so far,very interesting setting! I am pretty sure everything went smooth. We got all the air defenses, both bunkers, both Hueys landed succesfully. However after landing... mission failed! I never got any feedback about anything going wrong. I just edited the mission log to pass the mission but thought it'd better to report the issue anyway.

Hi, I've flown the mission a couple of times. Both times the results were similar. The escort and sweep flights did their work and the air was clean. However Dodge came in before SEAD flights had clean all of the SAMs and some of the strike fighters were lost so the missions were failed. I think this is not really fair because the mission was failed for reasons out my control. The escort flights responsibility was to clear the skies and that was successfully achieved on time. Is it maybe an issue with timing? Maybe the strike packages should come a bit later so that the SEAD can have enough time to do their part? Awesome campaign so far anyway!

I can confirm this has now been fixed in the beta branch! Would have been nice to get some feedback from the devs though :)

Cool! :thumbup:

Not sure if something has changed in all this time but I am finding the mission unfairly difficult as it is now. From the moment you are notified about the enemy presence until the mission is failed you have just a few minutes. There are no clear instructions about where are the AAA targets. After you fly the mission a few times, you know, but knowing it feels like cheating. Last time I tried it was almost a perfect attempt. I took care of one AAA and the wingman of another. Next I dropped a bomb in one of the white buildings in the first pass while I ordered 2 to take care of the mortars. I gained a little bit of distance to go for a 2nd pass for the other building and 2 took care of some of the mortars. Like a minute later: mission failed! My bombs didn't eliminate all of the targets but they were effective. I mean, are we supposed to kill all the bad guys in the first pass? You are also notified of targets in a 3rd area (the incoming column).I don't see how you can find the time to deal with that on top of everything else I mentioned. Maybe the AI behaviour changed and now time is more limited than intended? Other than this... I'm enjoying the campaign so far!

Oh I see. It'd be great to know if it looks better now

Interesting! It'd be good to know if it's related with the map or the type of object... maybe I will try to do some more testing when I have the time

Do you think that for some reason the map objects around certain areas are not "found" by the AI? I mean: a bomb task will just bomb the coordinates, no matter what's there, so it always works. A map object attack order will bomb the closest object found. Maybe it has to do with objects not being there during the mission creation but added later? Thinking about it from a development perspective, I can imagine the get object somehow returning nothing and so the AI has nothing to attack. No idea why though... Really glad to hear you are working on a review! :thumbup:

Guys, I implemented a small change trying to fix the AI not attacking targets in Desert Tiger 76. I suspect this issue is also present in other DCE campaigns, though I haven't tried. You might be interested in having a look. The more people gives ideas about how to better solve this issue the better!

Guys, I implemented a workaround for the AI not attacking targets issue. It seems like there are actually two problems: 1. The wingmen AI have problems following the scripted attack orders. I suspect they follow your orders instead and this is just ignored. I'm nowhere near completely sure though. 2. The "Attack map object" orders do not work in some instances. I don't know why, but changing them to bombing makes the AI attack the targets 100% of the times I tried. So what I did was changing the orders to bombing and enabling the default (non scripted) attack orders (the ones you see on the map). I uploaded the change to my github. If MBot prefers me removing it from there I will of course comply. But I thought it might be useful to get some feedback and get this fixed as soon as possible.

I'm enjoying a lot the Museum Relic campaign, I guess that should give you more than 8hrs more!

Guys, any plans for a Sabre campaign? I know the era unit choice is limited but it might be cool mixing the Sabre and MiG-15 with some late WW2 warbirds or maybe even a few F-5 and MiG-21. Any thoughts?

Great news indeed. Does anyone know if they will reduce the glare too?

I noticed something weird. I actually thought my axis was not working because I wasn't seen the pedals move! If you press W you can see both pedals brake axis move in the cockpit. If you use one axis for left and another for right, it works too. However if you use a single axis for both the pedals don't move even if the brakes work.

Well that's what they say and I assume it's true. I haven't tried them online myself :)

You have actually several options: https://www.digitalcombatsimulator.com/en/files/?set_filter=Y&arrFilter_pf%5Bfiletype%5D=5&arrFilter_pf%5Bgameversion%5D=&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=154&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter

Interesting! It'd be great to hear from some developer about the issue then

I reported a bug here.

I discovered a weird AI wingman behavior that is 100% reproducible (I attach a track). Flying the Flanker, If I lock a friendly for whatever reason and then I use TWS on a bandit and issue the "Attack my target" order, the wingman will attack the friendly. It seems like the sim stores the last locked target and doesn't update it with targets tracked with TWS. I checked with the F-15 and this doesn't happen. I didn't check with any other aircraft, sorry. traitor.trk