hadoken

The rolling fog issue does disappear for me after a few minutes, but I think this is a bug. This issue was not present in the previous version.

I just installed "Beta2", however I'm getting this weird rolling fog in effect when the sim loads. After a few minutes the entire area is covered in fog. I can't take a screenshot because all you will be able to see is gray.

I'm asking if DTG view P3D as competition, specifically the Academic license since that's the one most people are buying. If LM is allowing people to abuse this license unchecked, that could pose a real problem for the actual entertainment license which is what DTG have. I asked that question because I want to know if DTG has any plans at all to stay competitive with the Academic license of P3D. For example if P3D decided to go 64Bit also.

Hello Martin. Who is your competition? Is DTG trying to stay competitive with Lockheed Martin's P3D v3.1 and their pricing strategy (specifically the Academic license that's widely used due to the price point)? Or do you view P3D as a non entertainment license version of FSX-SE with no direct competition to what DTG is doing? Thanks

I disagree with some of the post in regards to the style of training. I personally enjoyed the way the training was done in the Q400, because it was not boring to watch. Please don't change the banter between you and the trainer to much. Your Q400 training video was just like a conversation between student and teacher, which not only made it educational, but also entertaining. Even to this day I fire up the video, not so much to learn anything new, but because I love the converstion between the actors. I hope in the newer videos that you keep that same style of training, and not make a video with two people talking plain, dry and boring. In my opinion that does not make for such a good training video.

I didn't think the Zinertek HD textures worked in FSX LVLD 767. Do you have any other screenshots confirming this? As for the issue, make a backup of the folder that contains the TUifly livery, then try copying the Zinertek VC textures into that folder's texture folder. I have a collection of the McPhat studio liveries and I remember I needed to do that for specifically for one of the liveries in order for it work.

HIGHMEMFIX is no longer needed. This is defaulted internally by FSX-SE. This change was made in the previous release build.

This is just my recommendation. I think you should try deleting your fsx.cfg file, so that FSX SE generates a new one. Try without adding any tweaks. FSX-SE and FSX are not the same products. A lot of the old tweaks used in classic FSX can actually override some of the new changes that DTG has added to FSX-SE. For example, AFFINITY MASK. While you can set this in your config file in FSX-SE, it's no longer needed with the latest build because FSX-SE sets this internally now based on the type of CPU you have. Setting it in the config will override the defaulted setting. That's just one example of reasons why you do not need to tweak your config file in FSX-SE.

This is just my guess, but I don't think that 777 is complied for simconnect 62610. The 737 probably was and therefore doesn't have any issues with FSX-SE build 62610. I think the 777 is probably complied for simconnect 62608. PMDG will probably have to release an updated installer to fix the 777. If you have Active Sky Next, you should see the same incompatiablity. The current build of ASN isn't compiled for simconnect 62610 either. These simconnect issue should be sorted out soon.

Okay thanks, I have the same thing in my 777 also after updating to 62610. I just wanted to confirm if it was a compatiablity issue with the 777 and the latest Steam Build. Hopefully a fix will be coming soon. SP1D is for the 737 if I'm not mistaken. My question is in regards to compatiablity between the latest FSX-SE 62610 build and the PMDG 777. The 737 SP1D works fine with FSX-SE build 62610.

Sorry if this has been posted already, but has anyone ran into any compatibility issue with the PMDG 777 and FSX-SE 62610?

I emailed Dovetail's support about this issue, after reading several "fixes" and suggested work arounds; which never worked I must mention, to get to the bottom of this issue, and they did reply. They said, "We are currently aware of this issue and we are working on a fix. When finished this fix will be downloaded automatically via Steam." -Dovetails Game Flight Simulator X Support I found another post on the Steam forums from someone else with a similar response from Dovetails. I don't think any of the fixes in this thread actually fixes the issue. The best we can do at this point is wait for them to release the next update. Anyone that suggest that this issue is just part of the way the simulator works, or you have your settings to high, or that Dovetails cannot fix the issue because legally they cannot release updates which they have already done, is probably being disingenuous.

[uPDATE] Tried another long flight and I got another terrain.dll error. Affinity mask is not the solution to fixing this issue. Back to waiting in hopes that Dovetail will release an update for the issue.

