DavidRN

All the problems start when you try to arrive there :P. I have been able to depart with no issues, the problem is landing. :mad: And, this is the only FSX KEWR that is available other than Ray Smith's AFCAD. Considering the overall quality, it should run much better than it does. It is not bad, but it should run better for what it is. Flighbeam, FSDT, Fly Tampa, etc. run on my machine all day long. I am still running DX9. Maybe there is some relief with DX10 as far as VAS goes. I have heard mixed things about the DX10 fixer and the results it yields regarding some land and water textures. I have a top of the line system, have not had an OOM or crash in months, and KEWR crashed the sim (OOM) 3 of 4 times. And, not long flights either. :wacko: I hope there is another fix coming.....soon. If there isn't; there should be.

Hi Skewr, Thank you very much for the reply. I had already changed the texture load back to 2048. That is where I run it usually. I also have all other non-used sceneries disabled. My water is set to 2X high though. I will try that and see if it helps any. I am still using DX9. I do have a person in my airline that went to DX10 with the fixer. I guess there are some texture issues with water? I am leery of changing all that stuff. Funny how you just get things stable and running right, and then comes along a new add-on that makes us go back to the drawing board. Thank you again for the reply.

Hello, I bought the latest version of the New York airports. I am only using KEWR and have the others disabled. Every time I fly into KEWR, I get an OOM error. Now, when I am flying out of KEWR, I am getting OOM's at my destination airports. I can honestly say it has been months since I have had an OOM and that was after a 10+ hour flight, PMDG 777 and Flight Beam KSFO. SO, I can expect that. :P Has anyone else had an issue with these airports after the re-release? I have looked around and have not found anything. My system handles the scenery just fine, no jitter, stutters, etc. Just up and OOM's on me. Open to thoughts on this. I would have posted in the Drzewiecki forums, but their site has been down for a few days now. Should have known better than to try this! Thanks

Thanks for the replies guys. Using TRackIR and zoomed all the way into the knobs themselves. I have had times where I was too far back and lost the click areas. Simple move in did the trick for those. Not this time. Not sure what the deal is. After I land I will have to reboot it and see if it clears up. I think it thinks it is on another screen rather than the VC. When I cycle through the screens I am getting some strange ordering of how they are coming up in the sequence. Maybe just a 777 brain fart.

Hello, today I found anothe rissue with the 777. Flying form ZBAA to YSSY all of the sudden the capt seat VC went unclickable. No pointers, no hands. Everything works as it should from other views like to FO and all panels. All pop-up panel work just fine as they should. Just the capt side is inop. Thought it may be a screen issue. nope. Also tried the f9 button as sometimes the vc is inop after changing screens. nope. I am at a loss on this one. anyone else have this issue? I have quite a few flights in this bird and this is the first time I have seen this one. Google and other forums offered no help. Am I the first ?? Thanks.

1) Loses its track on True heading mode when going over the pole. Side to side action of about 3 miles. Magenta line turns but no fix, wpt or coords associated with it in FMC. 2) Back lights and panel lights on over head do not function. Knob works just fine. 3) During manual landing, trim is INOP; no green bars. Programmed button on yoke does not work. Works with all other planes I have including the MD-11 and NGX. Comes back as soon as you land. Works fine after takeoff with no issues. 4) GPWS does not call correctly. Misses alt call outs. Last night went 40, 20 and then touchdown. Also missed some other ones too. Other than that it flies like a dream with no issues.

Thanks for the response and explainations Damian. I look forward to working with you to find resolve to this SimConnect issue. If possible.

