Hello gents, I recentlly started using RC4 again and there are a couple things I'm hoping there is a way to tweak or something I just missed. Sorry if this has been posted but having a hard time trying to think of the right words in an advanced search on the matter...1.) I am not a real world pilot and love how realistic RC is. But, sometimes it's hard to understand no matter how many times I use the "Say again". I have the text block enabled but it doesn't work correctly. It doesn't list everything that is being said to me from ATC and when it does it always fails to enter the last digit or character in what is being sent in the green bar. For example, upon getting Clearance, ATC will end with my Squawk code but only the last digit will be shown. The entire statement is being written out, but no matter how long I have the green message bar stretched it always blanks out and only the last character is being seen. I know it doesn't keep a history which is a major bummer IMO, but there has to be some way to fix this. Maybe a setting somewhere that I have yet to find.2.) I had a flight plan with a Cruise of FL390. RC only had FL380 and FL400 available as choices. I am guessing that this is due to real world operations and having read somewhere that certain directions of travel will be at even or odd altitudes. My question is, is this why RC does that? If so, that's just too cool. If not, maybe someone can help me explain.3.) Is there a way to create a pause between ATC and the AI pilots responce? It doesn't miss a beat and the wav files are back to back without 1/10th of a second of pause. This seems to be a little thing and a very simple fix but it's the only thing (one of the only things) that bring me back to reality that it is just a program after all.Last time I used RC the sound set was different and now it is much better, but having read so much about the Meatwater pack, wanted to try it so it might just be that, that I'm not hearing pause. I will revert back later tonight and try. Also, I know how to lengthen their speach that is not the same thing. I like them talking fast, but there seems like there should be a way to create a break between ATC and the AI.None of these are complaints of course, and overall I am glad to be using it again. It sure has made me google a few terms though but am always happiest when I'm being educated and learning new things. Sad to see there still is no way to get progressive taxi (not the arrows but another addon I use, problem is that it will not load until FSX has assigned a RW or Parking spot). I have figured out a workaround so that is no longer a question anyway. I was happy to see this will be available in RC5. There are other things of course but others already mentioned them and most aren't that bad at all for me and once I get the 3 Q's above answered, I'll be more than content.Thanks guys, I appreciate the help!

If on the Controller Page of RC you select RVSM then the these rules apply as in the real world:http://en.wikipedia.org/wiki/Flight_level#Reduced_Vertical_Separation_MinimaIf not the separation increases to 2,000 feet between flight levels for opposite directions for the most part.At the time you request your altitude change RC will look at your current direction and based on mainly US rules which follow most common ICAO rules will offer you "legal" choices."2.) I had a flight plan with a Cruise of FL390. RC only had FL380 and FL400 available as choices. I am guessing that this is due to real world operations and having read somewhere that certain directions of travel will be at even or odd altitudes. My question is, is this why RC does that? If so, that's just too cool. If not, maybe someone can help me explain."

If on the Controller Page of RC you select RVSM then the these rules apply as in the real world:http://en.wikipedia.org/wiki/Flight_level#Reduced_Vertical_Separation_MinimaIf not the separation increases to 2,000 feet between flight levels for opposite directions for the most part.At the time you request your altitude change RC will look at your current direction and based on mainly US rules which follow most common ICAO rules will offer you "legal" choices.

In addition to what Ron said, a work around for flying the altitude you want (rather than what is assigned) - and I know this is truly a work around - is to be at cruise and tell the controller you're having turbulance trouble and can't hold altitude. The controller then stops nagging you, leaving you to climb or descend as you please. When you're done flying non-standard altitudes, tell the controller the turbulance is gone, and everything returns back to normal.I suppose it kind of simulates a block altitude range, except that the range is SFC - FLgazillion :)Subs

