Hi,

 

My VA needs to use a FSUIPC version of 4.7 and above for the flght logging software, but I can't seem to get RCv4 to work with the latest.

 

When I use the new version RC moves me to the middle of the airport, pauses the FSX and doesn't render the main box.

 

Reverting to the shipped v4.1.5 works fine.

 

Any ideas?

 

My Specs:

Win 7 x64

FSX

REX Essentials

GSX

8gb RAM

Intel Core i7 Processor

250gb SSD HDD

 

I'm at a loss here. I even tried reinstalling FSX from scratch today, but that didn't solve anything but a few scenery bugs that had developed.

 

Any suggestions would be great.

My VA needs to use a FSUIPC version of 4.7 and above for the flght logging software, but I can't seem to get RCv4 to work with the latest.

When I use the new version RC moves me to the middle of the airport, pauses the FSX and doesn't render the main box.

 

Sounds like your airport data files are out of date. Rerun MaeRunways and make sure Rc is using them. I run RC all the time with FSX and always use the latest FSUIPC -- which is 4.852, BTW.

 

Reverting to the shipped v4.1.5 works fine.

 

Shipped? Who's shipping 4.1.5? That's missing most eveything developed and fixed for fSX over the past years!

 

Test again, but with 4.852. And NEVER start RC until FS is "ready to fly", and certainly not paused. FSUIPC is unable to get all the needed data from FSX if it starts up paused.

 

Pete

These links will get you the current fsuipc4 and makerys.exe:

http://forum.simflight.com/topic/66139-updated-modules/

http://forum.simflight.com/topic/66136-useful-additional-programs/

 

After updating makerwys.exe in your FS folder rerun the RC scenery database rebuild. If on a network (RC is on a client to an FS host) then first run makerwys.exe directly in your FS folder and then run the RC scenery rebuild answering yes to the prompt regarding WideFS. If RC and FS are on the same PC answer no to that prompt.

 

Be sure your FS path entry in the scenery rebuild process is correct.

No difference. Updated both of them and I'm still getting the same results.

 

Install FSUIPC4.exe is in the c:\program files (x86)\rcv4x folder

 

 

 

Here is what is going on, I've included the rebuild of the scenery in the process, notice the change of location when I hit Start

 

No difference. Updated both of them and I'm still getting the same results.

 

Well, all RCV4 will be doing is checking that the LAT/LON it sees is within reasonable range of the "centre" of the starting airport, provided in the Plan. Since the LAT/LON supplied is not at all related to the version of FSUIPC being used, there must be something else going on in RC which I am unaware of. The problem I was trying to address in my earlier reply would have drastically changed your location, probably to (0,0), somewhere in the sea off the coast of West Africa.

 

You didn't have the Lat/Lon showing in your video -- not that I could have read it if I could. It would have been more instructive to see where the aircraft was and where it moved to by having the overhead view displayed. How far did it move?

 

Rather than show a video, use Shift+Z to display the LAT/LON/ALT and write them down, before and after. Specific and numerical data about a problem is always far more useful than a video.

 

I think this will have to be a matter for JD to address in the first instance. I cannot imagine what else he could be using other than LAT/LON, and there's no way I can determine what he is using which may have changed over the 5 years since the version he seems to still be packaging was valid!

 

I also wonder why there aren't more reports of this event here. As I said, I use RC on every flight and have never seen this. Before I can do anything to help I need JD to look at it and tell us how it could occur.

 

Regards

Pete

It's odd that with the older version of FSUIPC it works, but doesn't in the newer version. FSUIPC is the only thing that has changed to cause this.

 

It's odd that with the older version of FSUIPC it works, but doesn't in the newer version. FSUIPC is the only thing that has changed to cause this.

 

Yes, and I already explained that only JD, the author of RC, can look into it. I have no idea what else RC will be looking at for this other that the aircraft position and the airport database values. But like me he will need actual information, not blurry indecipherable videos which don't help at all. You've not even bothered to note down and tell us the different Lat/Lon values.

 

I expect JD will want an RC log too so he can work it out. Considering it only appears to be happening on your system, he will no doubt need a list of all the other add-ons you are using -- it may even be one of those causing it.

 

Meanwhile, please don't expect me to comment on videos.

 

Pete

Sorry about that.

 

Original LAT/LON: N51* 28.32' / W0* 29.16' ALT: 97.5 FT

 

After the start: N51* 28.72; / W0* 27.68'

 

It moves the a/c to the center of the airport

Original LAT/LON: N51* 28.32' / W0* 29.16' ALT: 97.5 FT

After the start: N21* 28.72; / W0* 27.68'

 

Wow, 30 degrees south, and still lands on an airport? That's somewhere in Mali, isn't it?

 

It moves the a/c to the center of the airport

 

Well, assuming you made a mistake in the above value, it means that RC is measuring the distance from the position it thinks you are at, and decides it is too far from the airport. I've no idea what measure it uses for this, but assuming you meant N51 not N21 then I reckon those are only about a mile apart, so it shouldn't move you.

 

Do you get this at all airports or only this one? If only this one, tell me which it is and which gate you were at and I'll try it here -- tomorrow now, though.

 

Pete

Sorry that was a miss type, it's N51 not N21

 

Here's a picture of before and after

 

 

 

 

 

Sorry that was a miss type, it's N51 not N21

 

As I guessed. And you missed this part:

 

Do you get this at all airports or only this one? If only this one, tell me which it is and which gate you were at and I'll try it here -- tomorrow now, though.

 

Pete

Interesting. It's just seems to be happening at Heathrow (UK2000), Geneva (FSDT) is fine.

Interesting. It's just seems to be happening at Heathrow (UK2000), Geneva (FSDT) is fine.

 

Heathrow is quite large. Tell me the gate at which you started. And try another, see if it does the same - eg terminal 1, nearer the tower.

 

Pete

I usually go from 512, which was working on the older FSUIPC. I've tried various gates around T1, T2, T3 and T5, none seem to work though

RC calculates the airport location from the geometric center point of all of the runways, not the defined center point in a table. That location is in a4.csv. If where you are parked exceeds the RC allowed distance your aircraft gets moved.

 

There have been other complaints regarding UK2K EGLL regarding this. What is after your scenery rebuilt the line for EGLL in a4.csv?

 

Also, after a scenery rebuild RC should be shut down a few seconds after you get the a4 rebuild complete message, wait a few more seconds, and then restarted. This insures the writing to HD is completed and the Win disk caching is flushed so RC reads the new values.