[mobcdmoc3]

http://pastebin.com/1rTphnXR

There you go. Hopefully someone figures out what's wrong, because my shotgun approach isn't working. (Not that I was expecting it to work anyways.  )

[karajorma]

Your transports are still in a wing. Wings are designed to follow fighter/bomber AI. Putting a transport in a wing is going to cause all kinds of strange behaviour.

Disband that wing and then deal with the fallout from all the ships changing name and everything should be peachy.

[bigchunk1]

My advice is still one waypoint path per transport.

[mobcdmoc3]

My advice is still one waypoint path per transport.

I did that as part of my attempt to shotgun the problem down, and I intend on keeping it. Thanks for bringing that up 

Your transports are still in a wing. Wings are designed to follow fighter/bomber AI. Putting a transport in a wing is going to cause all kinds of strange behaviour.

Disband that wing and then deal with the fallout from all the ships changing name and everything should be peachy.

I'll get on that - Thanks for likely saving me from another couple hours of useless raging. 

[mobcdmoc3]

After about a week of perseverance and rage, the first mission to my campaign is finally complete! While away, I've also (almost) completed a second mission, but I'm just *one* step away from being able to do so.

Problem - For whatever reason, I can't get this Shivan Comm Node to get scanned. I set its cargo, went to the misc window and established it as scannable, but when I test the mission, it refuses to allow me to do so. According to the mission, it's not scannable at all. I can get cargo containers to scan, but not this thing.

I've looked at a couple other missions, and I haven't found any mistake I've made that's immediately apparent. Have I made a completely inept mistake (again)?

[mjn.mixael]

Uncheck Cargo Known? You didn't mention it, so I thought I would start with the easy stuff.

[mobcdmoc3]

Nope, I don't have that box checked. Aside from this, I've got my entire second mission functional. 

[FelixJim]

The "knossos" flag in ships.tbl is causing it, as far as I can see. Removing it seems to work anyway; I couldn't tell you why this is the case though.

EDIT: I can't remember if you could ever scan the comm nodes in "Into the Lion's Den"; I thought you could, but I can't seem to be able to on 3.6.12 or 3.6.14 RC 6 (although the mission designer did go to the trouble of setting one of them as Scannable... but he also left a few "Event Names" as well, so that doesn't prove anything.

[mobcdmoc3]

Hmm... Since I don't know how to modify tables, I think I'll just improvise a way around it.

Next problem/question - For some reason all my ship models are in black and white while I'm FREDing and while I'm testing my missions. Any idea why? It's not exactly a showstopper, but it's just a bit annoying.

[FelixJim]

I feel hesitant about doing this, because I don't know what the repercussions will be of wantonly removing the "knossos" flag, but you're welcome to at least try this:

Code: [Select]

#Ship Classes

$Name:                          Shivan Comm Node
+nocreate
$Flags:                         (  "dont collide invisible" "cargo"  )

#End
This should go in a text file xxx-shp.tbm in mymod\data\tables

Brief testing seems to show it working, at least with respect to scanning. To reiterate though - I don't know what else the flag actually does and is being removed.

EDIT: Thought it ought to have a ship class of some sort.

[mobcdmoc3]

Hmm... I think I'm going to leave the tables alone until I really need to do some tweaking.

Can anybody provide an answer as to why all the ship models are in black and white? I tried switching over my stuff to another computer, and the problem seemed to have fixed itself, but it'd be preferable to get it working on my primary.

EDIT: Nvm I'm stupid, I fixed the problem.

[mobcdmoc3]

Alright, I'm getting close being ready for a 6-mission demo release. Expect to see it within the month (as long as I don't run into any showstoppers like I just did)

The problem now, is that I can't get this freighter to undock with its cargo container. It follows its waypoints, then comes to a stop. As it stops, an undock order triggers, but the cargo continues to remain docked to the freighter, and then the freighter jumps out with it still attached.

I have tried...
- Using sexps to order an undock
- Using the initial orders boxes to set up the cues
- Adding a delay between the point at which the freighter is supposed to undock, and the point where it's supposed to follow another set of waypoints, then jump out. (5 seconds)

I'm out of ideas. I really just don't know why it doesn't want to undock.

[The_Force]

Stupid question but what are you giving the undock order to the ship or the cargo.

[Axem]

Keep in mind that undocking is a whole procedure in itself. You should use a has-undocked-delay sexp to make sure that the whole thing was completed. If undocking isn't complete, technically its still attached.

But if that takes too long for your mission or it still doesn't work, try the cargo-jettison-delay sexp, it'll release anything docked right away, no questions asked.

[mobcdmoc3]

Alright, late reply, but thanks, fourth mission is now off the ground.

Out of curiosity, why can you use TAC-1 containers when there's no GTFr Chronos to carry it around?

[Nohiki]

Because the retail creators said so, and SCP/Upgrade doesn't mess retail Also the Amazon adv. should be able to carry it, no? Then you just change the name and displayed class of the ship in FRED and you have a chrnos

[mobcdmoc3]

Alright, I ran into another problem - Chained Directives - I seem to be able to get them to work some of the time, but not all the time. Can someone give me a method that will always work? It would seem that my reverse-engineering of other missions was limited in effectiveness in this respect.

[karajorma]

How the hell are you going wrong with them?

[Legate Damar]

I will admit I have often had problems with chained events as well.

[karajorma]

Unless you're using repeats, I fail to see the problem. There isn't a huge difference between a chain and a is-event-true-delay except for repeating events.