MyTrafficX 5.4C - ATI - traffic levels

[KingGhidorah 209]

No, no, the SDK won't mess your system up!  Just follow the instructions at http://fsdeveloper.com/wiki/index.php?title=SDK_Installation_%28FSX%29

 

There are some little quirks to it, like editing your .dll, but that's just the nature of the hobby.  Besides, if you run into trouble, you can always ask questions on Avsim, right?

[Driver170 42]

installed SDK but i still cant change the schedules?

[KingGhidorah 209]

When you bring up the Traffic configurator, isn't there a warning in a red box telling you that it needs the TrafficDataBasebuilder executable from the SDK, with a notation "<--what does this mean"?

 

If you can't bring up the GUI at all, then I'll bet you need Java too.  That would be at Java.com/getjava.  Sorry.  I just went through all these steps myself recently, so I know it's frustrating, but when has setting up FSX and it's addons not been frustrating?

[Driver170 42]

do i have to do this...

 

 

http://www.flightsim.com/vbfs/showthread.php?200041-How-to-Install-SDK-for-FSX-Gold

yeh thats right keep getting that error message

i cant get tools to show up in fsx menu bar during free flight...

already got java still not working :(

sorry but i have a different error message aaaaahhhhhhhhhhhhhhh

my traffic x windows cannot access the specified device path or file. you may not have the appropriatepermissions to access the item

[KingGhidorah 209]

ok, if you've installed the SDK in the correct order: 1) make sure you run the ConfigSDK.exe in the root directory of your SDK installation.  This will set up the registry paths for the SDK.  Next, you'll have to go into your dll.xml file, which is in the same directory as your FSX config file (appdata/roaming/Microsoft/fsx).  There will be an entry in the dll.xml file for the 3 toolbar items that are supposed to show up( Object placement, traffic toolbox, visual effects tool).  In each of these, you will find that there is a line that says <Disabled>True<Disabled>.  Change the True to False, and if you've done everything else correctly, you should get the Toolbar next time you load up FSX.  This appears to be a bug in the SDK setup, that I feel isn't properly emphasized in the relevant installation guides, that you just have to fix manually, unfortunately.  The first time I installed the SDK, it took me at least half a day to figure out why my Toolbar wasn't showing!

 

Oh, one more thing:  If you installed FSX in a directory different than default directory of C:/Program Files, you will have to modify the path to those tools to show the full path name (for example,  D:\My Games\Microsoft Flight Simulator X SDK\Mission Creation Kit\object_placement.dll)

 

That will get you your FSX toolbar, but I don't think it is what is keeping the MyTraffic Communicator from running.  Without knowing more, I might suggest you run the F1 Registry Fix Tool, to make sure your Windows Registry is correctly pointed to FSX.

 

Meanwhile, while you're at it, stick that TrafficDatabaseBuilder.exe from the SDK ( path is ...Microsoft Flight Simulator X SDK/SDK/Environment Kit/Traffic Toolbox SDK/) in the root folder of MyTraffic X.  Remember, getting access to that file is the only reason why you installed the SDK in the first place, regardless of whether you ever get the FSX Tools menu to ever show!

 

I know this is frustrating as hell, and I very much sympathize!  They didn't tell you that you would have to do all this when you purchased MyTraffic X did they!!!!

[Driver170 42]

Hi i installed SDK from my gold edition then downloaded a further 2 files    fsx_sdk_sp1a   and also   sdk   ?

 

changed entrys to false.

 

i will run F1 registry. thanks for your help

TrafficDataBasebuilder found

 

i have this message in green in my trafficomm

[Driver170 42]

something weird is happening i uninstalled MTX but when i got into scenery library nothing comes up in the directory its blank i can see all the folders in the list but the directory remains empty even after selecting it

[KingGhidorah 209]

When you navigate to the scenery folder under FSX/MyTraffic, it has all it's folders, but there are no files in them?

 

What I think you are saying is that you are having trouble adding the MyTraffic scenery directory to the Scenery Library.  Again, this might be another quirk.  The manual says that in Windows 7, you add the Mytraffic X directory, but then you will have to additionally right click in the window for it actually be added.  This little step threw me for a curve, and I had to read the manual to know to take that extra step. Then the scenery library should be added in at the top, and you then move it down to between the Propeller objects and the Addon Scenery.  Sounds like you're getting the Traffic Communicator window just fine now, your TrafficDataBaseBuilder is correctly in place, so you're almost there.  Make sure there is the SimObjectPaths.6=MyTraffic\aircraft entry under [Main] in your fsx.cfg, and if not either add it manually, or use the Traffic Communicator "Manage fsx.cfg" button to add it.

[Driver170 42]

Hi i have spent an hour left and right clicking the mouse to no avail it doesn't get added :(

 

But i still get that denied access i have always disabled UAC and DEP run as admin share folders etc tried everything thats the only thing thats keeping me back.

 

I haven't checked my FSX.CFG for that entry i'll have a look tonight

[KingGhidorah 209]

Gosh, I'm sorry to hear that!  To get it added, I had to move the mouse specifically over the Scenery List before right clicking.

 

They really ought to make this process more automated for people.

[Driver170 42]

day 2 of clicking this stupid box LEFT click RIGHT click how many more? i give up now whats UT2 do you know?

[KingGhidorah 209]

I don't know too much about UT2.  I strongly considered getting it, but since I had MyTraffic 2010 before, I decided to stick with the devil I knew, hoping there would be some improvements.  In retrospect, the amount of difference between what I already had in Mytraffic 2010 did not justify the price to get MyTraffic 5.4c.  I went with it because I thought it would have corrected some of the flaws it's predescessors caused in scenery areas, such as Trees growing out of the taxiways at Dulles.  Nope.  I also thought maybe it would be cool to run retro-traffic.  A few Pan Am 747's and Eastern 727's was kind of neat, but it certainly wasn't something that I needed to buy a newer program for. 

[Driver170 42]

having no luck just got hit with this never had this one before#

 

 

Version=1
EventType=APPCRASH
EventTime=130506337235628348
ReportType=2
Consent=1
UploadTime=130506337236038372
ReportIdentifier=bd861ee6-12c5-11e4-b46e-bcee7b8c5ef9
IntegratorReportIdentifier=bd861ee5-12c5-11e4-b46e-bcee7b8c5ef9
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61637.0
Sig[2].Name=Application Timestamp
Sig[2].Value=46fadb14
Sig[3].Name=Fault Module Name
Sig[3].Value=ui.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.61637.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=46fadb59
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0003c963
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
UI[2]=C:\FSX\fsx.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\FSX\fsx.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\syswow64\GDI32.dll
LoadedModule[8]=C:\Windows\syswow64\USER32.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\apphelp.dll
LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[20]=C:\Windows\system32\UxTheme.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\samcli.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\MSACM32.dll
LoadedModule[25]=C:\Windows\system32\VERSION.dll
LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[27]=C:\Windows\system32\sfc.dll
LoadedModule[28]=C:\Windows\system32\sfc_os.DLL
LoadedModule[29]=C:\Windows\syswow64\USERENV.dll
LoadedModule[30]=C:\Windows\syswow64\profapi.dll
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[35]=C:\Windows\syswow64\urlmon.dll
LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[43]=C:\Windows\syswow64\iertutil.dll
LoadedModule[44]=C:\Windows\syswow64\WININET.dll
LoadedModule[45]=C:\Windows\system32\MPR.dll
LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll
LoadedModule[50]=C:\Windows\system32\mscms.dll
LoadedModule[51]=C:\Windows\system32\DDRAW.dll
LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[54]=C:\Windows\syswow64\IMM32.dll
LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[57]=C:\Windows\syswow64\NSI.dll
LoadedModule[58]=C:\Windows\system32\msi.dll
LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[60]=C:\FSX\language.dll
LoadedModule[61]=C:\FSX\API.DLL
LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[63]=C:\FSX\ablscpt.dll
LoadedModule[64]=C:\FSX\flight.dll
LoadedModule[65]=C:\FSX\ai_player.dll
LoadedModule[66]=C:\FSX\acontain.dll
LoadedModule[67]=C:\FSX\controls.dll
LoadedModule[68]=C:\Windows\system32\DINPUT8.dll
LoadedModule[69]=C:\FSX\fsui.dll
LoadedModule[70]=C:\FSX\atc.dll
LoadedModule[71]=C:\FSX\facilities.dll
LoadedModule[72]=C:\FSX\demo.dll
LoadedModule[73]=C:\FSX\main.dll
LoadedModule[74]=C:\FSX\fe.dll
LoadedModule[75]=C:\FSX\util.dll
LoadedModule[76]=C:\FSX\simprop.dll
LoadedModule[77]=C:\FSX\g2d.dll
LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[80]=C:\Windows\system32\d3d9.dll
LoadedModule[81]=C:\Windows\system32\d3d8thk.dll
LoadedModule[82]=C:\FSX\g3d.dll
LoadedModule[83]=C:\FSX\panels.dll
LoadedModule[84]=C:\FSX\multiplayer.dll
LoadedModule[85]=C:\FSX\ui.dll
LoadedModule[86]=C:\FSX\sound.dll
LoadedModule[87]=C:\FSX\sim1.dll
LoadedModule[88]=C:\FSX\simscheduler.dll
LoadedModule[89]=C:\FSX\visualfx.dll
LoadedModule[90]=C:\FSX\window.dll
LoadedModule[91]=C:\FSX\terrain.dll
LoadedModule[92]=C:\FSX\weather.dll
LoadedModule[93]=C:\Windows\system32\DSOUND.dll
LoadedModule[94]=C:\Windows\system32\POWRPROF.dll
LoadedModule[95]=C:\FSX\symmap.dll
LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll
LoadedModule[97]=C:\Windows\system32\MSIMG32.dll
LoadedModule[98]=C:\FSX\xuipc.dll
LoadedModule[99]=C:\FSX\livingwater.dll
LoadedModule[100]=C:\FSX\fs-traffic.dll
LoadedModule[101]=C:\FSX\gps.dll
LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[104]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[105]=C:\Windows\system32\rsaenh.dll
LoadedModule[106]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[107]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[108]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[109]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[110]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[111]=C:\Windows\system32\wbemcomn.dll
LoadedModule[112]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[113]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[114]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[115]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[116]=C:\Windows\system32\dxgi.dll
LoadedModule[117]=C:\Windows\system32\d3d11.dll
LoadedModule[118]=C:\Windows\system32\nvd3dum.dll
LoadedModule[119]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[120]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[121]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[122]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[123]=C:\Windows\system32\d3d10_1.dll
LoadedModule[124]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[125]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[126]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[127]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[128]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[129]=C:\Windows\system32\winbrand.dll
LoadedModule[130]=C:\Windows\system32\nvapi.dll
LoadedModule[131]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[132]=C:\Windows\system32\WINSTA.dll
LoadedModule[133]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[134]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[135]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[136]=C:\Windows\SysWOW64\wer.dll
LoadedModule[137]=C:\Windows\System32\Wpc.dll
LoadedModule[138]=C:\Windows\System32\wevtapi.dll
LoadedModule[139]=C:\Windows\System32\msxml6.dll
LoadedModule[140]=C:\Windows\system32\SAMLIB.dll
LoadedModule[141]=C:\Windows\system32\netutils.dll
LoadedModule[142]=C:\FSX\uiautomationcore.dll
LoadedModule[143]=C:\Windows\system32\OLEACC.dll
LoadedModule[144]=C:\Windows\System32\MMDevApi.dll
LoadedModule[145]=C:\Windows\System32\PROPSYS.dll
LoadedModule[146]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[147]=C:\Windows\system32\avrt.dll
LoadedModule[148]=C:\Windows\system32\RICHED20.DLL
Sec[0].Key=LCID
Sec[0].Value=2057
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft® Flight Simulator X
AppPath=C:\FSX\fsx.exe