I don’t know if anyone has tried something like this but I thought I’d throw it out there to see what people say…
We have memory restriction issues on our current project which force us to reduce varieties of sounds on one PS3 in order to preserve the quality of the remaining varieties. This means we have to either duplicate every change we make in two seperate projects or peridoically make a copy of our PC / 360 project and then remove a couple of hundred waveform varieties from sound definitions by hand. Is there a way we could automate this? Perhaps some utility to scour thgouh the .fdp and remove the entries relating to a waveforms contained in a list?
I don’t know if others would find it useful but it would be great to have a flag on each waveform within a sound definition which determines whether it is included on a particular platform.
- JeffOfDeath asked 7 years ago
At some point they were discussing the possibility of allowing per-platform sound definitions, such that platform X could have 5 variations in a sound definition, and platform Y could have 3.
I haven’t heard much more beyond the initial ‘yes, it is on the requested features list’.
- Symbiotic answered 7 years ago
The FDP file is basically XML
you could add some text tag to the "notes" field of the Sound Definition and have an XML parsing tool perform some modification for you. Then you would have:
- Work in main FDP project file.
- Setup "notes" fields in Sound Definitions where you want less variations
- Run FDP through XML parsing tool to remove waveforms from those sound definitions
- build the other platform(s) from the automatically generated FDP file.
- mattconnolly answered 7 years ago
Please login first to submit.