Thanks Momtchil... I was taking my daily 4 hour nap and missed the excitement here.

 

Best regards,

Jim

Thanks Momtchil... I was taking my daily 4 hour nap and missed the excitement here.

 

Best regards,

Jim

No problem Jim!

Hope you enjoyed that nap. I'm going to have one of these soon too :biggrin:, looking forward to it.

I would recommend taking the plunge Dr V, I did (despite a few reservations) and have no regrets.

 

Regardless of what others may say on other forums about DX10, the few simple steps and fixes posted here (and elsewhere) I think improve the visual and enjoyment factor many fold.

 

Asfor the lights issue, I still have the default scenery in my fsx installation and note (like others) that the approach lights, strobe effects and VASI lights at some airports do not work and yet at others work just fine. And it is not as if all the lights I mention do not work, seems some do some don't.

 

Does the AddonConverterX software fix this?

 

Or is it more of a design issue in the original scenery file for a particular airport?

 

I for one will not let it detract from my fun, after all that is the whole point is it not. To have fun and enjoy the experience.

 

Regards

 

Stuart

Edited October 8, 201213 yr by firehawk44
increased size of your font as lettering was too small

Does the AddonConverterX software fix this?

 

It does not. It only converts FS9 textures.

 

Best regards,

Jim

[/font][/color]I don't have any issues with you jumping any kind of gun, Brett!

I'm doing the same as you are, except it's with the smaller airfields of the Orbx PNW.. My exceptions are KSEA, KPDX (both modified) and FT's St. Maartens. I have to repeat a few, as I did change to Mike Swannick's halo, and it's too dim to be used for approach lighting systems. (I think)

I agree. Way to dim for approach. But look at FSDT runway lights. Nice and bright. Up close to them, kind of blocky but acceptable. So like I was saying. Maybe there is a way to see how FSDT lights are made. You can't even change them with the .cfg tweak. I'm going to be looking at LatinVFR and Tropical sim next. But still. DX10 has done wonders for me and since I'm a daytime flyer. Night textures are not a huge concern to me, but I know it's huge for others. That's why I'm doing what I'm doing.

And yeah, I wondered about the title to this thread myself. I believe it was titled DX10 night textures. And as if 2am last night. I saw no reason to change the title. Made no sence.

Thanks Momtchil. No drama as far as I'm concerned, just puzzlement and a faint amusement at the shouty ALL-CAPS.

 

The original title was something simple like "DX10 at night". Since the discussion has drifted onto a general discussion of lights in DX10, I've no problem with the current title if it helps interested parties find useful information, as long as it doesn't make the original poster (i.e. me) look like an over-excited thirteen-year-old. At least whoever changed it had the decency to use the apostrophe correctly. :lol:

 

So back to the important business of our pretend aeroplanes and their blinky-bits, or lack of in DX10. I fly a mix of all sorts - daylight GA hops, location barnstorming and commercial tubeliners, depending how the fancy takes me. When doing the latter I usually fly real-time, real weather and sometimes the arrival might be after dark. So lights are going to be an issue for me.

 

The problem isn't just with add-ons - I was flying the default C172 and that was missing the tail light.

 

Definitely not writing off DX10 just yet. Sounds like the gurus here are working their way through all the glitches and niggles one at a time.

 

Dr V

I am looking at DX10 mode simply because the performance of FSX in DX9 mode on my PC is so disappointing in very highly detailed areas. However, I am not referring to framerates here. It's the ridiculous number of OOM errors that is annoying me. Quite why I get this and others don't is a complete mystery. I do not get the same problem with DX10 mode, although I do notice that AA/AF isn't quite as good (some trees and other objects "shimmer" a bit more than I would like), and then there is the "lights" problem mentioned above.

 

As for Addon Converter X....it is very good, but again it is not perfect. Airport vehicle textures (in particular) do not display at dawn or dusk, and one of my existing BGL files caused FSX to crash when loading with Addon Converter X installed. Removal of this BGL file was necessary to solve the problem, but as it is a library file for one of my high detail scenery addons, I really can't do without it. Hopefully, a solution will be found by the developer of Addon Converter X, and then I can relax a bit! The strange part of this tale is that I know someone else who uses the same scenery package with Addon Converter X, and they can run FSX just fine..... :huh:

