Not many posts regarding FSHotSFX and RD4 compatability yet ,has anyone found a work around yet, I really dont want to uninstall FSHotSFX if I can avoid it. One post I found pasted below.CheersPetei have an update. the beta tester reported:I long since uninstalled FSHotSFX. However I just made a quick KLAX-KLAS flight with FSUIPC TCASid=Type+, which is the setting when FSHotSFX is installed and running. As far as I could determine, RCV4 functioned normally except for the call signs, which were something like "Boeing Seven Whisky Echo" instead of "Southwest One Twenty-three" This sort of thing applied not only to AI chatter, but to all conversations, including clearance, taxi, takeoff and landing instructions and acks. While this may appear to be a trivial matter, believe me, these conversations sound awful in terms of overall ATC realism. i hope that helps. it looks like rc will "work" with fshotseat, but the chatter will sound awful. i guess an alternative to that would be to turn chatter off. but if i call traffic enroute, it may also sound funny.jd

Hi Pete,The report you found is completely accurate. It's the callsigns which are wrong in RC4 when using FSHotseat. Other than that RC performs as normal.No known work around at this point.All the best,John

I uninstalled my FSHot FX, since I like the call signs to be realistic more than the aircraft sounds at the airport. You have to rememb3er, if you do that, to change the FSUIPC ini file.....

I have had an idea for a workaround that might work. Perhaps someone who has both RC4 and HotSFX could try something? Once you have loaded FS, RC4 and HotSFX, then change the FSUIPC TCASID settings back to what RC4 is expecting (presumably the default option) and see if that works for both of them.

I would think you would need one or the other ,as far as the setting goes, for both programs to work.

No, HotSFX needs the FSUIPC TCASID all the time to work correctly. But there may be a compromise: Start with the HotSFX setting, and change to the RC setting when airborne. Of course you will have to accept the "awful" ATC on ground, but during your flight it will be fine. And you should avoid to hear the sound of other planes during flight anyway ;-)Kurt

OKAY guys, have a problem here after uninstalling FSHoxFX/Seat. Once starting up FS9, I get a message from FSHotFX stating that a module cannot be located/Error 2.It doesnt affect how RCv4 or FS works, just annoying. I read above that you have to do a mod to FSUIPC. How do I do that?thanks,Eric

So unless I have it wrong, its FSUIPC's ini file that is changed by FSHotSFX which alters the callsign settings?? Assuming thats correct I could use a freshly generated FSUIPC ini file and disable FSHotSFX from starting and all should be well? Does that make sense?CheersPete :)

Hi Pete,If you go to the FS menu bar, modules, fsuipc, technical tab.Bottom right is a 'Set TCAS id string from'RC requires this set to FlightI think FShotfx sets it to type+I'm sure you can change it directly in the .ini file as wellHope this helps,All the best,John