A320cockpit

I had the same issue. When i started Voxatc after the indexer run once in non network mode and then in network mode, the problem was gone. But i have still the problem that most of the transfered files does not match with the files on the client pc. You can read more details about that in my previous posts. Kind regards Jürgen

Hi James, I got it to run. The problem was my simconnect configuration. You can check the simconnect.cfg on the server and the simconnect.ini on the client. Both files are containing the port number. Make sure to have the same port number in both files. as said, i got it to work but have still problems with the transmitted indexer files. They seem to be different from the source. Good luck! Jürgen

I would prefer a complete uninstall/reinstall to get a clean installation instead of spending a lot of time for error analysis Regards Jürgen.

Congratulation! Do you have a performance hit when running Voxatc? The framerate went down to 15 fps. I have now updated to P3D v4.2 but have not tried it yet.

Hi Charles, Yes, i think you need to do a complete reinstall because the scenery path is related to the Sim path. Regards Jürgen

If you run the Netserver then do not run the Proxy! The proxy is only needed when you want to run the remote panels without the net server.

Hi all, after i got Voxatc working over network, i have a problem that Voxatc think it is a VFR Flight altough a IFR Flightplan is loaded. (when i run Vox on the Sim with the panels on the Sim Screen, every thing is working well). some Flights works also fine over the network as most flights wont. In the logfiles there is a difference between flights working/not working. Example Flight working: bei com.intworkings.voxatc.FlyiInt.GetFlightPlan() 14:54:16.7069149 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\world\scenery\bvcf.bgl 14:54:17.1591217 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\world\scenery\BNXWorld1.bgl 14:54:17.5321358 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\world\scenery\BNXWorld0.bgl 14:54:17.7998779 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_EDRP.bgl 14:54:17.8013814 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_EDFU.bgl 14:54:17.8013814 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_EDSA.bgl 14:54:17.8013814 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_EDNG.bgl 14:54:17.8018590 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_EDFJ.bgl 14:54:17.8018590 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_ETOA.bgl 14:54:17.8018590 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_ETIN.bgl 14:54:17.8023839 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_EDER.bgl 14:54:17.8023839 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_EDSN.bgl 14:54:17.8028850 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\0601\scenery\APX49150.bgl 14:54:17.8334428 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\0601\scenery\NVX06010.bgl 14:54:17.9011503 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\0601\scenery\APX49130.bgl 14:54:17.9247128 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\0601\scenery\APX49140.bgl 14:54:17.9347394 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\0601\scenery\APX50130.bgl 14:54:17.9502776 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\0601\scenery\APX50140.bgl 14:54:17.9718375 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\0601\scenery\APX51150.bgl 14:54:17.9893813 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\0601\scenery\APX50150.bgl 14:54:18.0124179 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\0601\scenery\ATX06010.bgl 14:54:18.1387782 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_ETIN.bgl 14:54:18.1397807 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDFJ.bgl 14:54:18.1402818 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDER.bgl 14:54:18.1402818 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDDK.bgl 14:54:18.1417854 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDNG.bgl 14:54:18.1417854 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDDR.bgl 14:54:18.1422871 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDSN.bgl 14:54:18.1427858 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDSA.bgl 14:54:18.1427858 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_ETOA.bgl 14:54:18.1427858 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDFU.bgl 14:54:18.1432903 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDRP.bgl 14:54:18.1432903 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDFH.bgl 14:54:18.1442689 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_eu\ftx_aa_lowi\scenery\Westsim_Innsbruck_APX.bgl 14:54:18.1452950 BGLFILE c:\program files\lockheed martin\prepar3d v4\ecosystem\aerosoft\german airports - stuttgart p3dv4\scenery\EDDS_AFX-OP02.BGL 14:54:18.1483031 BGLFILE c:\program files\lockheed martin\prepar3d v4\ecosystem\aerosoft\mega airport frankfurt 2.0 p3d v4\scenery\EDDF_AFX-OP06.BGL 14:54:21.0256718 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_EDQE.bgl 14:54:21.0261722 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_EDQZ.bgl 14:54:21.0266740 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_aec\scenery\AEC_Z11O.bgl 14:54:21.0266740 BGLFILE c:\program files\lockheed martin\prepar3d v4\scenery\0601\scenery\APX51140.bgl 14:54:21.0382278 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDQZ.bgl 14:54:21.0382278 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_Z11O.bgl 14:54:21.0387288 BGLFILE c:\program files\lockheed martin\prepar3d v4\orbx\ftx_vector\ftx_vector_apt\scenery\APT_EDQE.bgl 14:54:21.0387288 BGLFILE c:\program files\lockheed martin\prepar3d v4\simmarket\taxi2gate-eddm p3dv4 p3dv4\data\eddm\scenery\EDDM_AF.BGL And flight not working: bei com.intworkings.voxatc.FlyiInt.GetFlightPlan() 15:49:11.7487220 BGLFILE 78906.vidx 15:49:12.2540412 BGLFILE 78905.vidx 15:49:12.5267940 BGLFILE 78904.vidx 15:49:12.9107868 BGLFILE 78925.vidx 15:49:12.9218166 BGLFILE 78918.vidx 15:49:12.9278548 BGLFILE 78919.vidx 15:49:12.9368827 BGLFILE 78975.vidx 15:49:12.9774910 BGLFILE 78976.vidx 15:49:12.9910003 BGLFILE 84084.vidx 15:49:12.9935337 BGLFILE 78915.vidx 15:49:12.9940323 BGLFILE 78914.vidx 15:49:12.9970439 BGLFILE 84022.vidx 15:49:12.9975447 BGLFILE 84021.vidx I know that files like 84021.vidx are transmitted index files but not more.. Has anyone an idea what the problem might be? Regards Jürgen

