FSDreamTeam forum
Products Support => Chicago O'Hare for FSX/P3D => Topic started by: axiom13 on March 15, 2008, 05:21:59 am
-
Im a Chicagoan and really want to purchase this product. I noticed that the taxi and runway textures bleed, and there are double gates at all the parking positions, one moves into postion and a copy stays in the same place. Is this just a fault with the demo, or the whole product?
axiom
-
I can not reproduce the problem of jetway doubles, try to restart windows it seems a FSX problem on charge of scenery, for texture, the terrain on kord has a resolution up of 30 cm pixel, but to view this on full glory, you must set the slider on fsx relative at the terrain resolution.
regards.
-
I tried reinstalling, downloading the installer again, but nothing works, and I also changed the resolution setting but the runway, taxi, and apron textures still bleed.
And another funny thing happens, and I think the installer should be checked or removed because when the trial version ends for me nothing disapears...
Im thinking that the problems might go away when I buy the product?
axiom
[attachment deleted by admin]
-
You have another scenery or double entry for same area, please verify your scenery library.
Regards.
-
I still have the runway texture bleed though prob. i have no duplicate ORD installed, and also set the texture to 30cm and the prob is still there
-
No double scenery
axiom
-
No double scenery
axiom
Please try to find another afcad files active for Kord on your FSX
-
I did have one, and i got rid of it, but this did not get rid of the problem. I also tried reinstalling, but nothing.
axiom
-
Let's not confuse the two issues:
- Runway/textures bleeding, it really looks like a double scenery. Maybe it's just the default popping out for some reason ? That might explain why you had the impression the Trial didn't really "end", perhaps you were seeing the default scenery ? I just checked soon after you posted that message, I assure you that the Trial works: after 5 minutes you should only see the ground and jetways, but no buildings, except from some in the peripheral areas.
- Jetways that doubles when you activate them. This is not caused by another scenery, and I can see this as well. We are investigating, it looks like either we found an FSX bug or undocumented behavior, and it looks like it *might* be related to the complexity of the AFCAD file. We are looking into it.
-
I completely reinstalled FSX clean (nobody likes doing that ;)) happy to hear that im not the only one with the jetway problem, hope you guys will be able to fix it soon because im getting my credit card ready ;D
That might explain why you had the impression the Trial didn't really "end", perhaps you were seeing the default scenery ? I just checked soon after you posted that message, I assure you that the Trial works: after 5 minutes you should only see the ground and jetways, but no buildings, except from some in the peripheral areas.
Im serious, the message which states that the trial ended would show but the scenery wouldn't change. Now since I reinstalled FSX the trial version is working, the scenery disapears. Just thought you guys should know...
axiom
-
I have the full version bought and i have the bleed through problem.
-
I have the full version bought and i have the bleed through problem.
As axiom13 can confirm, the bleed through it's nothing related to OHare, it must be some other scenery in conflict or a leftover from another scenery that wasn't properly uninstalled, that's why the issue was solved for him by reinstalling FSX.
Also, there are no differences whatsoever between OHare Trial and full, other than the limited time. But of course, one can't expect our installer would scourge the whole PC for installed sceneries that *might* conflict with it and delete them.
-
Hi All ;)
Have DL the new AFCAD file for FSX
and still have the problems with the double Gates on the 777er gates ( there i can see this Issue )
Another thing :
For proper docking the gates at the AC i have to edit all my entry edits to other points
because they not fitting your setup from the gates
So allways i go for a "FSX Airport" i have to open the aircraft .cfg and set the orginal settings back
and the other way i fly to KORD i have to set the spezial entry i made for KORD !! ( and there realy a lot off different planes to do ) ???
Can this be done better ?? You have to think allways where you fly and have to set the right exit entry in the aircraft .cfg .
Quite circumstantially isn`t it !?
And another:
Can you do some ( from all off them ) Parking Ports with the FSX Pushback and Bagage Vehikle so you have a use off them too ??
That would be great :-*
regards
Mario Görs :D
-
Have DL the new AFCAD file for FSX and still have the problems with the double Gates on the 777er gates ( there i can see this Issue )
We said it probably depends on the AFCAD file, and we are working on it, never said that the latest AFCAD already fix it. When and if we find a way to fix it, be sure it will announced.
For proper docking the gates at the AC i have to edit all my entry edits to other points
because they not fitting your setup from the gates
Are you referring to the default A/C or a specific 3rd party one ? The gates (other than the doubled jetway issue) seems to work fine on default A/C.
-
Hi :)
> Are you referring to the default A/C or a specific 3rd party one ?
tried it with the FSX A321 and IMO it wasen`t at the right Place
And sorry what means 3rd party one ?
If i set my normal FSX gates for the 3rd party one the gates are docking perfect.
So if you use the same setup as the FSX Engine there should be no difference there.......................... :-\
or.........
regards
Mario ;)
-
tried it with the FSX A321 and IMO it wasen`t at the right Place
I still don't understand what is the problem you are having. The jetway is handled by FSX, you can park slightly forward or backard, the jetway will always reach the airplane's door.
And sorry what means 3rd party one ?
Addon airplanes not included in FSX.
If i set my normal FSX gates for the 3rd party one the gates are docking perfect.
??? Now I have to ask you what do you mean now, by 3rd party...
So if you use the same setup as the FSX Engine there should be no difference there...
Exact, it shouldn't. I guess we are not fully understanding each other. Can you please be more specific ?
-
how is a double scenery possible when all i had before was a KORD cross wind runway afcad which is now deleted
-
Try to use AFCAD program, search for KORD, and check how many AFCAD you have. You should have 2 at most, the Stock (default) and ours.
As you can see from axiom message, he solve the issue by reinstalling FSX. Not that this should be normally necessary, but if one is not able to find the offending scenery in any other way, reinstalling might be the only option. As I've said, we can't certainly search all your hard drives for files that *might* create problems to our scenery in order to be able to delete them.
This is only related to the textures bleed through. The double jetway problem is an entirely different issue we are looking into, and it looks like an FSX bug.
-
I take it back, the texture problem is being caused by the O'hare ground textures. When they load, the runway and apron textures bleed.
-
It's not, because we can't see any bleeding.
Which products you also have that might have an effect on ground ? UTX perhaps (although we tested it with UTX)
-
Yes I have ultimate Terrain X. I run with no autogen
-
Yes I have ultimate Terrain X. I run with no autogen
Please try with autogen
-
will there be a difference? Ill try anyways, but currently im in the process of reinstalling. Just to happens that i have needed to reinstall for quite sometime now, but havent had the motivation or cause until now.
-
It might. We observed some issue with Zurich as well, when running with no autogen at all. Try the lowest complexity setting.
-
OK, Im very confused. I reinstalled FSX clean, then SP1 and SP2. Right after I installed O'Hare.
Now, the jetway problem is gone, but the texture bleeding is back. I have nothing installed but O'Hare, no other scenery. When I made my first statement saying that the bleeding is gone, this was because XGraphics from HiFi got rid of the FSdreamteam apron and taxiway textures. When it would load I didn't notice until later that the cement blocks didn't load and there was no apron texture, so I now beleive that the apron textures are causing the bleeding. About the jetway problem, it comes and goes. Very confusing...
axiom
-
Have you tried to temporary fix for the double jetways problem we just posted ?
-
I have not yet tried the fix for the double jetways. i have not yet had an issue with double jetways yet, but i have just completed my complete reinstall of fsx and still have the issue. autogen on normal.
-
Can you please try it with that fix posted ?
Regardless of the fact you never had double jetways before, it *might* be related to your issue, since the jetway thing was caused by a *bug* we think to have discovered in FSX handling of scenery exclusions, and the fix is a workaround for that bug, it might have an impact on the texture bleeding as well, because something wasn't excluding correctly.
We are not sure, because we can't see any texture bleeding, that's why I've asked you to try.
-
Just tried with the newer afcad, and no luck. Runway tire marks are bleeding all through out the runway.
-
JETWAYS WORK!!! but sadly tire marks, and apron markings bleed. Again, freshly installed FSX with SP1, SP2, and nothing but O'hare installed, and it still bleeds.
Sorry, but my first remark about the textures not bleeding was wrong because there were no textures loaded and I didn't realize until later. The markings would load, but the apron cement wouldn't so nothing would bleed. Now that the cement does load the markings bleed but thanks for the jetway fix
axiom
-
JETWAYS WORK!!! but sadly tire marks, and apron markings bleed. Again, freshly installed FSX with SP1, SP2, and nothing but O'hare installed, and it still bleeds.
That's really strange. As I've said, we can't see it, and right now you are the only 2 users reporting it.
It might be something that appear only with a specific setting, then. What is your current mesh setting ?
Another issue why such issue might appear, can be related to z-buffer problems. More specifically, too few bits and/or not enough precision for z-buffer calculations, sometimes due to a video driver bug or settings. Have you ever used a video card tweaker ? Are you running in 32 bit color mode ?
-
What do you suggest I change?
[attachment deleted by admin]
-
Try starting with Mesh resolution set at 38 or 19 meters.
Texture resolution should be set at 30 cm if you want to enjoy the full resolution the scenery was designed with. This might not solve your issue, but it will look surely better.
On the video card, you might want to look if there's something related to z-buffer. Sometimes those settings can be only accessed by a tweaker. But start with FSX settings first.
-
Can you recommend a tweaker that can get me to z-buffering? Thanks
axiom
-
yes 32 bit, settings medium high: level of detail: large, mesh 65, mesh resoultion 76, texture resolution 1m, scenery complexity extremely complex, autogen none, advanced animations on special effects max, ground shadows off
-
Hi :)
Hello FSDreamTeam :D
Might that be possible :?
Can you do some ( from all off them ) Parking Ports with the FSX Pushback and Bagage Vehikle so you have a use off them too ??
That would be great
regards
Mario Görs ;)
-
Hello all ;)
I can confirm with the newly downloaded Afcad file
the Double Gates Prob is gone on my PC :-*
Thanks a lot for that fast Support on that one ........... 8)
regards
Mario Görs ;)
-
That's really strange. As I've said, we can't see it, and right now you are the only 2 users reporting it.
Make that 3, it's with the trial, I was already set to purchase this product when I saw this problem. (Texture Bleed) At first I thought it may be caused by 3rd Party Mesh, that was a problem with Fly Tampa's KSEA for FS2004 which had a similar problem on systems with FSG Mesh installed (Like mine). Since the others though have reported this still happens after a fresh install, that's now unlikely the problem. I'm running Windows XP FSX SP1 on an E6850 3.0Ghz 2GB 1066Mhz PC2-8500 Mem and a Geforce 8800GT. Also I'm noticing stuttering similar to what I see in Orlando, but it seems worse at Ohare. I have to believe it has something to do with your copy protection and add-on manager, as I don't get it anywhere else in the FSX world, including other 3rd Party sceneries. Only the ones using this addon manager!
-
Hello again :)
> Also I'm noticing stuttering similar to what I see in Orlando, but it seems worse at Ohare.
That happens to me also.......
Tought it was something else - but as you say that ,looks like it has to do with the scenery / Add on Manager
That are short hard stutters coming up after a minute or so and keep on doeing as you around the scenery - so can confirm that.
cheers
Mario ;)
-
We are trying to identify the cause of the problem that is affecting you 3-4 people (out of several hundreds that already bought it ), and we WILL get to the source of the problem, just like the double jetways issue.
But please, do not start any more nonsense about the "protection" might have caused this. It doesn't make any sense.
First, the Addon Manager is not there to handle just the protection but, more important, if we didn't had it, you would had to say bye-bye to THIS level of detail with THIS level of quality.
A scenery like this and as big as this, it's NOT doable without the Addon Manager, certainly not with FSX SP2, due to the lack of LOD for scenery objects (a "bug" that appeared in FSX SP2), the we put back with the Addon Manager, together with a lot of other distance-based optimizations that developers used in FS9 and that can't be used in FSX anymore, but we have by the means of the Addon Manager.
And, just to prove the case more clearly: your texture bleeding is happening on *ground* and, incidentally, ground textures are the ONLY thing in the scenery that is NOT handled by the Addon Manager! The ground is made using a combination of native FSX photoreal terrain and FS9-styled detail layers. The Addon Manager doesn't know, doesn't care, doesn't interfere with any of that.
So please, if you want your problem searched and solved, like the double jetways problem we JUST fixed (that one was instead affecting everyone), the discussion about the Addon Manager ends here.
-
I'm sorry, I shouldn't have mixed the 2 issues, I wasn't referring to the Addon Manager causing the texture problem, but I do suspect it to be the cause of the stuttering. I've had this in the Orlando scenery, the trials in other cloud9 sceneries, which I didn't buy because of it. I thought I'd give this one a try, and saw the same thing! The one thing these sceneries all have in common is the addon manager. I do like the quality of Cloud9, and your FSDT scenery, but this stuttering problem is real annoying. I could actually live with the micro stutters on the tarmac, it's on approach where they are more severe (especially after a long flight) that is the real problem. Other High Quality 3rd Party airport scenery like UK2000 does not exhibit this behavior.
-
The Addon Manager can't cause any stuttering due to texture loading. It doesn't know about texture handling at all. This is done entirely by FSX engine.
Starting with the fact that not everyone see it, stuttering might be caused by a lot of things.
First, other "high quality" scenery might not use FSX texturing at all, but it can simply be FS9 visuals used in FSX. It's quite obvious that, a simple diffuse texture not only takes much less space in memory than a texture with diffuse+specular+bump, but also its shader can be slower to execute or, better yet, triggering a state change that *might* cause stutters, if the graphic settings are put too high (the system, being already overloaded, can't process drawing calls fast enough). A scenery with a flat FS9-looks, that is drawing everything with the same shader, will not have this problem. But then, what's the point of using FSX...
Other problems might cause stuttering, is the added load of AI airplanes, especially legacy FS9 models. This, when used in *combination* with a scenery that instead uses fully compliant FSX 3D objects (like we do) forces FSX to keep switching between its two different rendering paths, the FS9 and the FSX one. If one does everything FS9 style, the problem might be lessened. Of course, only until a fully FSX compliant AI package comes out...
Another reason for stuttering might be exhaustion of the Video RAM. This can happen on cards with less than 512MB, especially when used in combination with AI packages with lots of *different* liveries. The constant switching between AI models textures COMBINED with the airport scenery textures might cause the video card to struggle, the less VRAM the more the struggle. Solution here is the usual: LOWER your settings, the most important ones are the Global Max Texture size (decreasing it one notch will lower memory requirements 4 TIMES! ) and the Scenery Size, if it's put to "Large" you really need a lot of VRAM to handle the scenery.
Other reasons for stuttering might also be external ones, not related to FSX. For example, a big issue is Vista file indexing and automatic defrag. That is the N.1 source of problems with anything related to disk loading. If you constantly see your hdd light flashing while you are flying, most of the times it doesn't have anything to do with FSX, but instead is the Vista file indexer and the automatic defrag that is running on its own. I always shut down these services, it really makes a lot of difference in smoothness.
Of course, all this doesn't have anything to do with the Addon Manager. The fact you are seeing with our sceneries more than with other, it's only because we use very high detail textures, with many of the advanced FSX properties.
-
Well lets just say, whatever the cause of the stuttering it only happens with Cloud9, and now FSDT scenery (At least on my system) and as such is a show stopper for me from buying any further scenery. I do have Orlando, and I do think the quality is top notch, but the stuttering on approach ruins what otherwise is a very smooth flight. Less so on departures, which is what I now use this scenery most for. As for my system, it's a Dell XPS 720 E6850 3.0Ghz 2GB 1066Mhz PC2-8500 Memory, and a Geforce 8800GT 512MB card. I do keep it well tuned, and defragmented using Ultimate Defrag keeping the FSX folder together at the outside of the Disk. I do use WOAI AI Traffic at 100% and get frame rates in Orlando about 25 with non complex aircraft, and about 18-20 with LDS-767! Other than the stuttering, I can't complain about the performance. I also had this problem on my previous system (which got fried in a lightning storm) which was a Gateway FX530XG E6700 2.67Ghz, 2GB Memory, and Dual ATI X1950XTX Crossfire cards, and also got high frame rates in FSX.
-
Frame rate and stuttering are entirely different matter. In fact, it's very possible that, the higher demands put on the system to generate more fps, eats more bandwidth to handle the background tasks of handling objects and textures, that might result in stuttering. One might get better results with a little bit *less* fps, and get less stuttering.
The parameters you might want to play with are:
TEXTURE_BANDWIDTH_MULT, setting it too high can cause stutters.
PoolSize, default is 1000000, increasing to 5000000 might help
The Addon Manager has an easy way to tweak these values without having to work on FSX.CFG directly.
-
I do not have a shuddering problem or a 3rd party mesh installed. But do u think it would be easiest to create a mesh just for the airport? Would really like to get this working. The tire markings seem to be the thing that is bleeding most.
-
May I please know which texture files are the apron, taxiways, etc (but not the markings)? Like I said before, X Graphics from HiFi somehow got rid of these files, so that the were no textures under the markings, just fsx ground. The tire markings were still there and the apron markings also, and nothing bled. When I realized that the apron textures were gone, I got rid of XGraphics, and reinstalled O'Hare. The apron textures were back, and so was the bleeding.
Lets have the other 3 people also remove those texture files to see if their bleeding stops, and thus we have the culprit.
Also, shadows bleed, Im really thinking that the apron textures are causing all the bleeding.
(And how can I access z-buffering?)
axiom
[attachment deleted by admin]
-
Texture themselves can't cause any bleeding, it's the conflict between the altitude of ground *polygons* that use those textures that can create the problem. In FSX, removing a texture will make an object disappear so, one might have the wrong impression of having fixed the problem, but it lost the object as well.
An altitude conflict might be created by:
- Another afcad that is still active
- Another mesh that has been put on top of Ohare. The scenery has an embedded native FSX flatten to prevent this so, if it stays on top, it will be able to flatten all terrain elevation underneath, without any need to provide a custom mesh.
- Another scenery with ground polygons. If a scenery range was badly programmed, even a scenery on the other side of the world might create issues at KORD.
- Video card with not enough z-buffer precision. z-buffer settings usually can only tweaked using tweakers.
I would like to point out that I'm still unable to reproduce this problem, even by playing with FSX settings, there's absolutely no bleeding or visible flickering.
The issue that might happen with XGraphics might be a different one, but it's not really a bleeding, it's more like a see-through. Since they replace default runways textures with their version that, for runways, includes details like tire markings, since we *also* have tire markings, but on a different layer and in much higher resolution, it's possible that you might see both, if KORD is used with XGraphics. But that wouldn't look like a bleeding. And, it should work the opposite as observed, meaning it should only appear with XGraphics enabled.
-
I do not have any addon meshes or anything, I did have a addon airport texture pack but I tool it out to see if it would effect the problem, but it did not. Ohare is at the top of my scenery library.
-
I got rid of Kord_apron.bgl, and most of the runway bleeding stopped, accept for at runway intersections when they overlap. Markings seem to bleed when the overlap each other also. Taxiway markings bleed when those little line things overlap the markings.
What tweaker would you reccoment so that I can adjust this z-buffering thing?
axiom
[attachment deleted by admin]
-
What tweaker would you reccoment so that I can adjust this z-buffering thing?
You can try RivaTuner.
-
i have riva tuner. what setting would i have to change? also what is z buffer and what would it do to the scenery?
-
Where can I find the z-buffer settings?
axiom
-
DirectX settings->LMA
However, I already tried it on my system (nvidia 169.25 drivers), I can't make the bleed to appear, with either setting.
-
i have the nvidia 169.75 drivers
-
is this it?
[attachment deleted by admin]
-
Yes but I already tried it, make no difference: I can see no bleeding with any of the settings. Which drivers are you using ?
-
so what do u think is gonna need to be changed in order for this to get fixed?
-
As I've said, we still can't see it, regardless of the setting. I've already listed some things that *might* cause such problem but I'm going in the blind because nobody else except you 3 guys are reported it. Have you tried with other video drivers ? Have you tried resetting video drivers to default ?
Another thing that can be tried, is removing the FSX.CFG from the %APPDATA%\Microsoft\FSX folder, so FSX will recreate a new one with all default settings.
-
idk dude, i just completly reinstalled fsx, fresh cfg etc and its still there. I have no other traces of an O hare scenery. I use UTX and their landclass, and have a few other tweaks. I perosnally dont think the issue is driver related. i have done everything that i have been suggested to do and the prob is still there.
The support that has been provided is great!!! thanks
-
and have a few other tweaks
which ones, exactly ?
I perosnally dont think the issue is driver related.
But have you tried another driver ? That's far easier than reinstalling FSX from scratch.
-
just tried with the new drivers 169.25, and still no luck
the only tweak that i have installed is a different autogen descriptions. TEXTURE_BANDWIDTH_MULT=1600
[TERRAIN]
TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=900
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=1000
-
how do I figure out what driver im using?
axiom
-
open riva tuner and look at the second box on the bottom that says "forceware version"
-
Im using 163.69.
Im very upset and angry. I went to the screenshot section and just felt very sad. Everyone is enjoying their KORD, and Im stuck here trying to fix it. I've been planning to do a flight, LOT Polish Airlines 767-300 EPWA (Warsaw)- KORD for months. Thats the first flight I ever flew on in real life, I was 2 years old. Thats when I immigrated to this country I love, where I can do anything I desire (like acctually become an Airline pilot, unlike in Poland where I would be stuck in a small town) I had temptations to do the flight with the default KORD, but kept on telling myself that Im going to save it for the FSDreamTeam KORD.
Now that I gave you my lifes story :), any new developments on fixing this problem?
axiom
-
Im using 163.69.
This is relatively old, can you try with 169.25 or 169.21, that I think it's the latest with WHQL certification ?
-
IDK what else to do, i have 169.25, the latest version of rivatuner and ntune, fresh install of fsx. and i still have problems. Really dissappointing that i cant get it to work correctly. I guess a possible solution would be raising the runway markings up off the other textures, but i still get bleeding around the edges of the aprons as well. I would really like to get this fixed.
-
ok i installed the 169.25 driver. is there a new setting that will get rid of the bleeding?
axiom
-
ok i installed the 169.25 driver. is there a new setting that will get rid of the bleeding?
Assuming your are running in 32 bit color, both in the desktop and in the sim, the only setting that *might* have an impact, is only accessible via RivaTuner tweaker program, and it's the Z-buffer compression, under the LMA tab.
But, as I've said, I can't see no difference at all, I can't see any bleeding with either setting, even by playing with FSX settings like mesh complexity or switching between DX9 and DX10, I still can't see anything wrong.
That's the whole point of the issue: if we were able to reproduce it, it would have been already fixed, just like the double jetways.
-
any new developments on fixing this problem?
The key here is for me being able to reproduce it. We might try another thing: can you post your FSX.CFG here or send it to me via email, so I can try it on my system with exactly the same settings as yours ?
-
Here is my cfg
[attachment deleted by admin]
-
And here is mine. Could it be that im using Vista 64?
[attachment deleted by admin]
-
If this is elevation related, how can that be adjusted. And how was this scenery made that the texture could bleed? I have alot of other sceneries and they don't bleed. Zurich doesn't bleed, why would this scenery bleed?
axiom
-
If this is elevation related, how can that be adjusted.
As I've explained already, the scenery has an embedded FSX flatten inside the BGL and it should flatten any ground elevation, regardless which mesh is used underneath, in the airport area.
And how was this scenery made that the texture could bleed? Zurich doesn't bleed
Zurich has FS9 style ground. OHare is using FSX native terrain + a detail layer. That's the main difference in how the ground is made between the two.
Maybe this difference could trigger a different behavior, but that only happens under very specifics settings of *your* machines, that we haven't discovered yet.
-
What do you need to know about my specs? I really want to resolve this problem.
axiom
-
alright, so still there is now solution. this is now getting annoying that we keep providing information for u, but yet there is nothing that can be done about the problem. maybe just to do a current hot fix for the prob, do the terrarin the zurich way.
-
I've tried with both your FSX.CFG files, and no problem at all, no texture bleeding.
maybe just to do a current hot fix for the prob, do the terrarin the zurich way.
What you are suggesting is simply not possible. There are reasons why we did Chicago this way, and Zurich the other way. Apart for the fact that it's not even sure if this IS indeed the cause of your problem, what you are suggesting it's not an "hotfix", it's a rebuild from scratch of the whole ground scenery, that doesn't make any sense to do since it's works like it is now for basically anyone else.
There is a reason why we offer a Trial, and we said, many times already, the Trial is *EXACTLY* like the full version except for the lapsing time. If you had the problem during the Trial, and it annoyed you like you are saying it does, you shouldn't have bought it in the first place. What's the point of having a Trial, if not for test the product on your own machine and hardware/software configuration ?
At this moment, we simply spent too much time already on a problem that affects just 2 people and can't be reproduced in any way. The only thing we can do is to offer a refund, if you want one, even if, considering there was a Trial, it's way more that we are supposed to do.
-
virtuali,
im not giving up that easily. I haven't purchased this product yet, but like I said, Im a Chicagoan, and I never was so excited about a FS add-on. Can you please supply me with your full specs and cfg file and ill try to copy them.
axiom
-
I've tried your CFG, and it doesn't show any bleeding, so I don't think it's an FSX setting.
However, I use a C2D E6700, 4GB Ram, nvidia 8800 GTX, and Vista 32. But I don't think this really matters, since we have hundreds of other users with probably thousands of hardware combinations who don't see the problem either.
If this might help, I *do* recall having seen this kind of bleeding a while ago, but not on KORD (back then, we didn't had any KORD to test), it happened on FSX default scenery, and only in DX10 mode. It doesn't happen anymore so, I guess it was a driver problem that was fixed when updating drivers along the way.
-
but could the problem be that im using vista 64? because i have nvida 7900 gtx, 4GB ram, intel pentium 4 processor CPU 3.80 GHz
axiom
-
Many other users are using Vista 64. Our graphic designer, Francesco ( Kappa on the forum), uses only Vista 64 and he did all the scenery ground textures. I think if the problem was Vista 64, he would noticed it by now.
He also uses a GeForce 8 so, might well be a driver bug that affects only GeForce 7 series and only under Vista 64 perhaps only with a specific driver relase, that's why we haven't heard so much of it.
-
Im sorta giving up right now, Im going to try and contact nvidia, see if they can help, and if not, I don't care, Im still going to buy this product, waited too long not too, ill just have to deal with the flickering. thanks for trying to help though.
(One last thing, I don't have acceleration, might that be it?)
axiom
-
(One last thing, I don't have acceleration, might that be it?)
If you have SP2, it should be exactly like if you had Acceleration, from a graphic engine point of view. Unless we discovered a bug that affects only SP2 but not Acceleration. Do you have any chance to try it on a different PC ?
-
I currently do not use SP2. Yes, i hope that this will get fixed in the future, but it is dissappointing that it cant be fixed, and also would be nice if Kappa would step n since it me it looks like he made the scenery, cause he was the one that posted all of the preview shots of it
-
I currently do not use SP2
Can't you simply trying it ? SP2 can be installed and uninstalled.
. Yes, i hope that this will get fixed in the future, but it is dissappointing that it cant be fixed
As I've said, many times already, the only way we can fix it, is that we can SEE it, first. And, of course, if it's driver related and only happens under certain circumstances, there's nothing we can fix.
also would be nice if Kappa would step n since it me it looks like he made the scenery, cause he was the one that posted all of the preview shots of it
Kappa did the textures for the scenery but as I've said already, it's not the texture *design* that can create this problem.
Also, don't you think that, after the FIRST message you posted about this problem, we ALL went to immediately check on our systems first, only to confirm the problem doesn't happen ? When I say there are only 2-3 people at most that are having it and we can't reproduce it, I mean it...
-
Why would i use SP2, just for your scenery, when all of my current aircraft would then be incompatable? Even if the DX10 preview is not enabled, my planes still have issues. I have tried sp2 before and did not like it, so i removed it.
From all of the things that we have been told to do, it is not a simulator error, it looks like its a scenery error. We both have done everthing u have asked, and nothing has changed, still have bleeding. I would start looking into possible scenery solutions instead of FSX solutions.
-
Why would i use SP2, just for your scenery, when all of my current aircraft would then be incompatable?
I said: can't you just TRY it ? However, It's just a try, but since axiom is saying he's using SP2, I don't think is related to the Service Pak version.
From all of the things that we have been told to do, it is not a simulator error, it looks like its a scenery error.
If it was a scenery problem, everybody else would have seen it, not just 2 users out of several thousands who downloaded it.
-
I purchased it. I got to enjoy the scenery for a bit, taxied around. The bleeding isn't that noticible on the apron, but it is on the runways. Hopefully you guys aren't going to forget about this problem, even though it might affect only a couple of people. :) (And at Terminal 5 there are two M1 markings which screws up the gate numbering, there is a seprate post regarding this)
Grazie per vostro lavoro (e non ho scritto quello solo perchè voi siete italiani, io studio italiano ;D)
axiom
-
Well I have FSX SP2/Acceleration running on my Vista Disk, and O'Hare runs fine there, so right now it looks like the problem is, it's not compatible with FSX RTM or SP1.
-
i guess. I also have the fly tampa sxm scenery that works great, no texture bleeding, and also the indianapolis X scenery with no bleeding either
-
i guess. I also have the fly tampa sxm scenery that works great, no texture bleeding, and also the indianapolis X scenery with no bleeding either
That's doesn't mean anything. Each scenery is done differently and you can't just compare like this. As I've said already, OHare is a little bit more FSX-native than Zurich. Probably Zurich will not exhibit this problem on your system as well. And no, we can't redo the whole ground like Zurich, because there are solid reasons why this scenery is done this way and the other not.
Perhaps it's something that manifests only with FSX SP1, but that's also not certain, because Axiom says he use SP2 and he's the only other one that see it. So, it might also be a system problem that only affects FSX sceneries, but only those made in a specific way. There aren't many around to compare.
But, as I've said, too many times already, it's not possible to even START working on a fix, if we can't reproduce it. At least, if we had more users that reported it instead of just two, we might even start seeing a pattern of system configs and trying a fix "in the blind". But this is not the case. We have 2 users, one with SP1 the other with SP2, for everybody else the scenery works, where's the pattern in this ?
There is a reason why we have a Trial, to let the user TRY the scenery on HIS system and let it test it against unforeseeable issue that might happen only on HIS system, like this one. If you can't stand this issue, you shouldn't buy it in the first place. I already offered you a refund, BTW.
-
My cousin recommended that I should switch back to Windows XP because the driver might not be fully compatible with Vista. Any thoughts?
axiom
-
Im not gonna do that!!! that is going a bit to far for me. but is there anything else that we can provide in order to maybe get on the right track to get this fixed?
I would rather not take a refund at the current moment. I belive that this can be fixed. I talked with another guy on the Flytampa forms and he too said he had the runway bleeding prob with fsx sp1.
-
No, I also don't think it's a XP vs Vista issue. We are all using Vista here, and we can't see any problem.
I think the most probable cause is FSX SP1, even if axiom said he's using SP2. Switching between SP1 and SP2 is FAR more easier than changing OS.
-
Just to add to that, I have FSX SP1 running on Windows XP and have the bleeding problem, while my FSX SP2/Acceleration installation is on my Vista Boot Disk, and there is no problem!!
-
i'll get acceleration then, didn't they make some terrain changes with acceleration?
axiom
-
Yes, there are. But the changes were from SP1 to SP2. Acceleration, in this regard, should be exactly like SP2
-
what else can we do in order for this to get fixed?
also just had a thought, is there a way to remove the default ord scenery files to see if that is the conflicting part?
-
As I've said, it might be worth trying with SP2.
-
Ill try sp2 when i get home, but axiom has a sp2 problem, so i dont think it will be any different with me.
but in the mean time how could i remove the default ORD?
-
Ill try sp2 when i get home, but axiom has a sp2 problem, so i dont think it will be any different with me.
I'd try it anyway. Perhaps there are two combined things at play here, one that is affecting axiom on sp2, and another one that is affecting you on SP1 that *might* go away with SP2. You never know.
but in the mean time how could i remove the default ORD?
It's not so easy. The right way to remove an airport, is with an exclude file. We provide an exclude in native FSX format (VTP exclude) at KORD. Default airports are inside the files named AP*.BGL (thousands of files) but it's not a simple as having just KORD with its own file. The AP*.BGL file that contains the default KORD, will also contains other airports in the area.
-
Strange, it seems to work with SP2, but not with SP1. SO that means that it isnt fully compatable with SP1 or something to that effect.
Quite honestly im baffled right now.
-
Strange, it seems to work with SP2, but not with SP1. SO that means that it isnt fully compatable with SP1 or something to that effect.
Quite honestly im baffled right now.
i made a mistake, turns out SP2 never installed. I remember running it though, but it never installed. As soon as i found out SP2 is the answer, I rushed to install it again but its not going. It starts caching, and when it reaches the end in starts to rollback and the installer closes, thats what must have happened when i originally tried installing it. HELP! This is the answer to the problem and its not working!
axiom
-
I cant help u there buddy, sorry. my install went very smooth.
-
It starts caching, and when it reaches the end in starts to rollback and the installer closes, thats what must have happened when i originally tried installing it. HELP! This is the answer to the problem and its not working!
I read in a previous message you were going to install Acceleration. SP2 it's not needed and will not install if you have Acceleration.
But, it happened to me once, that if you uninstall Acceleration, it's not possible to install SP2 anyway, and you have to uninstall FSX entirely and reinstall it from scratch.
-
IT'S FIXED!! NO MORE BLEEDING!! ALL THIS TIME AND IT WAS SP2!!
I reinstalled FSX and SP2 installed, I guess because I didn't modify any files in any ways until I installed both SP's. Im so happy right now its not even funny! ;D
Im gonna do my LOT 767-300 EPWA-KORD flight!! Thanks for an awesome KORD, never thought I'd see someone do it, and Im extremely grateful!
Thanks again,
axiom
(Since the solution to the problem has been found, I think this topic should be locked or something)
-
Im glad that u got ur problem fixed.
-
Well I guess it's clear now the problem is FSX SP1. Now the big question! Is there going to be a fix for this? If not and the requirement is to go to FSX SP2, then I think FSDT should put a warning that the scenery is not compatible with FSX RTM/SP1, either on the download page or the FAQ's. There are still many that are still not willing to go to SP2, because of it's other issues (I included), so they should be aware of this problem.
-
There are still many that are still not willing to go to SP2, because of it's other issues (I included), so they should be aware of this problem.
Before deciding the scenery is not compatible with SP1, I would like to hear from someone with SP1 that doesn't have this issue.
Since we only got 2-3 people reporting it so far, out of many thousands who downloaded the Trial, if the issue always appear in SP1 and never in SP2, then we must concede that the "many" not willing to go to SP2, are really not that "many".
-
i also am getting the bleeding textures, and just becaus "hundreds of people" have downloaded this, doesnt mean they are all going to report it once they see it. (unfortunately)
and i also only have SP1 installed. (have done a re-install, played with settings, have no scenery addons whatsoever, and no AFCADS.)
-
ok, i just installed service pack 2, and problem solved.
-
just becaus "hundreds of people" have downloaded this, doesnt mean they are all going to report it once they see it.
It's not "hundreds" that downloaded it, it's several *thousands*. If we have 3 reports in total, the only thing we have to assume is that:
- People don't see it as a big problem. Since the ARE several reports of other issues, clearly people DO report about problems, usually.
- If the problem it's just SP1, we must assume the percentage of users still with SP1 it's now too low to be taken into consideration.
That's the only assumptions we can do, with THIS report/download ratio. The fix it's quite simple: we'll update the web page with scenery requirements, putting SP2 or Acceleration as a prerequisite.
-
mmk.
-
How do I disable the FSX default gates from showing, Along with that the gates for the product don't show at all just part of the jetway tunnels.
(http://i276.photobucket.com/albums/kk24/dva085_tys/Boeing%20777/TYRONE-PC-2008-apr-24-033.jpg)
-
Your screenshot is not normal at all. Your problem doesn't have anything to do with this thread subject, that has been fixed for quite some time already, and that was only relevant to just the jetways.
What you are seeing, is entirely different: you are seeing the *whole* default O'Hare scenery.
A reason for this could be another AFCAD coming from another product that is interfering with its own exclude. These usually comes with AI traffic packages, like MyTraffic X or UTX.
Use the AFCAD utility to check how many AFCAD you have at KORD. There should be ONLY TWO: "Stock" (the default one) and ours.
If you see more, delete all the offending ones.
-
Thanks for the info I shall try as you suggested..