I was able to complete a long flight today, no d3d11.dll, terrain.dll or g3d.dll errors after adding affinity mask to my config file. A thread in the steam forums suggested that adding the mask would leave the first core open for the system, and put FSX-SE on subsequent cores (based on your cpu and selected affinity mask). I used a FSX affinity mask calculator to get the proper setting for my system configuration. I don't recall the link, but you should be able to find it by searching Google. So far after adding the affinity mask to my config, I have not seen any of the above issues. I'm going to try a few more long flights before I say this is a definite fix for the issue, but so far it has worked. Full disclosure, before adding this to my config file I did run a repair installation on FSX-SE, and reinstalled Global, Vector and FSGlobal 2010. I would be interested in hearing if adding the affinity mask to your config worked for anyone else as well that is using FSX-SE and have these issue while doing long flights.

I'm starting to see a lot of d3d11.dll errors, in addition to terrain.dll and g3d.dll. Has anyone else using DX10 and FSX-SE seen the same? I'm aware of removing KB2670838 as a possible fix, but I've had DX10 and this windows update for years installed and only recently starting seeing this issue in FSX-SE. At this point it's impossible to even complete a short range flight.

I would assume that DTG is aware of these bugs. If you read the latest news on the Active Sky Next page, you will be able to confirm that the developers of ASN has had some stability issues with FSX-SE also. I don't think there's much we can really do about the .dll errors until DTG uploads a fix for the issue, which I'm sure that they will do. For now long haul flights on the new simulator are all but impossible for most people, but after these issues are sorted out this will be a very solid simulation.

Looks like Aerosoft will be on Steam.... Source: https://fsxinsider.com/aerosoft-makes-the-leap-to-fsx-steam-edition/

I have concluded that there's an issue with stablity in FSX-SE whenever you fly for long durations. Based on Dovetail's Steam Support forum, they are aware of the issue and is working on a fix. Please see source comment.... [uPDATE] This information is based on a response from a user that received a response on the issue from Dovetail's support. I have not yet found a direct response from Dovetail that they're working on the issue. If anyone else has received a similar response, let us know for confirmation. SOURCE: http://steamcommunity.com/app/314160/discussions/1/612823460253102801/

I think Dovetail is aware of the issue. Please see my post here... http://forum.avsim.net/topic/460411-an-impressive-fsx-se-report/?p=3168900

We should conclude that Dovetail games is aware of this issue, and is working on a fix. Apparently the developers of ASN have been dealing with some stability issues in FSX-SE during there testing, and I quote "We have completed the ASConnect re-design, and we are currently ironing out the last remaining issues. This has been a difficult update, as we've been up against stability and freeze problems in FSX:SE even plain/default without any add-on including ASN. Fortunately we have been improving stability more each day, Dovetail has been active with updates, and we should be ready to begin official internal beta in the next few days." - Active Sky Next As it stands now, most cannot complete long haul flights in FSX-SE. For now it's probably best just to wait and see what's included in there next update. Maybe they will release one this month whenever ASN SP2 is released. Source : http://hifitechinc.com/ Active Sky Next SP2 News. Published February 1, 2015

You want to see something cool? Install Drezweicki Design Miami City. Crank up your autogen setting to Very Dense, and scenery to Extremely Dense. Depart KMIA RWY 30 and ride the wing on the DEEEP1 departure, PMDG 777 with Immersion if you have it, using DX10 and FSX-SE. All I can say is WOW! This is something that I could never do in the classic version without OOMs, or very poor performance. My FPS never dropped below 20fps, even with these settings. I'm now curious to see how Drezweicki Design's New York City handles under FSX-SE on an arrival into KJFK.