Hi Charles, may be the problem is caused by the different path where the Sim is installed. Might be Voxatc expect that the Sim is installed in the default path/folder. I know that a lot of users recomment to install the Sim in a separate folder. For me it never made sense to do that. I think LM knows best where the Sim should be installed and if a separate location would be better, the installer would suggest this. I think if the Sim installed in the default path/folder the indexer will run. Regards Jürgen

Have you installed the correct version of Voxatc? If you have installed the version for P3d V4, Voxatc should find the path by itself. Regards Jürgen

The proxy must run on the SimPc. I have tried this with no success...

Hi Dave, normaly it should be enough to run the proxy on the client machine where you also want to have the panels displayed and Voxatc on the Sim-Pc. If you want to try it with the Voxnetserver on the same machine where the Sim is running, then start Voxatc and the Netserver on the Sim-Pc. Then start the Remote Panel Program on the client. When the panel on the client-pc has connected to the Netserver, the red bar changes to green. Make sure that the Sim-pc can connect to the client-pc and vise versa. Check if you can open folders with windows-explorer on the other machines. Regards Jürgen

Hi, does anyone have an idea what the reason is for the following error message? Ins Text set : 7.41 Initializing......... Object reference not set to an instance of an object. at VoxATCServer.VoxATCServer.SetupDestinationMsa() at VoxATCServer.VoxATCServer.InitVoxAtc() 0 Ins Text set : FATAL ERROR! disable VoxATC Object reference not set to an instance of an object. at com.intworkings.voxatc.Dispatcher.SetupUserFlightPlanLocationsForRecognizer() at com.intworkings.voxatc.Dispatcher.Run() Regards Jürgen

Try the following: Close the Sonic Studio App and then try it again without restarting the computer. Have also a look at the windows task manager. If there are still Sonic Studios processes running, just end them before you try it again. Regards Jürgen

Which Mainboard are you using?

Hi Dave, I did it with the netserver and without the proxy. If you run the net server, the Proxy should not be running but you have to run the Net Client Firewall Setup on the Simulator Pc once. I got it running with FSX. Now i tried it in my Homecockpit with P3D V4.1 and nothing is working, also not working in a non network setup... Have you got an error-message? You can create a log-file by checking the option in the advanced settings of Voxatc and then click the save button. Can you tell me what the log-file says? Regards Jürgen