Log in to reply
 

No Afterburners in Rockstar Editor [Add-on Aircraft]



  • I have a problem where afterburners do not show up for add-on planes in recorded clips in Rockstar Editor. This recently started to happen and I'm quite perplexed as to why this happens because they show up in-game, and there have been instances where afterburners show up in recorded clips.

    PLEASE NOTE: This is not to be confused with scrubbing backward through a video which results in the afterburners disappearing temporarily.

    I am using the following mods:

    • @SkylineGTRFreak B-1B Lancer.
    • B1bhelper.cs is installed in scripts folder (Works as intended in-game).
    • GTAV_CarpetBomber.dll is installed in scripts folder (This isn't the problem).
    • AirFleet.dll and AirFleet.ini is installed in scripts folder (Not sure if this has anything to do with it).
    • Scene Director is being used for my video (This seems like it could be a probable cause, not sure).

    This issue is hindering my progress with this video project. Please, I'm kindly asking anyone who thinks they can figure it out to help me resolve it.



  • @Richie01 What happens when you take the ones you think might be causing the problem out of the equation... i.e. move them out of the scripts folder?



  • @LeeC2202 It seems to me that it might be Scene Director, everything else works fine when in the scripts folder and when removed for testing purposes to rule out the problem. I'm not 100% certain that it is the main cause but it happens arbitrarily when I use SD. I made the video anyways. I'm still hoping someone can resolve the problem for future purposes.



  • @Richie01 I might be able to help you a bit more on this, seeing as I have encountered a similar problem during my latest mod.

    ParticleFX exist over time, so they need to generate and then develop to a certain stage in their lifespan. As I have discovered with the smoke in my helicopter mod, if you disrupt the flow of the timeline, you can break the particle generation. Using fine scrub on the timeline will do it and once they have gone, you have to go back along the timeline, to give them chance to recreate themselves.

    With the particles in place, you should be free to edit cameras and move around and as long as you keep an eye on things, the particles should stay intact.

    So as a test, I would suggest you record a clip as normal with the afterburners on, let it play straight through in the editor, see if they remain visible. If they do, play the clip through again and at a time of your choice (when you can see the afterburners on screen), add a marker and see if you can edit the camera with them intact. If that works, then try using fine scrub from that marker, see if that causes them to disappear. If it does, go back to the start of the clip and play through again, to see if they return.

    Let me know how you get on, because I was recording some sample clips last night with generated particles and found them very delicate to work with. Your problem might be completely different to what I encountered but I thought it was worth sharing my experience with it.



  • @LeeC2202 Thank you for your explanation, however, I'm familiar with what you described. The issue I had (I'm sure it'll re-occur in the future) just did not show any afterburner lights at all in the editor no matter what, even when I allowed the video to play in game-camera mode It's as if the burners weren't even recorded at all (so strange).

    Fortunately, I managed to record one scene of the KC-10A refueling plane and the B-1B Lancer together with the afterburner lights showing. It took me several tries, say for example -- 9 out of 10 times I had to redo the scene setup, check in Rockstar Editor to see if it showed up or not, and each time it didn't show up I restarted the game.

    This problem is still unresolved, but I don't need to worry about it for now since the video is now complete. But for the future...I need this fixed. :sweat:


Log in to reply
 

Looks like your connection to GTA5-Mods.com Forums was lost, please wait while we try to reconnect.