Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

1 Neutral

About tripecac

  • Birthday 01/01/1973

Flight Sim Profile

  • Commercial Member
  • Virtual Airlines
  1. I just noticed a big 38% off banner on the ORBX forums. This reminded me of a topic where John Venema (the ORBX CEO) promised “no more sales, ever”: I questioned the validity and wisdom of that promise, and the topic ended up getting locked, and I received a "warning" and an accusation from Ian Routely that my line of questioning was "borderline" and displayed "no understanding of how these things work." In retrospect, was my line of questioning completely out of line? Were my questions about development costs, software depreciation, and ORBX's update plans for PNW really so threatening that their censorship, warning, and condescension were justified? The way John and Ian handled their side of the discussion left me feeling deeply shocked and insulted, to the point where my enthusiasm for ORBX was (and remains) greatly diminished. Their harsh (and very public) reaction to my line of questioning ended up costing them hundreds of dollars from me, and possibly many more from other people who read their reactions to that topic. Coincidentally, I just watched Straight Outta Compton last night. Perhaps that stirred those old memories, of John and Ian shoving me to the [virtual] curb.
  2. Okay, I downloaded and installed FSX SceneryConfigEditor, and used it to disable these: 3) FS Genesis - World Mesh, North America 4) UTX USA 5) GEX North America I also disabled ORBX's Olympic Peninsula freebie; I had forgotten about that. The game loads, NZ scenery looks fine. I can't tell for sure if it loads faster or not; my impression was yes, but that could just be wishful thinking. I suppose if I want to be scientific about it I should time it before and after making those changes, but oh well... So far it hasn't seemed to break anything, and might be a tad faster (certainly not slower), so that's good enough for me. Is there any advantage in disabling the base FSX scenery as well? For example: - Las Vegas - Rio de Janeiro - St. Maarten ... - Australia - Asia - Africa etc? Or are none of those likely to bog down the load time (significantly)?
  3. Okay, so it's not hurting anything (in terms of performance) to leave the North American scenery enabled when I fly in NZ, right? How about that FS Genesis world mesh? Any idea if it is being used in an ORBX-covered area?
  4. I fly primarily in New Zealand. I would like to reduce load times. I've got the following add-on scenery installed: 1) GodZone RealNZ Southern Lakes Adventure (Wanaka, Tekapo) 2) ORBX New Zealand South Island 3) FS Genesis - World Mesh, North America 4) UTX USA 5) GEX North America Clearly, the USA scenery isn't being used when I am flying in NZ. I'm not sure about the FS Genesis World Mesh; it might be getting overriden by ORBX's NZSI or Godzone RealNZ. My questions are these: 1) Is FS Genesis World Mesh even being used? If not, is it slowing down the game or increasing load time? 2) Will disabling FS Genesis, UTX, and GEX increase the speeding of loading (or perhaps even frame rates)? 3) Is disabling scenery just as effective as uninstalling scenery completely (in terms of loading), or should we uninstall scenery if we want to minimize load time? Thanks!
  5. Problem fixed (I think), at least for DX10; it appears to have been a cpnflict between 2 add-on scenery packages. Fixed by renaming a particular scenery file. DX9 still does not work. No big loss, though, as DX10 seems fine so far (in my limited testing).
  6. Today I started up FSX for the first time in months. I flew the standard route that I always do when getting back into FSX, which is around Wanaka Airport in New Zealand. I am using 2 sets of add-on scenery in that area: ORBX's New Zealand South Island, and GodZone's RealNZ Wanaka. After flying for about 3 minutes I noticed some black textures on nearby mountains. And then I noticed water textures in the middle of the town. As I flew closer, the water textures changed to other textures quickly, as if it were cycling through different textures looking for the correct one. Weird. Clearly a glitch. I checked my settings and noticed that FSX was using the DirectX 10 preview, so I switched to DX9 and restarted FSX. This time, no textures loaded at all: the image of the plane on the Free Flight page was completely black, and when the actual game started, it just flashed "Loading 100%" over and over, with black in the background. I switched back to DX10. The Free Flight image was there, and I could start flying. But again, some of the nearby ground textures were corrupt. So, DX10 has corrupt ground textures, and DX9 has no textures. My video card is an ATI Radeon HD 5850. I'm running the latest driver (13.12). I usually use DX9 but a few months ago, a driver update (13.9) "broke" FSX for me; it would not run at all in DX9. The standard advice was to roll back to a previous driver (13.4), but since I play other games I did not want to do that. I found that switching to DX10 enabled FSX to run, but I didn't have time to do much testing of DX10 at the time. I don't know if today's texture glitches were also present back on 13.9; I didn't fly around enough back then to notice them. I also don't know if the texture glitches have always been present in DX10, since I have mostly flown with DX9. So I don't know for sure whether they are DX10-specific. I am, however, 100% sure that these texture glitches did not exist back when I was running FSX in DX9 before the 13.9 update. My scenery add-ons have not changed since then, so I suspect the problem is driver related. NOTE: If I disable RealNZ Wanaka, the glitches go away (but I lose the detail that RealNZ Wanaka provides). So there appears to be a conflict between the video card and the add-on scenery. Here are my questions: 1) Are the ground texture glitches a known problem for DirectX 10? If so, is there a fix? 2) Is there a way to get DirectX 9 working on current Radeon drivers? Or is rolling back to 13.4 the only known fix? Thanks!
  7. Ah, ok, thanks. I guess I either didn't test long enough, or didn't set the sliders high enough to encounter the problems other people are having with 13.9 and DirectX 10. Have people confirmed that the betas for 13.10 and 13.11 also have the same problems as 13.9? Also, would copying the 13.4 atiumdag.dll to the FSX directory fix the problem, even if 13.9 or later is still installed? (In other words, are there any solutions less drastic than rolling back to 13.4?)
  8. I recently installed the Catalyst 13.9 drivers. As with everyone else, I get a crash to desktop when trying to start Free Flight mode using DirectX 9. Instead of rolling back to 13.4, I simply enabled DirectX 10 Preview. Now, FSX loads, and I can fly around as before. Using menus doesn't break it, at least so far. DirectX 10 might not be as efficient as DirectX 9, but it's a lot easier than rolling back to 13.4, and doesn't put other games (or the computer in general) at risk. So I am curious: why are people recommending a rollback to 13.4? Why not simply switch to DirectX 10, at least until we get a Catalyst version that works? Are some people having problems with 13.9's DirectX 10 as well? Or is DirectX 10 *dramatically* slower than DirectX 9 on some machines?
  9. It's hard to click on the little "-" and "+" controls on the GPS. Is there a way to get the GPS to zoom in and out using keyboard shortcuts?
  10. Does anyone know how to get Spot View to rotate in the correct direction?
  11. I downloaded FSUIPC but after reading the docs suspect that time sync feature is for the registered version only; is that the case?
  12. I'm in New Zealand, and often fly FSX here too. However, i have my default flight saved as an aiport near Seattle. For some reason, the fact that the default flight and my physical location are in different time zones confuses FSX. For example, I start FSX at 9:19am, and go to Free Flight. The default flight is near Seattle, and the Current Time and Season says 8/12/2012 9:19am, which is the current time in NZ, not the current time in Seattle. When I load the flight and then go to World / Time and Season..., I see that the local time is 9:19am, which is wrong; the actual local time in Seattle right now is 2:19pm. If end the flight and then select Auckland Intl as my current location, I see that it is dark, and FSX says that local time is 03:19:32, GMT is 16:19:32, and the date is 8/13/2012. In other words, FSX thinks the current time in New Zealand is actually 18 hours in the future. So, it's as if FSX assumes that your computer's time is the current time at the default flight's location, not your actual location. It doesn't seem to be "aware" of your computer's actual time zone. The workaround is to change the default flight to an airport in your own time zone. So, if I start at Auckland Intl, and then save that as the default flight, the next time I open FSX, the time of day issues are gone; all time of day calcuations seem correct at that point. This is a relatively painless workaround, but what would be ideal is to get FSX to become aware of our computer's actual time zone, so that it can base time of day calculations off of that instead of off of the default flight. Of course, maybe these "errors" are intentional. Let's say you live in Seattle, but want to fliy a "grand tour" around Africa, where each day you fly to a new airport, and save your current position as the default flight, so that tomorrow you can continue where you left off. If you fly at a time when it's actually dark in Africa, it will be a real pain to have to keep changing the Time of Day each time you load FSX (in order to get daytime scenery). So maybe FSX is trying to be "helpful" by assuming you always want to fly your default flight at the time of day where you are now, not at the actual time of day at the default flight's location. (Of course, if you happen to fly at night, the "helpful" feature will be annoying). Anyway, has anyone else investigated this issue? Is there a cleaner workaround than setting the default flight to the same time zone as your computer? Thanks!
  13. This morning I started Flight (in Alaska), jumped to the airport in Kodiak, and then started GMap. It loaded fine, except when GMap was loading, Flight also seemed to re-load the scenery. Strange! Does this happen to you too?
  14. I started Flight, switched to an airport in Hawaii, took off, started Gmap, and it still says it cannot connect to MS Flight. I then switched to an airport in Alaska, and still no go. But then I tried running it as Administrator, and it worked. Looks great once it's running! I just hope I can get it to run consistently... Do we have to jump to/from Hawaii each time we started Flight in order for GMap to work?
  15. I start MS Flight, and then start GMap, and when I click the GMap button it says "Cannot connect to MS Flight". I've tried GMap versions 2.0 and 2.1 (the most recent version - July 4 I think). Neither work. I've also tried starting GMap before and after Flight starts. I'm using the Steam verison of Flight, install on my D drive. Any ideas on how I can get GMap working?
  • Create New...