I've been having a strange problem with S-Gear in Reaper that I just cannot figure out; any help you can provide would be most welcome!

I recently updated to the newest version of S-Gear and I'm using it as a VST3 in Reaper. For this particular track, it's just drums and guitar with S-Gear assigned to the guitar track. I've also been using S-Gear in Reaper for many years and have never encountered this issue before.

I've recorded the track, and playback in Reaper works fine with S-Gear assigned as VST3 on the FX block and sounds totally correct.

When I go to mix down and render the finished track, however, Reaper is only rendering the amp model on the track -- the 2 Room Thing reverbs I have assigned on that preset are not rendering, so I'm left with the dry guitar signal with The Duke amp only, alongside the drum track.

I've tried printing the FX onto the actual track using a number of methods (freezing the track, rendering the track, applying FX to the track as a new take), but in all instances, the Room Thing reverbs are still not rendering, only the amp model. But if I play back the original, unrendered track with S-Gear enabled on the FX block, everything sounds as it should.

Has anyone else encountered this before? It seems very strange, I can't quite figure out the best next step and like I said, I never had an issue like this until the recent upgrade.

I'm using a Scarlett 2i2 interface with a Windows 10 PC, 16GB RAM and i7-9700 processor.

Which version of S-Gear are you using? Please make sure that you do indeed have the latest S-Gear v3.0.3. The problem described was fixed in v3.0.2,

Thank you Mike -- so it turns out I'm not losing my mind, and I thought the most recent version was 3.0.1. I'll upgrade tonight to 3.0.3.

Make sure you're recording the output of the track, not the input. (Reaper default)

Also check that you're recording OUT Post FX.

I'm not sure how you're not getting the reverb but still getting the amp, unless you've disabled it in the preset?

Mike was correct -- it was a bug that had been fixed in a prior update that I wasn't aware of.

But also, you don't have to record the output of the track in order to "print" the FX usually -- you can do that by applying the FX to the individual take, basically "printing" it onto the track after you've dialed in all your FX. Doing it this way allows you to reamp or make whatever changes you want until it's time to render. That's what I've always done, and it always worked until I encountered this problem -- but it's fixed in 3.0.3.

hi all - i found this thread when having the same problem in my Mixcraft DAW... so i upgraded to 3.1.2 and it seem to be fixed... but now it's happening again... what is the nature of the bug?

thanks