Haha, FL-Gazillion. I have a saying I tend to say to people "I've told you a gazillion times, stop exaggerating!" Thanks for the tip, I'll keep that in mind. It's not really an issue though and will leave the RVSM checked and try to memorize the altitudes since most of you probably know this by heart I'm sure. That's pretty cool to see and learn about the Reduced Vertical Separation Minima. Thanks for the link Ron. Sometimes I read things and if I don't understand it, my mind tunes it out I think (getting old ;-). Like I said before, that's pretty cool that RC determines that. I'm enjoying it a lot more this time around since I learned a lot more since the last time.Any thoughts on #1 about the text? I see it when it's first said but then it disappears. The green text line is still there but just the last letter/number to whatever was said remains. I have a knee board somewhere so could start writing it down as I hear it to be more realistic but I tend to do my simming late late at night and am too lazy at that point I guess. The main question I guess is, is that normal? Does anyone else have this problem or is it just me?#3 isn't that big a deal, I just think it would be nice to have a couple seconds of radio silence between responces. I am making my own pilot voices and I realize that it would be hard/impossible to put deadspace on each possible wav end, but I would think putting a space between one voice set to the next wouldn't be rocket science. If there is no way to make a pause between voices, maybe a blank 4 second wav that is referenced between voice changes? Edit: One other thing. Is it normal for the pilot or copilot to answer the way they do in these two examples below:1 - Upon contacting ATC to let them know I'm switching to check weather, it doesn't tell them anything, it just says "Blahblah control, United777" then ATC says to report back up when I return, but I never said anything except my callsign and theirs?2 - Just like #1 but when traffic is being alerted from ATC, they say "Turbine777, Traffic at 1 O'clock, 1-5 miles, 100 thousand", my reply is nothing more than "Turbine777". Shouldn't they be saying "Have the traffic" rather than just the call sign?Thanks again guys,

Hello gents, I recentlly started using RC4 again and there are a couple things I'm hoping there is a way to tweak or something I just missed. Sorry if this has been posted but having a hard time trying to think of the right words in an advanced search on the matter...1.) I am not a real world pilot and love how realistic RC is. But, sometimes it's hard to understand no matter how many times I use the "Say again". I have the text block enabled but it doesn't work correctly. It doesn't list everything that is being said to me from ATC and when it does it always fails to enter the last digit or character in what is being sent in the green bar. For example, upon getting Clearance, ATC will end with my Squawk code but only the last digit will be shown. The entire statement is being written out, but no matter how long I have the green message bar stretched it always blanks out and only the last character is being seen. I know it doesn't keep a history which is a major bummer IMO, but there has to be some way to fix this. Maybe a setting somewhere that I have yet to find.2.) I had a flight plan with a Cruise of FL390. RC only had FL380 and FL400 available as choices. I am guessing that this is due to real world operations and having read somewhere that certain directions of travel will be at even or odd altitudes. My question is, is this why RC does that? If so, that's just too cool. If not, maybe someone can help me explain.3.) Is there a way to create a pause between ATC and the AI pilots responce? It doesn't miss a beat and the wav files are back to back without 1/10th of a second of pause. This seems to be a little thing and a very simple fix but it's the only thing (one of the only things) that bring me back to reality that it is just a program after all.Last time I used RC the sound set was different and now it is much better, but having read so much about the Meatwater pack, wanted to try it so it might just be that, that I'm not hearing pause. I will revert back later tonight and try. Also, I know how to lengthen their speach that is not the same thing. I like them talking fast, but there seems like there should be a way to create a break between ATC and the AI.None of these are complaints of course, and overall I am glad to be using it again. It sure has made me google a few terms though but am always happiest when I'm being educated and learning new things. Sad to see there still is no way to get progressive taxi (not the arrows but another addon I use, problem is that it will not load until FSX has assigned a RW or Parking spot). I have figured out a workaround so that is no longer a question anyway. I was happy to see this will be available in RC5. There are other things of course but others already mentioned them and most aren't that bad at all for me and once I get the 3 Q's above answered, I'll be more than content.Thanks guys, I appreciate the help!

HelloIs RC4 output being sent to the Fsuipc window or the FS green bar?Is your Fsuipc set up as in this Pic

