Bjartie

I've tried that but no change. I've been trying to post on the AIG forum but for some reason it is not letting me. It says one of my answers is not correct when it is. Frustrating! That said, all in all it is a minor problem, but an irritating one.

Hi Ray, all my AI aircraft are AIGFP. I have the P3D and VOXATC traffic at zero.

I flew from KSAN to KLAX (no ORBX) and same thing. No AI traffic at landing, closed TC, restarted it and the aircraft were there. I'm giving up for tonight. Tomorrow is another day.

I agree that it probably an AIGTC issue. I deleted the traffic controller and reinstalled, no joy. I have ORBX England installed, could it be an ORBX issue? I'm flying from EGGP to EGCC as a test. I'll try somewhere I don't have ORBX installed.

Yes AIG traffic is at 100%, P3D traffic is zero.

I recently had to reinstall my P3dv4 (long and boring story). Most things are now fine but this vexes me. At my starting airport there are plenty of AIG AI airplanes, and they show up during flight. I can hear them on the ATC radio. But when I land the airport is empty, no planes at all. Now comes the even weirder part, I close Traffic Controller, and then start it again and presto, all the AI aircraft are there. This never happened before. I must have done something with the Traffic Controller. I have updated AI Manager and saved. Same problem, I'm stumped. Could it be something with the Simobjects.cfg?

I want to have P3Dv4 on drive E and VOXATC to work, that is all.

OK, I've had a couple of crazy ideas. The first one is move the sim back to E and then never tweak anything ever again. That would mean I don't use the VOX indexer so there should be no problem. The problem is that I like tweaking, like adding ATIS or ILS to an airport, or new aircraft, which means I need the VOX indexer. My next crazy thought is to have the sim on BOTH C and E. Would that mess things up? Maybe I could keep only elements of the sim on C to "fool" VOX tat it is on C when it really on C. I sent an email to the VOX website but I'm not expecting an answer any time soon.

When I tried to install VOX when the sim is in E the indexer never gets going as its path is C. I never got past this first indexing so it never gets to panel setup. If I interrupt the indexing the installer goes on and then tells me that VOX has been installed successfully, but it hasn't.

Hi John Martin. I don't understand your answer. My folders/data files are on drive C:. P3Dv4 works fine wherever it is, the problem is VOX. Do you mean that I should move my folder/date files to E:? Is that possible? Would VOX then "think" that is in E: when I run the indexer?

I've had to reinstall VOXATC but I have a problem. I had my P3Dv4 and VOX on drive E. I want to keep both of them there. I can get VOX to work if P3D is installed in C: drive but on E: drive. Maybe not a big deal but I have my reasons for keeping the sim off of C:. I had an old computer crash and burn, and since all my sim stuff was on C: everything had to reinstalled. If that happens again and the sims are on E:, which is a physically separate drive, it would save me a lot of bother. When I have the sim in E: VOXATC still thinks it is in C: and the indexer hangs. I'm using VOXATC version 7, and as far as I can see there is no place to point it to the correct path. It asks me where I want to install Internal Works, but nothing about where the sim is. It worked like a charm before, so I don't know what has happened.

I found a work around. I gave up on the dsd files after a lot of variations. I found an old Rikooo Embraer 135 that had callouts, and copied the code from the panel there and it works! It is different from the set up that I had before when I used the dsd files. but it works and that is the most important thing. Thanks for your help. Bjartie

Here is my sound.ini, as far as I know everything seems OK [Config] MaxSounds=14 ErrorFlag=0 [Sounds] Sound00=./Sound/CALLOUT/10FT.wav,100 Sound01=./Sound/CALLOUT/20FT.wav,100 Sound02=./Sound/CALLOUT/30FT.wav,100 Sound03=./Sound/CALLOUT/40FT.wav,100 Sound04=./Sound/CALLOUT/50FT.wav,100 Sound05=./Sound/CALLOUT/100FT.wav,100 Sound06=./Sound/CALLOUT/500FT.wav,100 Sound07=./Sound/CALLOUT/1000FT.wav,100 Sound08=./Sound/CALLOUT/2500FT.wav,100 Sound09=./Sound/CALLOUT/MIN.wav,100 Sound10=./Sound/CALLOUT/APPMIN.wav,100 Sound11=./Sound/CALLOUT/200FT.wav,100 Sound12=./Sound/CALLOUT/300FT.wav,100 Sound13=./Sound/CALLOUT/400FT.wav,100 [LVars] Lvar00=CA_Sound00 Lvar01=CA_Sound01 Lvar02=CA_Sound02 Lvar03=CA_Sound03 Lvar04=CA_Sound04 Lvar05=CA_Sound05 Lvar06=CA_Sound06 Lvar07=CA_Sound07 Lvar08=CA_Sound08 Lvar09=CA_Sound09 Lvar10=CA_Sound10 Lvar11=CA_Sound11 Lvar12=CA_Sound12 Lvar13=CA_Sound13

I have just tried gauge35=dsd_p3d_xml_x64! sound, 0,0,0,0, .Sound\CALLOUT\sound.ini without the "Callout_Sound" at the front, and have added "x64", which I think is right and still no joy. Very frustrating as I had this working perfectly in my old computer.

Hi Jorge! I took your advice and checked the error reporting file and indeed my gauge was wrong, it was 32 bits. I changed it to the 64 bit version but no joy and no error in the error report. I still think I am doing something wrong in the path. Regards, Bjartie