• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Two big disappointments

S

sblzei

Charter Member
Payware add-ons to my FSX include GEX, UTX, Scenery Tech-Europe, Genesis U.S. mesh V2 (Download version), plus Air Wrench, FS Panels and FSUIPC.
I am rather happy with almost of them, with two exceptions: Genesis US Mesh and FSUIPC.

The major reason for Upgrading to V2 was to get rid of the unpleasant "mesa effect", as advertised in their wb place:

"Additionally, vertical resolution has been increased from 1 meter in v. 1 to .25 meter in v. 2, which will create a more pleasing display of terrain elevations while eliminating any terracing effects seen in version 1."

Unfortunately this proved not being 100% true, as some major airports are still affected by the problem.
It must be noted that there were no instrucions how to install: I deleted V1 first, but I am not sure this was strctly necessary.
I like also to add that while UTX and GEX have provided free upgrades to thir products, In the case of Genesis I had to buy it again.

As far as FSUIPC is concerned, the hope was to be able to easily and conveniently set up the buttons in my Saitek yoke and joystick. In reality only few of them are recognized and no practical improvements are perceived over the Saitek profiler. This product is in effect useless to me. Am I missing someting in terms of capability to use it?

It would be interesting to hear from anyone who had similar experience.

Ezio
 
I am using FSUIPC to map 100% of my Saitek buttons and axes in FSX... wonder what's up with your system? FSUIPC has never given me a moment's trouble.
 
Missing drivers perhaps? If you're trying to drive a multi-button controller using a generic Human Interface Device driver, Windows won't know most buttons exist, so FSUIPC won't be able to pick them either.
 
As far as FSUIP, it has never given me an ounce of problems, and I find it invaluable.

As for FS Genesis mesh, I also went from version 1 to version 2, and I downloaded v2 for free. Never had to pay extra for the updates. It has also 'cured' most all the plateu issues you have shown within the areas where v2 files are availiable. There are some rare exceptions, and if you run into them, I'm sure Justin will be willing to take note of these for future fixes, or could provide some immediate help.
 
v2 of FSG was a free upgrade from v1, so if you paid for it again you should contact Justin and I'm pretty sure he'll make you right.

The terracing effect is different from the plateau effect and one had to look really close to see the terracing effect. If your pics are from Europe, then Justin hasn't gotten there yet. He's had to go from full-time FS Dev to part-time with work outside the home to support his family.

I'm not saying if I did or did not fill out a MS survey, but if I had the chance, then non-flat runways would be the first thing listed in the comments section...
 
Also, the terracing effect Justin is talking about has nothing to do with the airport plateaus. The plateaus are caused by FSX's flat airport background polygons, where the entire polygon has to be the same height. When the surrounding terrain is not at that specified height, you either have a platform or a hole in the ground. Terracing, however, occurs as FSX interpolates elevation points in the mesh, so on what would otherwise be a smooth slope is now a terraced effect.

Hm, just saw Meshman's post, we are saying the same thing :)
 
it took me a while to configure all buttons in fsuipc and the saitek yoke and an extra throttle . you must be doing something wrong . contact me via pm if you need assistance
 
Sorry guys, but I brought up the term 'plateau', and should have uses the term 'terracing'. Posting too fast this morning before getting to work :icon_lol:
 
Thanks you all for the replies.

Just to be more specific: the airports on the screnies are SEA-TAC (Wa), Everett (Wa) Paine Field, and Santa Barbara (Ca), but I had the same effect with some Mid-West State Capitol airport as well. I understand the reason for the "terrace" (or mesa, or whatever you wanna call it), but I assumed that V2 would somehow blend the surrounding terrain in order to have a smooth transition.
It is also true that the majority of US airports are not affected by this problem anymore.

As far as FSUPC is concerned, I'm trying to:
1) solve a problem represented by "differential brakes" that come on as soon as I touch the pedals, despite a setting that should provide plenty of free play (70%) to the braking action and - of course - a separate axis for the rudder
2) program the set of toggle switches on the joystick to adjust the radio frequencies.
I gladly accept the offer of atf 300 for a private lesson.

Thanks :guinness:
 
HI sblzei,

Just to let you know. here is a screen shot at KSEA on my rig:

ksea.jpg


No terracing on my rig, none at KPAE (Snohomish/Everett) either (one of my favorite airports). I also landed at Santa Barbara not too long ago, and again, no not remember any terracing issue there either.

Thus, perhaps you need to re-check your install.
 
Very interesting!

3 questions then:

1) Is your version Download or DVD (supposing it makes any difference)

2) Is it possible that a modification to V2 was made lately? - My download was in April 09

3) how / where did you install it exactely?

Thank you :ernae:

Ezio
 
I download all my software, including FS Genesis.

I installed v2 the same time they were released (within days), again via the download option available on the FS Genesis website.

I let the original install 'do its thing'. Justin has the installer place things were they should be, with no manual input required by me. FS Genesis was one of the first add-ons I purchased for FSX. The v2 updates were all installed by hand, simply finding the correct folders to put them in. Quite easy as they are numbered by scenery section number/folder; i.e. '000' to '1107'.
 
I checked my installation.
I have downloaded auto installers .exe files named:
NADEM-X_US_ERK 914.651 KB
NADEM-X_US_NE 416.943 KB
NADEM-X_US_PLN 1.018.448 KB
NADEM-X_US_SE 597.598 KB
NADEM-X_US_WC 539.830 KB
NADEM-X_US_WRK 791.317 KB

They seem a little too small for providing full .bgl's to the respective areas; I previously unistalled V1, was it supposed to be kept?

I tried to unistall / re-install NADEM-X_US_WC, but the problem still persists.

BTW: Santa Barbara Mun. is OK. My 3rd screenshot is Monterey (Ca), sorry for the mistake
 
You must log in or register to reply here.
Back
Top