Jump to content
The simFlight Network Forums

christian1974

Members
  • Posts

    29
  • Joined

  • Last visited

Everything posted by christian1974

  1. @youngGun821 Maybe the error you get of because of this line Local="D:\Games\My TrafficFSX\MyTraffic\Aircraft" should be this Local="D:\Games\My TrafficFSX\MyTraffic\scenery" I doubt there is a scenery directory under the aircraft folder - nor are there the additional scenery-bgls and the traffic-bgls Kind regards Christian
  2. Just to be sure... You are sure you disabled the files correctly? The new Windows-Versions (since Vista I think) don't show the full filename by default. So if you only see "BR2_EDDF" with filetype "bgl" (which is BR2_EDDL.bgl in full view) in your Explorer The simple renaming to "BR2_EDDL.bgl.passive" with filetype "bgl" won't fulfill your needs as in full view it would be "BR2_EDDL.bgl.passive.bgl" and therefore it would still be recognised as a part of a senery. So please make sure that file-extensions are shown in Windows when you rename files manually. I'm just saying this because in the past often users in other forums had difficulties in renaming files correctly.
  3. Hi tesza please check if you have a quite big file in your F:\MyTraffic Professional\MyTraffic\Scenery - Directory Should be around 125MB and is called "Mytrafficcommercial.bgl" (or something like that - I'm not at my home-pc at the moment) and there should also be two others ("Mytrafficglobal.bgl" and "Mytrafficmil.bgl" - I think) Also check if the following file is set to passive: "trafficAircraft.bgl" (should be "trafficAircraft.bgl.passive") in F:\Microsoft Flight Simulator X\scenery\world\scenery\ If all this is ok there must be other things that your traffic does not show up (mabe old traffic-bgls from another addon). You are sure you edited the right fsx.cfg file and the right scenery.cfg (there sometimes are more than one!)??? The right fsx.cfg is in here: C:\Users\YOURNAME\AppData\Roaming\Microsoft\FSX The right scenery.cfg is in here: C:\Users\All Users\Microsoft\FSX All the so far given information are also in the new "MyTraffic 6 Installation Guide.pdf"... ;-) Regards
  4. Hi tesza Guess this is not what burkhard advised. The entry in the scenery.cfg has to be: Local=F:\MyTraffic Professional\MyTraffic The entries in the fsx.cfg must be changed as follows: Delete the SimObjectPaths.6 line and change the SimObjectPaths.7="F:\MyTraffic Professional\MyTraffic\Aircraft" to SimObjectPaths.6=F:\MyTraffic Professional\MyTraffic\Aircraft This should solve your problems if all the rest is setup correctly. Kind regards Christian
  5. Sorry can't say more as I don't use MT-Interactive. If you have the trafficdatabasebuilder just copy it to the mytraffic directory. Does not harm if it is there. From the "normal" mytraffic installation there should be 3 mytraffic traffic.bgls in the mytraffic\scenery directory. One of them should have around 125Mb.
  6. Hi There are two SimObjectPaths.6-entrys in your fsx.cfg. Think the second one (not related to MyTraffic) has to be deleted.
  7. Hi As MyTraffic refers to FSX stock airports there might be incompatibilities with Addon airports. Go to your MyTraffic\scenery directory and change the file extension from ".bgl" to ".off" at all airports you have problems with. So BR2_KDEN.bgl will become BR2_KDEN.off Maybe there is more than one file for an airport. Make sure to disable all. After that the problem should be gone. Kind regards Christian
  8. In your scenery.cfg The mytraffic entry [Area109] guides to the wrong directory. Should be: Local=G:\MTX6\MyTraffic. Also the SimObjectPaths-entry in your prepar3d.cfg is wrong. Should be: SimObjectPaths.7=G:\MTX6\MyTraffic\Aircraft Kind regards Christian Edit: Sorry didn´t know about the simobjects.cfg as I only own FSX and thought the configuration files are same ones ;-)
  9. Hi Tom. You cannot disable the installation of the new airports in a classic way. Which should say they are all installed automatically. As MT6 should be blow your Addons in the scenery libary there normally should be no problem. But as MT6 is bgl-based you are able to disable these airports manually by changing file-extensions from ".bgl" to ".off" if there is a problem. Kind regards Christian
  10. Hi Tom. I have installed MT6 and I have traffic at OTHH. You don't have to do anything except following the installation instructions.
  11. Hallo also ich habs jetzt ausprobiert, und irgendwie hat es nicht hingehauen. Hatte zwar Traffic - von daher scheint das compilieren ja geklappt zu haben, aber eben kein Traffic auf OTHH UND OTBD. Ich warte jetzt bis MyTraffic dann mal angepasst wird. Solange neheme ich halt sie alten Traffic bgls. so I tried the thing you suggested but somehow it didn´t work. I had traffic elsewhere - so compiling must habe been ok - but not at OTHH and OTBD. Therefore I now wait mytraffic to be addapted to the new airport. As long as I´ll be waiting I take my old traffic bgls. Gruß/ kind regards Christian
  12. Just to be clear: The changes in the MyComercialRoutes.dat file must be done nevertheless??
  13. Thanks for your instructions. Will give it a try tomorrow evening as I am quite busy today.
  14. Hi Burkhard. I gave it a try and replaced OTBD by OTHH in the MyComercialRoutes.dat file (2013Plans) and after that I selecteted the schedule in the communicator to force a rebuild of the traffic-bgls. But I fact I then had still no traffic at OTHH and also no more traffic at OTBD. Is this really the only file we have to change? In fact I think everyone would be very very very happy I you could somehow manage to make the new airport work with mytraffic. Kind regards Christian P.S.: I think we will have the same problem in future when AS releases its new Johannesburg scenery. There the airport code changed too i think
  15. Hallo Volker Also da es ja kein wirklich schwerwiegendes Problem ist, kann ich mit der Antwort irgendwie leben. Bisher war es nur immer so, dass der eingestellte Flightlevel auch immer genauso im FSX-Flugplan übernommen wurde. Aber kann natürlich sein, dass das heute ganz besondere Umstände waren bei meinen Flügen. Ist ja auch in sofern nicht schlimm, da man den Flugplan ja im FSX notweise nochmal mit der richtigen Flughöhe speichern kann. Oder ich starte demnächst den FSC halt immer neu. Kannst das Topic wenn du magst schließen. Gruß Christian
  16. Hallo Volker. Kein Programm meldet einen Fehler. Es ist nur so, dass ich im FSC für nen Flugplan einen Flighlevel festlege. Den Flugplan speichere ich ja dann ab. Also auch als FSX-Plan. Wenn ich diesen dann später im FSX lade, bekomme ich dort dann einen ganz anderen Flightlevel angezeigt. Beispiel: im FSC FL015 im FSX dann FL290. Das ganze passiert aber erst wenn ich mehrere Pläne hintereinander erstelle. Der erste ist immer ok, der zweite oder die folgenden Pläne haben dann diese Flightlevel-Abweichung. Sorry ist nicht besser zu erklären. Aber wie gesagt: Es gibt keine Fehlermeldung von irgendeinem Programm. Gruß Christian
  17. Hallo Volker Vergiss was ich oben geschrieben habe. Denke das Problem ist ein anderes. Wenn ich einen Flugplan erstelle und diesen exportiere, kann ich ihn ohne Fehler einladen. Erstelle ich danach direkt einen neuen Plan, kommt es zu dem Fehler, dass die Höhe nicht richtig übergeben wird. Beim ersten Plan ist die Höhe in roter Schrift, beim zweiten Plan dann in blauer Schrift. Der FSC wurde zwischen den Plänen nicht neu gestartet. Gruß Christian Hi Volker Forget about the things I wrote before. The problem exists in 9.2.1 too. It happens when creating two flightplans after another. In the first plan, the hight is displayed in red and its loaded right into FSX. In the second plan the hight is displayed in blue, and when loaded into FSX I get the wrong Cruiselevel. FSC is not restarted between the two plans. Kind regards Christian
  18. Hallo Volker Erst einmal ein großes Dankeschön für das neue FSC update. Doch leider habe ich damit ein kleines Problem. es scheint, dass seit dem Update die Flughöhe aus dem Flugplan nicht mehr richtig in die exportierten FSX-Plandateien übertragen wird. Habe heute mehrere IFR-Pläne mit unterschiedlichen Flughöhen erstellt (von 8000ft bis 15000ft), aber immer wenn ich den Plan dann in den FSX geladen habe, hatte ich eine Flughöhe von 29000ft. Kann es sein, dass das mit dem Update zusammenhängt. Vorher hatte ich dieses Problem nicht. Ich werde nun nochmals mit der alten Version 9.2.1 testen, und dann berichten. Evtl kannst dir das Problem ja mal ansehen. Gruß Christian Edit: Die Version 9.2.1 scheint den "Fehler" nicht zu haben. Hier werden die Flughöhen richtig übertragen. Hi Volker First off all a great thank you for the new 9.2.2 update. But unfortunately I got a minor problem with it. Today I created several IFR-flightplans with flightlevels from 8000ft to 15000ft. But I seems that these hights are not transfered to the fsx flightplan-files anymore after the update. Every plan that I Imported in FSX got a flight level of 29000ft. I will now test with the old 9.2.1 again, but as far as I remember I did not have this problem with the "older" version. Maybe you could please have an eye on this topic. Regards Christian Edit: The old 9.2.1 seems not to have the "error". It transfers the flightlevels as they should be.
  19. Hi Burkhard I now installed the last patch (2.66MB) and - to me - now all seems to be ok means the big worst errors are killed ;-). Sure there have been some errors left, but as you say and explained these seem to be intended. So I will no longer regard them as errors (Hope I remember them at the next update :D ). It was a pleasure to help you. Kind regards and - hope for the last time now - a happy new year. Christian
  20. Hi Burkhard Looks much better now but there are still some errors concerning textures. But maybe as you already told they were intented. Attached is the new report. I left out all the texture.blank errors this time. Concerning flusifix I have to say that it never damages anything at my installation. But maybe it is like with all software: You simple have to know what you are doing when using this programm. Kind regards Christian Edit: Report deleted due to no more errors with the lastest Patches54b (2.66MB)
  21. Hi Burkhard If the MD11FMX cfg-file was for the MD11FMX-Folder we surely gett much less errors. Concerning the intended errors maybe you could include a short textfile in the updates which contains the liveries that are not used (anymore). So it would be easy to work out if there is a real error or if it is an "intended error". And maybe you will get Flusifix sometimes for yourself. As you see it is quite helpful in finding errors ;-) http://www.flusifix.de Please tell when the new Patch - if there wil be one - is ready. I´ll do another test then. Kind regards Christian
  22. Dear Burkhard I downloaded the new Patches54b.exe this morning (size was 2126KB) and let it run over my clean installation (I backed-up my celan installation from yesterday before editing the files). After that I run the Livery-Check again. First of all: Was the MD11DMX -folder supposed to be in the update? It causes many errors as there is only a cfg-file inside. But there are still other errors... I did this time an rtf-Dokument again, because I marked bad errors in red and try to give a solution in green. Maybe it helps. Remark to other users. Please let Burkhard do the update. Do not change files by yourself. Me and Burkhard do not take responsibility for problems you might get when you do the changes by yourself. Kind regards and a happy new year Christian Edit: Report deleted due to new one
  23. Dear Burkhard Just for a brief information. The patch I downloaded this morning was about 990 KB of size. So this might not be the last file availible. First of all I fixed all errors i found. Maybe I give your Patch another try next year. New year new luck ;-). Kind regards and a happy new year Christian
  24. Dear Burkhard I got a new error report file for you - a error report after a clean install. First of all I uninstalled all of MyTraffic that was on my harddisk acoording to the manual. After a computer-restart I even did a registryclean to make sure no old fragments are there. After another computer-restart i started reinstalling my traffic. All with admininstartor rights an with no virus scanner active (System is WinXP 32bit SP3) I first installed the file MTXV54a.exe that I downloaded from simmarket. After finishing the installation and creating the necessary cfg-entries, I installed the file MTXU54ab.exe which I downloaded from your fsrail page. Finally I updatetd with the file Patches54b.exe that I also downloaded from your fsrail page. Installation went fine. But then I did the Flusifix-Livery-Check again. What should I say: massive errors after a clean installation and no, I haven´t change any file at all. By the way you are right about the mirage3 model. It was fine after installing 5.4a! After installing update to 5.4b and the patch to 5.4b, it was not fine anymore! I don´t know when the change happened. I now will - again - correct the files/errors by myself! Maybe I´m the only one having these problems, but some errors are due to misspelling some words, or just mixing up some caracters. Buts this has a great influence. Maybe in the update/patches there have not been the last files you got on your computer. I don´t know. Attached is the new/clean error report. Kind regards Christian Edit: Report deleted due to new one
  25. Dear Burkhard For sure I got full control over the MyTraffic folder as I'm running WinXP as the only user and with administrator rights. And yes I refer to version 5.4b professional. First I installed 5.4 then the incremental updates to 5.4a and then to 5.4b. Today the communicator loaded the patch mentioned in my last post. If I find the time this weekend I will do a complete clean reinstall. Unfortunatally I then have to do all my changes again :'( but that was only about 2 days of work. Kind regards Christian
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.