Hello, Thanks for the reply. I would ask you to reread my post since I clearly state I see the text, it works, it just goes away then the green bar stays and only the last character is left on screen. So in other words, it the last words from ATC are Squawk 1234, then the number 4 will be the only thing on screen.As for the picture, no, if you set it up that way with the bottom box checked you won't get anything at all,,, no green bar, no text,,, nothing, since every text you'll get from RC is going to be single line text.

Hello, Thanks for the reply. I would ask you to reread my post since I clearly state I see the text, it works, it just goes away then the green bar stays and only the last character is left on screen. So in other words, it the last words from ATC are Squawk 1234, then the number 4 will be the only thing on screen.As for the picture, no, if you set it up that way with the bottom box checked you won't get anything at all,,, no green bar, no text,,, nothing, since every text you'll get from RC is going to be single line text.

HelloIf you set the fsuipc otions as I posted then you are correct you will see no single line messages in the green bar, this is exactly what we want.We need all RC output to be sent to Fsuipc's multiline window as in this pic.The settings you need for this to happen are in this pic.Post a sceenshot of what you are seeing on your screen and someone here will quickly be able to sort it out for you.Also what version of Fsuipc are you using?The mention of the green bar has me confused.

In your modules folder rename advdisplay.dll to advdisplay.dxx to disable the green bar. It is no longer used.RCV5 will probably have a pause inserted between pilot and ATC comms for action/request and ack.For non-navigational/operation requests and acks such as getting weather an ack with just your call or ATC call is all that is required. Navigational/operational acks will abreviate the information. This falls under the official brevity procedures to reduce comm congestion.

Hi guys, thanks again. I have tried disabling the single line in FSUIPC, but nothing shows up for text for what the ATC is saying more than half the time with it, and without it (the green bar) I don't get anything. That's why I ended up unchecking that box to begin with. I noticed when I installed that there was no option to tell the installer "NO do not touch my FSUIPC". That concerned me quite a bit because I have loads and loads of tweaks and settings that I didn't want to get overwritten by any addon, no matter what it does haha. Anyway, since there wasn't an option to deviate the overwriting of my ini, I just made a backup and let it do it's thing. I checked the date after the installation and it was new, but after a test I saw my settings were still there (good thing, that would have been a law suit :( ).My FSUIPC is version 4.60a (4 March 2010). It's up to date. I downloaded the newer manual today at work and am re going through it right now. I'll be back in a few with a screenshot if I have something to take a pic of that is. The only thing I could show is if I re-enable the green bar so you can see only the last character of what ATC said remains there.Anywho, you guys have been great and I just need to do some more reading, testing, learning etc. I will report back soon as I have a clearer head. It's just hard not knowing what it is I "Should" be seeing. I get the RC window like in Mad Dogs pic, but I prefer to fly with IFR checked so it doesn't tell me the freq/course etc. All I want is to be able to see what ATC said from time to time, haha. Well, I'll be back in a bit, Thanks again!PS. Thanks Ron, having a space between who is talking would be a plus. I've had the meatwater voicepack in since I installed it so just removed it and made some of the voices a tad slower. I was starting to wonder if it was just me. Sometimes all I seem to here is back to back "Continue own navigation" without as much as a comma ,

It won't help you now, but in RC5 most parameters (FLs, squawk codes, etc.) will be shown in the status area of the FSUIPC window.For RC4 we recommend not turning on Display Text because it slows RC performance.

It won't help you now, but in RC5 most parameters (FLs, squawk codes, etc.) will be shown in the status area of the FSUIPC window.For RC4 we recommend not turning on Display Text because it slows RC performance.

Sounds cool. But I hope there will be an option to turn it off.

