thenikos

hi everybody, i dont know if it exists (i searched but didn't found it-bad me if it exists), a sticky topic about real life atc procedures we should follow on pilot2atc to make the flight as realistic as possible. i will give an example and if dave or somebody else who is responsible and know how to use the forum, can make it sticky. when i start a flight i do this on pilot2atc: 1. i connect to atis and listen the atis transmission. then based to active departure runway i make my ifr plan (without choosing arrival star and approach) and fix the altimeter 2. request clearence on my ifr plan and get the squawk code 3. request pushback and engine start 4. request taxi to active runway 5. request takeoff 6. during flight i follow some basic procedure , alt changes, radio freq changes. 7. when i get close to the arrival airport i get from atc the active arrival runway and the star (because i think this happens in reality) 8. i land and ask for taxi to a gate now the questions: is it like that in real life? also when we get to the gate, is there a final request or info to the atc that we arrived and we get off the plane? i think if any of you would have to add any real life atc procedures that might exist or not in pilot2atc, it can help dave in the future to improve it thank you

i found the solution !! (i think) but i dont have much time to test it. when we shut down the plane (or we start from cold and start) everything is switched off. the plane is at 0 state. we switch on the battery or the external power unit and we have the 1st electronics work in the plane, together with the radio the radio starts with vhf l button, light on. if we try to get a radio freq by pilot2atc at that moment, whatever it happens we get 136.975 freq. but if we switch on the radio volume of vhf l, 1st arrow in the row there, then the pilot2atc gets the right freq !!!!

hi again. unfortunately not even the walkaround works: when i start the plane in cold and dark state, even if the ignore avionics switch or/and the ignore battery switch are checked, the radio on pilot2atc gets always the 136.975 freq. for dave: do you have pmdg 747 v3 to replicate the situation? thanks

hi dave ! thanks for your answer. i am not sure if i understood right what you wrote (sorry my english...). or maybe i didnt replicate the problem right: i give power to the plane. it is working fine. it even ... fly 🙂 but the problem is that the radio on pilot2atcget the freq 136.975 (all of the radios, atis, grd, twr) and it never work again. the radio on the plane, works fine but whatever freq i give it, it doesnt pass to pilot2atc. pilot2atc remains at 136.975 this happens only if i start the pmdg 747 v3 from start and cold. if i start it with the default state everything is working. and thanks for the work around, i will try it 🙂

sorry to write more 🙂 i also did another test: started the plane in default state, switched it off, to dark and cold state, manually. i followed the tutorial of pmdg. then i started it back and again i lost contact with pilot2atc. when i do everything step by step, the last moment pilot2atc loses the freqs is when i turn off the battery (without external power of course). if that moment ext pwr exist, everything is ok. but when i cut off the electrical power to the plane, the freq in pilot2atc change to 136.975 and does never come back. i have to load default state.

more observations: lets say i start the plane in default condition. pilot2atc freqs work perfectly. now, without disconecting, i change to cold and dark. freqs dont work. then again, without disconecting, i load again default, freqs work !!

hi (again), since yesterday i started using the pmdg 747 v3 in cold and dark mode. but i cant make pilot2atc connect right to it. the problem is with the frequencies of the radio. i connect to the simulator, i see my plane on the map in the right position, when i go to nearby freqs page, i see them right but when i click on one, in the stby freq i get a number which is not right. for example in lgsa airport, the atis freq is 130.17 and i get 136.975. the same happens with the gnd the twr etc. i always get 136.975. when i use the plane in the default mode, ready to take off, everything is working right. i also tried to put the freqs inside the plane, i see them right on the panel of the radio, but they dont change in pilot2atc. the problem is with the stby freq because when i face this problem if i disconect and connect again then i get the atis right and i hear the msg. but when i try to change to any other freq (twr, gnd) i always get the 136.975 freq. even if i go back to atis again. any ideas ? thank you !!

hi again, now everything is working fine. maybe it was a server problem. thanks

hi everybody, since yesterday the ter map mode does not work for me. all the other modes are working fine, zooming, unzooming etc. when i press ter mode, i just see a white page and sometimes i get the msg exception the operation has timed out. this also results when i choose sids/starts/app not to be able to see the map. just the exception message. any workaround in that? thank you

berts i never said it was plane's problem !! 🙂 ******* !!! i clearly said i was sure something i forgot 🙂 or did wrong. or didnt switch on. in our case if the reserve is mandatory to make vnav work, then it was the tutorial fault not mine 🙂 it said the entry is purely advisory. there should be written that in case you dont fill it , vnav will NOT work 🙂 so people like me (yes i know bad ones who accuse the plane), would put the entry from the beggining. saying good night, i made a test flight with vnav and is ... amazing 🙂 what i was missing so long time i didnt use it 🙂 thank you all for your help !!! ps. im sure i will ask more stupid questions in the future because just now i found time to read the 2500 page (in total) manuals 🙂 so i do experiments on what i read.

hi again: i found a mistake comparing to the tutorial: i didnt put reserve fuel. at the tutorial it says that this entry is purely advisory. i left it empty and vnav didnt work. now i put a value and vnav works. do you think that was the reason? thanks

hi scandinavian and thanks for your reply. of course i didnt say it is a pmdg problem. otherwise i wouldnt ask what i forgot or what i did wrong. thats also i said maybe it is the low altitude? or the short distance? i am the problem thank you for telling me 🙂 as i also stated i started the plane in dark and cold. the example on the tutorial is based on the default condition. thats why i also asked if i forgot something (to switch on i mean) that is related with the vnav. and to your question: no, there is no arrow, just the gr wt value of 552.7 for me.

hi, i tried today for 1st time, to use the vnav, following the tutorial (from cold and dark state). when i press vnav i get the msg perf/vnav unavaible. for me, i did everything right. in my demo flight i created, the only "strange" is the very short flight, lgsa to lgav, at 11.000 alt at a distance of 144nm. i used fuel 55.000 (25.000 for the flight in safety) plus 30000 for the wings as the example says. i put right the temperatures for takeoff (27c that moment +15 , plus a little more) 55 in total. trim also calculated 5.7 and put. v2 of 153 also at the spd ready. i dont know what else it could be. i read many times the tutorial example and there is nothing different. any ideas pls? thank you

i just got the 0.4 update and i managed to create the log file with the new version. i am sending it to the email. thanks

hi keven and thank you for your fast answer 🙂 everytime i try to generate the report file i get this : something unexpected happened:/ it looks like something unexpected occured. a log file will be sent to fsfx packages automatically is the same when the program crashes without reason (that moment i don't use it-i just fly the pmdg 747 without changing views)