Matrix Games Forums

Hey Guys,I'm new here.I've got a problem,and need some help.
In scenarios editor mode,I've set a package or mission of "land strike" and assigned multiple targets to the mission.But when I click"Create or Update flightplans" button,it says "no targets available."




Maybe it's not working to set targets in God Eye's View mode,that's the reason I can only guess.Before 1.05 UPDATE,there's no such problem,and I can assign units as targets loaded from file on God's View mode in some of my old version scenarios.Even targets can't be assign in editor mode,with lua scripts,it can still be triggered assigning targets after scenario started.
I also checked the some of the MDSP tutorial scenarios in editor mode,and found that in these tutorials you can see the other side's units on whatever side you're.

↓↓↓↓difference between these two situations as follows↓↓↓↓







does anyone have the similar problems?
anyone knows how to set the units visible or been aware of to the other side？

PS:I've tried set "unit has been spotted",but still not working
=====================================================================
=====================================================================
i created an another simple scenario. 1.do not start the scenario,just enter editor mode.
2.choose blue side,F11 open up ME.
3.you can see 2 task pools.
4.i've already assigned targets to each of the package.
5.set ToT.
now,when you click "create or update flightplans" button,you'll see what i said.

Good afternoon,

Not sure if I tried the same one but I waited a few seconds so the auto-detect ahs taken effect and the targets are shown (not being in Gods-eye view) added a take-off time and got a flightplan.
The auto-detect took a few secs to be seen by blue.
Sorry if I misunderstood.

best regards GJ

Parel803 wrote: Sat Feb 18, 2023 3:21 pm Good afternoon,

Not sure if I tried the same one but I waited a few seconds so the auto-detect ahs taken effect and the targets are shown (not being in Gods-eye view) added a take-off time and got a flightplan.
The auto-detect took a few secs to be seen by blue.
Sorry if I misunderstood.

best regards GJ

Good afternoon,even though it's midnight where i am.
Thank you for replying and trying.What you said just inspired me.I figured it out that i iust need to click the "start processing" button.Then targets will be shown in 2 secs.In that way,flightplans can be created successfully.

Thanks so much again.

A very good best practice is after making any change to missions or unit and it seems like it doesn't take, hit start for second or two. This applies to a lot of things.

thewood1 wrote: Sat Feb 18, 2023 6:19 pm A very good best practice is after making any change to missions or unit and it seems like it doesn't take, hit start for second or two. This applies to a lot of things.

That's it.But before 1.05 update,there's no problems in my old version scenarios,I could assign units as targets in God's Eye view and missions could be created successfully without hitting start. So I'm just a little confused about whether it's the update issue.

The mission is created as per old versions, but flight planner needs to know a lot more than the mission to create its flight plans (which is new in 1.05) I am guessing.

michaelm75au wrote: Sun Feb 19, 2023 2:32 am The mission is created as per old versions, but flight planner needs to know a lot more than the mission to create its flight plans (which is new in 1.05) I am guessing.

flight planner is a good thing indeed in 1.05,plans can be made in detail with precisely parameters instead of using lua scripts.I used to trigger some events with lua which was just a little bit complicated.

Parel803 wrote: Sat Feb 18, 2023 3:21 pm Good afternoon,

Not sure if I tried the same one but I waited a few seconds so the auto-detect ahs taken effect and the targets are shown (not being in Gods-eye view) added a take-off time and got a flightplan.
The auto-detect took a few secs to be seen by blue.
Sorry if I misunderstood.

best regards GJ

Yup , and in some cases newly placed or auto generated, auto-detectable flagged units can take up till the next minute (:00) marker, has been my experience over time (pre-tiny and post tiny), though often it's in a few seconds.

Logged #15044

Closing as WAD.

Had the same problem. Thanks for the solution
Curiosity, what WAD stands for?
Ciao

Had the same problem. Thanks for the solution
Curiosity, what WAD stands for?
Ciao

"Working as Designed"

So, not a bug.