Ok, I think I was perhaps misunderstood or didn't explain things the best. I thought there was a way to have the option to read everything the ATC was saying or a history window of some kind to look up at to get info I may have missed. It looks like that isn't an option and people rather have no typed text at all? I understand them most of the time and think it's only with a couple accents where I can't understand. My hearing is too good, but I also have a problem with hearing everything too well (clinical). So even though I have my sounds adjusted with say engine volume and environment down, sometimes they all sound equally loud. For that I just now switch views to outside slew mode then ask ATC to say again and can normally then understand them. Still occasions that I don't but again that's certain accents and I'm sure if I was just more real world ATC savvy and could differentiate what they most likely would be saying I would be able to guess what was being said.As for what Scott said,,,That is one of the things I really like about RC. All it's options, and like to turn off certain things that would appear to me as cheats when practicing IFR :wink:As for disabling the green bar, I forgot but have other addons that use that area. Mostly not important info but there are occasions. I went back through the manual last night as well as these posts/pics and have it set up that way. For me it was the want of a history ATC window anyway, since if I have my comms passed to the co-pilot they will often quickly say something else or tune someone else so say again even isn't an option. Oh well, we all have work arounds that we use for our tailored needs so I just need more time on comms to find my own. I don't see it as an RC limitation, just used to the default ATC history window. It looks like I just need to get my old kneeboard out and will learn more this way anyhow. As for the sound clips I don't understand, I'm sure I will via trial and error and after finding out what I did wron/ignored at the end of flight brief :(

I'll have to check but in RC5 the parameter display already may be optionally turned off like using the IFR training option in RC4.The amount of information that is displayed, however, is very brief, not full text, and is part of your small section where your next waypoint is shown. If I recall as soon as you ack it disappears.It is not the "green bar" being discussed in this thread.

Sounds cool. But I hope there will be an option to turn it off.

Ok, I think I was perhaps misunderstood or didn't explain things the best. I thought there was a way to have the option to read everything the ATC was saying or a history window of some kind to look up at to get info I may have missed. It looks like that isn't an option and people rather have no typed text at all? I understand them most of the time and think it's only with a couple accents where I can't understand. My hearing is too good, but I also have a problem with hearing everything too well (clinical). So even though I have my sounds adjusted with say engine volume and environment down, sometimes they all sound equally loud. For that I just now switch views to outside slew mode then ask ATC to say again and can normally then understand them. Still occasions that I don't but again that's certain accents and I'm sure if I was just more real world ATC savvy and could differentiate what they most likely would be saying I would be able to guess what was being said.As for what Scott said,,,That is one of the things I really like about RC. All it's options, and like to turn off certain things that would appear to me as cheats when practicing IFR :wink:As for disabling the green bar, I forgot but have other addons that use that area. Mostly not important info but there are occasions. I went back through the manual last night as well as these posts/pics and have it set up that way. For me it was the want of a history ATC window anyway, since if I have my comms passed to the co-pilot they will often quickly say something else or tune someone else so say again even isn't an option. Oh well, we all have work arounds that we use for our tailored needs so I just need more time on comms to find my own. I don't see it as an RC limitation, just used to the default ATC history window. It looks like I just need to get my old kneeboard out and will learn more this way anyhow. As for the sound clips I don't understand, I'm sure I will via trial and error and after finding out what I did wron/ignored at the end of flight brief :(

HelloGlad you are having some success now.As for the accents that you find difficult why not disable those voices for now until you are more comfortable with the phraseology, listen to each one in the controllers page and pick only those that sound clear to you.

HelloGlad you are having some success now.As for the accents that you find difficult why not disable those voices for now until you are more comfortable with the phraseology, listen to each one in the controllers page and pick only those that sound clear to you.

Thanks, I actually am doing that and thought I had the one disabled that was hard to understand but looks like it will just be something trial and error. I have been creating my own voice for my co-pilot (just for fun), and have had to reference several other voice paks. This has been informative to see that it's not really any particular voice set, but certain sound clips. So when creating my list of what I needed to record with my voice, I wrote it all out and listened to say voice folder #13. I could understand most everything he said, but not for some airports where I then went into another voice folder (#55) and then was able to understand.I like to have as many as possible and it's really just being able to understand that person say it once, to then have it permanently imbedded into my head :)