I have the same problem with AOCX and airport vehicles and have a suspicion it's to do with where those models are sat and that it's not actually attempting to convert them in the first instance rather than being unsuccessful when trying to convert. If you see what I mean.

However, I am not referring to framerates here. It's the ridiculous number of OOM errors that is annoying me. Quite why I get this and others don't is a complete mystery. I do not get the same problem with DX10 mode, although I do notice that AA/AF isn't quite as good (some trees and other objects "shimmer" a bit more than I would like),

As for Addon Converter X....it is very good, but again it is not perfect. Airport vehicle textures (in particular) do not display at dawn or dusk, and one of my existing BGL files caused FSX to crash when loading with Addon Converter X installed. Removal of this BGL file was necessary to solve the problem, but as it is a library file for one of my high detail scenery addons, I really can't do without it. Hopefully, a solution will be found by the developer of Addon Converter X, and then I can relax a bit! The strange part of this tale is that I know someone else who uses the same scenery package with Addon Converter X, and they can run FSX just fine..... :huh:

Hi Chris: glad you have jumped in! Going back to the OOM debacle - did you look at the recent post regarding the sizing of the Windows desktop heap? I put a copy of the fix here, as it is the most significant cause when the problem isn't related to VAS.

Yeah - AddonConverter is good, though not a "fix-all" - better with aircraft: I wish the devs would stick to the FSX SP2 SDK when they're producing and testing their respective product. Lighting is still an issue it seems, though the default airports and sceneries seem to be just fine.

Sooooo - after half an hour of flying up and down Bowerman's runways - I've found it is the tall grass that partially obscures the runway edge lights. Here are the shots... the first up/down pass is with Mike Swannick's Halo.bmp: the second is with another I happened to have from somewhere: the third pass is using the default halo and .fx effects. When closed in on the lamp - one can plainly see the grass. Remove the grass, and Voila`! No more blinking/dim runway lights.

 

pj

In regards to the poor runway lights, I saw some excellent lighting in the recent video put out by Les here in this forum. I heard that turning on Bloom (a framerate killer) will make the lighting much brighter. I haven't tried it myself as I mainly fly during the day or in massive rain and snow storms. Just read and saw the stuff. FSX lighting has always been a sore subject since FSX was released and I'm sure it would have been improved upon if the Microsoft Aces Team was still in operation and FSX was getting regular updates.

 

Best regards,

Jim

I have just bought Aerosoft Helsinki airport and there's no night runway lights in DX10 preview mode. All Mega Airports are the same? I really wish there could be some way to use these airports in DX10 mode.

 

These DX10 tips have really made my FSX a new thing. Thanks for the folks involved!

Paul. That is good news. But BP KSDF does not have the grass, at leart I don't think it doesn't.

This thread is growing. I enjoy working with you guys and enjoying digging into FSX to at least work on the runway lights. What our your thoughts on moving this to another forum or something so we can comunicate on what we have found instead of making this forum grow and grow. I have a private teamspeak channel we can use, email too. Then post our findings to the AVSIM community.

Thoughts on this. I'd like very much to be part of the team to help nail down this issue. You guys have helped me so much. I'd like to give back.

I work tomorrow, I'm a fireman so I work 24 hr shifts then Thursday morning I have a planned UPS flight from SDF to LAX to test the new US Cities X LAX , Megascenery x SoCal and FSDT KLAX and see how well they with together. Anyone is invited to join me. Then it is back to testing the night lighting issue. My goal like I said is to make a detailed list of what airport works good , dim and black.

 

Brett

From what I can remember (I haven't tested these thoroughly, so maybe I should), none of my Aerosoft airports work properly at night in DX10.

 

Maybe I should go through mine (CDG, Schipol, El Prat, Vienna, Munich, Madiera, Heraklion) and make a proper list of what works and doesn't at night?

Going back to the OOM debacle - did you look at the recent post regarding the sizing of the Windows desktop heap?

 

That "fix" did absolutely nothing to help me with my OOM problems, Paul.

 

As for airport lights, I do not seem to have a problem with these being displayed. However, I do have a problem with "doubled up runway lights and markings" at certain addon airports, and it has nothing whatsoever to do with "rogue AFD files", because the problem does not exist in DX9 mode.