I have searched and read the forums regarding this topic. I am not sure where the actual problem lies. So far I have installed the SDK on the Sever (FSX machine) and Client. I have updated all the way to SP2 as this is what SP I have in FSX.I am sharing these files.Users/xxx/AppData/roaming/microsoft/fsxUsers/xxx/Documents/Microsoft Flight Simulator X Files andThe main FSX folder from the default install location.The files can be viewed, written to and saved from the client. However, ASE gives me a database update error and states that the sharing component is not setup properly. Not sure how that is. Been running ASE with FS9 for 2 years! Because of this error, I cannot use ASE now as it looks for the files and continues to error despite that fact that these files show under the server computer on the client network tab. I figured this issue out on my own. It seems that ASE will only recognize folders in the Users\Public folder for sharing. Just plain sharing and seting the path is what caused ASE to not work. I moved the files and edited the registry to the new path and it fires up. Sim Connect still will not work. I tried both sharing options, from the Users..... and the direct path that is created when you share a folder using the properties functions. NO diceI have read and gone through the ASE manual many times.Here are my filesSimConnect ini out of the Microsoft flight Simulator X file folder[simConnect]level=verboseconsole=0;RedirectStdOutToConsole=1;OutputDebugString=1;file=c:\simconnect%03u.log;file_next_index=0;file_max_index=9HelloHere is the xml file from the App Data/roaming/Microsoft/fsx folder<?xml version="1.0" encoding="Windows-1252" ?>- <SimBase.Document Type="SimConnect" version="1,0"><Descr>SimConnect</Descr><Filename>SimConnect.xml</Filename><Disabled>False</Disabled>- <SimConnect.Comm><Disabled>False</Disabled><Protocol>Auto</Protocol><Scope>global</Scope><Address>DAVIDZYCHOWSKI</Address><MaxClients>64</MaxClients><Port>500</Port><MaxRecvSize>4096</MaxRecvSize><DisableNagle>False</DisableNagle></SimConnect.Comm></SimBase.Document>Here is the config from the client users/xxx/documents folder[simConnect]Protocol=AutoAddress=DAVIDZYCHOWSKIPort=500MaxReceiveSize=4096DisableNagle=0I have tried IPv4 and auto modes. I have tried IP (192.168.1.9) and computer name. Yet, I still cannot get it to connect when I use the AI Package exe from the Client.Yes, the msi was configured on the client as wellI created rules and opened port 500 on both machines. I even dumped AVG on the server and went back to Windows firewall. I also disabled both of them. Still will not connect.HiFi, why did you not just use WideFS for FSX like you did for FS9? That config takes the whole of 2 minutes!If anyone can shed some guideance it will be greatly appreciated and valued. If I had to guess, it seems as if the error is in the sharing aspect of things. However, I am not sure why they can be seen, opened, written to and saved then.This makes no sense.And, I am still waiting for HiFi support. I filled out a ticket days ago. They sent me survey forms for supoprt I did not receive.

No one has any input to help with this?I did figure out the ASE issue. It seems that the shared files need to be in the UsersPublic folder in order for ASE to work. After I placed the folders here, I edited the registry paths and ASE now fires up.SimConnect is still not working. And, no supprt from ASE either. But, they did send survery forms about the support they never gave. What a joke! No way I will ever buy 2012 from them now.

I think that is your porblem. You need to change the ip address in the Simconnect xml on the server machine and the simconnect config on the client. That should get you up and running again. WOW, I never thought I would be able to offer support on SimConnect. Now if I can only get my Charlie Foxtrot bag of simconnect issues straight.You can go here for more informationhttp://msdn.microsoft.com/en-us/library/cc526983.aspx

Ken, you can run AS2012 using Wide FS? REALLY? Are there directions for this anywhere? I have been trying to use Simconnect and ASE for days. If AS2012 works with WideFS, I'll just buy it!Thanks

I have searched and read the forums regarding this topic. I am not sure where the actual problem lies. So far I have installed the SDK on the Sever (FSX machine) and Client. I have updated all the way to SP2 as this is what SP I have in FSX.I am sharing these files.Users/xxx/AppData/roaming/microsoft/fsxUsers/xxx/Documents/Microsoft Flight Simulator X Files andThe main FSX folder from the default install location.The files can be viewed, written to and saved from the client. However, ASE gives me a database update error and states that the sharing component is not setup properly. Not sure how that is. Been running ASE with FS9 for 2 years! Because of this error, I cannot use ASE now as it looks for the files and continues to error despite that fact that these files show under the server computer on the client network tab.I have read and gone through the ASE manual many times.Here are my filesSimConnect ini out of the Microsoft flight Simulator X file folder[simConnect]level=verboseconsole=0;RedirectStdOutToConsole=1;OutputDebugString=1;file=c:\simconnect%03u.log;file_next_index=0;file_max_index=9HelloHere is the xml file from the App Data/roaming/Microsoft/fsx folder<?xml version="1.0" encoding="Windows-1252" ?>- <SimBase.Document Type="SimConnect" version="1,0"><Descr>SimConnect</Descr><Filename>SimConnect.xml</Filename><Disabled>False</Disabled>- <SimConnect.Comm><Disabled>False</Disabled><Protocol>Auto</Protocol><Scope>global</Scope><Address>DAVIDZYCHOWSKI</Address><MaxClients>64</MaxClients><Port>500</Port><MaxRecvSize>4096</MaxRecvSize><DisableNagle>False</DisableNagle></SimConnect.Comm></SimBase.Document> Here is the config from the client users/xxx/documents folder[simConnect]Protocol=AutoAddress=DAVIDZYCHOWSKIPort=500MaxReceiveSize=4096DisableNagle=0 I have tried IPv4 and auto modes. I have tried IP (192.168.1.9) and computer name. Yet, I still cannot get it to connect when I use the AI Package exe from the Client.Yes, the msi was configured on the client as wellI created rules and opened port 500 on both machines. I even dumped AVG on the server and went back to Windows firewall. I also disabled both of them. Still will not connect.HiFi, why did you not just use WideFS for FSX like you did for FS9? That config takes the whole of 2 minutes!If anyone can shed some guideance it will be greatly appreciated and valued. If I had to guess, it seems as if the error is in the sharing aspect of things. However, I am not sure why they can be seen, opened, written to and saved then.This makes no sense.

Maybe you are using a different IP address now?