View Issue Details

IDProjectCategoryView StatusLast Update
0000767FSSCPFREDpublic2006-02-17 16:57
Reporterjr2 Assigned ToGoober5000  
PrioritynormalSeveritytrivialReproducibilityalways
Status resolvedResolutionfixed 
PlatformMSI mobo, AMD Athlon XP 3200+OSMS WinDOwSOS VersionXP Pro SP2
Summary0000767: Import FSM file doesn't automatically look for FS1- entries.
DescriptionThe Import FSM function on FRED doesn't look for the FS1- entries (I run fred like this: ...\fred.exe -mod FSPort,mediavps -fredhtl). FRED knows they're there and you can manually change them, but if you could have it look for the same text as in the FSM file, except add the FS1- prefix to it, and only then change it to none, it would be nice. Or better yet, have it inform you of the problem and ask if you want to replace the file with an FS2 music track, or manually rename it. (hahaha, in my dreams, right? ;-) )
TagsNo tags attached.

Activities

Goober5000

2006-02-01 01:23

administrator   ~0004599

This has been fixed in CVS, but at the same time the entire import function was upgraded for v3.0 (which won't be released for a while yet). You're getting a mixed bag here, I'm afraid. :)

Goober5000

2006-02-01 06:05

administrator   ~0004601

Fixed.

jr2

2006-02-17 12:42

reporter   ~0004777

Last edited: 2006-02-17 12:42

Very small problem... the BRIEF doesn't get ported over (it doesn't add FS1- to the BRIEF music selection if it's set to an FS2 BRIEF file). I imagine this is because the BRIEFx file name already exists in FS2, so it doesn't change it. Of course, if you are importing FSM files, you want the FS1- variant brief.
Another small bug is that sometimes it forgets to import at all and sets all music to none... but I think that's just general FRED bugginess, as it doesn't usually do that if you restart FRED for each FSM file.

edited on: 02-17-06 07:42

Goober5000

2006-02-17 16:57

administrator   ~0004780

This was part of the other fix. It's in CVS; it works; I've tested it many times already. It won't be usable properly until v3.0, though, so keep your hat on. ;)

Issue History

Date Modified Username Field Change
2006-01-31 22:29 jr2 New Issue
2006-02-01 01:23 Goober5000 Note Added: 0004599
2006-02-01 06:05 Goober5000 Status new => resolved
2006-02-01 06:05 Goober5000 Resolution open => fixed
2006-02-01 06:05 Goober5000 Assigned To => Goober5000
2006-02-01 06:05 Goober5000 Note Added: 0004601
2006-02-17 12:42 jr2 Status resolved => feedback
2006-02-17 12:42 jr2 Resolution fixed => reopened
2006-02-17 12:42 jr2 Note Added: 0004777
2006-02-17 12:42 jr2 Note Edited: 0004777
2006-02-17 16:57 Goober5000 Status feedback => resolved
2006-02-17 16:57 Goober5000 Resolution reopened => fixed
2006-02-17 16:57 Goober5000 Note Added: 0004780