Unfortunately even after my recommendations that I posted, I started getting g3d.dll errors again. So to I investigated the issue a little more. I read somewhere that these errors can also occur if your scenery files did not install correctly, or are missing. I'm sorry I can't remember the source, but if you search Google something to this effect should turn up. To eliminate all possible variables, I completely uninstalled FSX-SE and all add-ons. I re-downloaded FSX-SE from the Steam servers and installed Global, Vector, OpenLC and then FS Global 2010 as indicated in the guide that I referenced in my recommendations post. This time I decided not to reinstall any of the Orbx free or payware scenery, or Orbx Libraries. Just to rule out the chance of any non FSX-SE compatible installer corrupting the fresh installation. I only installed the Orbx products that I referenced in the previous paragraph. I then installed all my payware scenery. Next I installed all payware aircraft. I decided not to re-install the Level D 767 since it has not been confirmed to have a installer specifically compatiable for FSX-SE. I did install other payware aircraft that is confirmed FSX-SE compatible such as, PMDG 777, Aerosoft Airbus etc. After reinstallation of FSX-SE, I have not seen any g3d.dll or terrain.dll errors. I have completed several hours of flight time, short and long range and still no issues. Something that was not possible in my first installation. So I can only conclude, at least in my case that something in my first installation had corrupted some of the scenery files. I have downloaded many games from the Steam servers in the past with no issues. Maybe one of the non confirmed compatible products I listed above overwrote critical files. I can't say for sure. However reinstalling, and eliminating the above factors have fixed this issue for me. It's a lot of work to reinstall everything, but if you have tried everything else, and nothing has worked then you can give this option a try.

This guys video's are awesome. Keep them coming! I switched over to FSX-SE after many years on the boxed version, and it does indeed run a lot smoother. Even with the 777 and all my setting near maxed out, I have no OOMs and the performance is much better. Liquid smooth frame rates even at some of the most complex pay ware scenery. I have a single installation, and no tweaks were used. The only config change I used after installation was setting Widescreen=True. Also FSX-SE with the DX10 fixer is even better. I have not seen a single blurry ground texture, and no ground texture popping at all in FSX-SE. Easily the best $5 I have every spent! Again great job on the videos!

I got it sorted yesterday. As it turns out at least for me. The g3d.dll error was indeed happening because of FTX Vector. I found a guide called "ORBX FTX The Definitive Guide", doing a google search. I think this guide is published by ORBX. The guide has a suggested installation sequence for ORBX products. The guide suggested that the installer will place ORBX products in the correct location automatically, which for me it always has. However I reinstalled my OS when I switched to a single install of FSX-SE, and installed ORBX products like I always have done. Typically I would install FS Global 2010, FTX Global, FTX Vector and the Open LC, in that order. In the past this never was an issue using classic FSX, but upon investigating my scenery config order I noticed that the installers put all of the FS Global 2010 files above all the FTX Vector files. This seemed a bit odd to me so I removed all of the ORBX files from my scenery config and reinstalled all ORBX products using the sequence suggested in the guide, which recommend that you install "FTX Global, FTX Vector, OpenLC, Terrain Mesh, FTX Regions and FTX Airports" all in this order. -ORBX FTX The Definitive Guide After using the guides recommendation, I noticed that all the FS Global 2010 files where listed below FTX Vector, which seemed more accurate. I was finally able to complete a 5+ hour flight without any kind of dll errors in FSX-SE, and the performance was 10 times better. Before reinstallation using the recommended sequence, I would typically get g3d.dll crashes at random points during the flight. I'm not sure if there's something diffrent between the way ORBX installers order the sequence in FSX versus the way it does in FSX-SE, but in my case installing FS Global 2010 before Vector created issues with Vector not being placed correctly in the scenery config list in FSX-SE. If you're using ORBX products, and you're having g3d.dll issues, I recommend that you confirm that all of your ORBX products are listed in the correct order in your scenery config. If it's not try reinstalling your ORBX products using the recommend method in the guide. I do aplogize for not providing a link, but I can't remember which thread I found it in, but if you do a google search for the "ORBX FTX The Definitive Guide" im sure you will find it. Source: ORBX FTX The Definitive Guide (pg.14)

A lot of people have reported issues of terrain.dll and g3d.dll issues. I have FSX-SE installed as a single installation with FS Global 2010, FTX Global, FTX Vector and FTX OpenLC. I often get g3d.dll errors if I have FTX Vector enabled. If I disable FTX Vector files in the scenery.cfg (only leaving AEC enabled) I no longer get the error. I'm not saying that there's some compatiablity issues between FSX-SE and FTX Vector, but on my system disabling Vector seems to fix the issue. Maybe some other users of FSX-SE and the listed ORBX products can confirm the same.