Aerosoft official retail partner for Microsoft Flight Simulator !! 
Click here for more information

Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

-7 Bad

About Senchay

  • Rank
    Flight Student - Airwork

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. There have to be some other bugs with the layering too. Not only related to autodiscovery. P3D (nor simstarter) simply did wrong things in the above mentioned state. There was no way anymore to have WSSS (for example), the one with 4 layers, in a working order. It ordered it always in a way that broke not only WSSS (overlapping with standard scenery, despite it being ontop) itself but caused also other problems. I think you see that i tried very very hard to use Simstarter to fix it but it simply did not work because also SS read the order wrong AND placed the order wrong into the sim. No way to fix it with the functions i know in SS. Ordering manually did not help. And you can also see (also in the post from the other guy) that SS even oders it different from P3D itself. I posted 3 pics of that. And doesnt matter how hard i tried to order the layers in SS, on reload of P3d they were simply in another place again. Impossible to order. Im not sure wich part of lorby did the trick, maybe the deletion of scenery indexes. Maybe other things but that was the only way to fix it. Btw, im not ranting here about SS, i like the tool but im pretty sure there is some thing overseen that causes this problem. Like i also mentioned, SS seems to place addons coming from the addons cfg in another place as P3D itself. You seem to place it before the other addon entries and P3D behind. One question i have now: Is it possible to use simstarter only to start P3D, without it touching my scenery order? I want to use the core set functions to free core 1 but im really scared atm to use it to order scenery. This cost me so much time already and i dont want to end up with a broken sim again.
  2. LorbiSi addon organizer fixed renewing the scenery indexes and using the right prio settings and the layering function it does
  3. I have posted this in LM forum too but make it here too because i cannot see if its p3d or SS or whatever... Long read but im sure it should point devs somewhere. Its just a copy& paste so dont wonder that i talk to LM there. And i found how to fix it. Now someone from LM really should read this....I feel like talking to myself. This seems to be clearly a P3D thing. If not then please reply so i can let the dev know about it. Maybe it has to do with WSSS having 4 layers or whatever, i dont know. But this is the way i can fix it so both, Simstarter and P3D are showing the same thing. And where WSSS doesnt overlap with standard scenery. The file add-ons.cfg in C:\ProgramData\Lockheed Martin\Prepar3D v4 When one is installing WSSS, at least in my case it will be added as [Package.0] PATH=E:\P3D\Addon Scenery\ImagineSim\WSSS Singapore P3Dv4 TITLE=Imagine Simulation WSSS2_PD4 ACTIVE=true REQUIRED=false The next entry for me is [Package.1] PATH=E:\P3D\Ecosystem\Aerosoft\Aerosoft-Maastricht TITLE=Aerosoft-Maastricht ACTIVE=false REQUIRED=false and this continues up to [Package.51] PATH=C:\Users\Alex Wolff\Documents\Prepar3D v4 Add-ons\UUEE Moscow Sheremetyevo X ACTIVE=true REQUIRED=false Now, if one looks here one can see that UUEE is the very first shown here on top (next to WSSS). That one has the number 51 in that file. But WSSS has 0 (zero). So i wondered why WSSS is Nr 0 BUT also stays ontop after first install, at least for a short time. Maybe 1 simstart or until another addon xml scenery is installed. Then it gets split up to something like this Where 2 of the 4 layers stay at top and the other 2 end up at the bottom of all addon xml entries. or somewhere inbetween. What i did now is ordering the numbers so WSSS is entry [Package.52] PATH=E:\P3D\Addon Scenery\ImagineSim\WSSS Singapore P3Dv4 TITLE=Imagine Simulation WSSS2_PD4 ACTIVE=true REQUIRED=false instead of 0 . So now WSSS is nr 52 (the very last one) and UUEE has this [Package.51] PATH=C:\Users\Alex Wolff\Documents\Prepar3D v4 Add-ons\UUEE Moscow Sheremetyevo X ACTIVE=true REQUIRED=false THis is also what the pic above would reflect. That makes at least some sense. But WSSS being 0 and UUEE being 52, still have postion next to each other doesnt make any sense to me. Now WSSS stays at pos 1, with all 4 layers together how they belong The same is reflected by Simstarter now too As soon WSSS is Nr 0 again it gets split up in 2 parts, causing problems for seemingly the whole sim. I tried it. Putting it back to the last numbers fixes it again. What i ALSO had to do is to delete all entries out of C:\Users\sdsdsd\AppData\Roaming\Lockheed Martin\Prepar3D v4 Flytampa chose to add their entries there for whatever reason. And i saw that also causes problems in 4.4. So i deleted them. The whole file is empty now. P3D would put those ones after the rest of addon xml entries while simstarter puts them ontop. Something is clearly wrong how 4.4 (or SS too probably...) handles the order of entries, as can be seen here. Now please someone respond to let ppl fix this if its not a P3D problem. I dont care anymore who is "at fault" but i know that i wasted probably over 20h to get into the root of this. Its not my job, every developer seems to put the fault to someone else or doesnt even respond at all. Thats so bad... Again put together: If my scenery library consists of the addon.cfg from %appdata% AND the addon cfg from %program data% AND scenery cfg entries i CANNOT fix this at all because then the ordering is fully broken and weird things happen. Maybe this happens only with lots of scenery i dont know anymore... But its like that. If i only have the entries in the addon cfg in %program data% and scenery cfg entries i can fix it by putting the last installed WSSS as the last position in the addon cfg (nr 52 in my case), instead at nr 0 where it will be installed. Then it all works fine, no overlapping of scenery at WSSS I hope i could make it clear. English isnt my native language.
  4. Maybe a hint whats going on here I saw for example that SS places entries coming from the addons.cfg in programdata infront of all addonxml entries. But P3d would put it at the end
  5. I would love to see a fix here now anytime soon. It starts to get a bit tedious, sorry for the pressure....Its reported by other ppl here too in the other post. Even "import scenery cfg doesnt do anything in this state. WSSS is always splitted. Among other weirdness. THis problem cost me at least 25h the last 2 months. Its not funny anymore
  6. "When I now add another scenery in P3D (installation outside SS) I then find the new scenery in ALL the scenery sets I made. Is that normal?" Yes that is normal. "My second question is : is there a way to select multiple lines in an scenery set (I can select with Shift) and then mark them all at once? I can multiselect but only can mark one line at a time." Not sure i understand this one right. You already say you know you can do it with shift so i probably misunderstand something and my answer wont be the one you seek. If you multiselect (either with shift or any other way) you can see a dropdownlist at the bottom of Simstarter. Here you can choose of you want to turn the selected ones active in all scenery sets or only in this one. See the pic what i selected at the bottom.
  7. That tool didnt found any errors. It reregisters the installer service, thats all. Also other .Net ++ libs seem to all be fine, either they do nothing on a repair or they say "everything already up to date". Besides that i code in VisualStudio and didnt found a problem so far.
  8. Sorry but there is something really wrong... It just doesnt work anymore as it should, i dont what to do... Now every airport i install ends up at the bottom of the list.... below all terrain. Look down for Maastricht. In P3d this is where it should be As if it swaps the order around as it sees fit. Can it be that SS has a problem to read/work with lots of seems as it broke at 1 point where the entries went above 290.
  9. Yep, i can reproduce this. It nearly has to be WSSS and maybe not related to SS but to the p3d files. If one compares the first pic up in last post there is ZUUU last, wich is right but then there is Moskow, and that is not right. What is right (that was the very last state of a working sim for the last 3 days) is the one shown here, ZUUU, Toronto, Boston, Vienna. And SImstarter really reads this "old" order, despite P3D this time showing something wrong....because now when i open P3D ZUUU ist last but again or still Moskow follows. So weired...
  10. I have "investigated this a bit further". The problem may be really related to WSSS scenery. I mean how SS is reading this (the scenery has 4 layers), or maybe really that something happens in the background in some addonxml file or something. I nearly wanted to write here today that i fixed it because the last 3 days this misordering didnt happen anymore. I deinstalled WSSS and a few other airports and from that moment all stayed the same. I also installed ZUUU and KPDX again and there was no problems. When i opened SS after this i saw them in right place in SS and Sim. No i reinstalled WSSS and suddenly the same happens again. If i open Simstarter now last installed airport ZUUU went down 30 or so numbers from Pos 1 to 40 or something. I bet that when i start sim now i get same behaviour again. It would be amazing if we can figure out why this happens, otherwise its either SS or the scenery. I dont want to make such choices... Would be great, thanks. I can send you all you want.
  11. Same here. 4.4, AS320 CFM, Win 1809, RTX2080, i7700K Running as admin, installed patch over Manager. (Latest Experimental update Flightplan EPAM1L EPAMA UN733 PRADO PRAD1J Holding was on the last WP before going to ILS. Was cruising, then i wanted to enter a holding near LEMD and the sim crashed same moment as i pressed Hold. Latest Navigraph AIRAC. Name der fehlerhaften Anwendung: PREPAR3D.EXE, Version:, Zeitstempel: 0x5bfdbb35 Name des fehlerhaften Moduls: FMGS.dll, Version:, Zeitstempel: 0x5c5dbc2a Ausnahmecode: 0xc0000005 Fehleroffset: 0x000000000004e682 ID des fehlerhaften Prozesses: 0x2080 Startzeit der fehlerhaften Anwendung: 0x01d4c4a8316a6c2e Pfad der fehlerhaften Anwendung: E:\P3D\PREPAR3D.EXE Pfad des fehlerhaften Moduls: E:\P3D\Ecosystem\Aerosoft\Aerosoft A320-A321 Professional\SimObjects\Airplanes\Aerosoft A320-A321 Professional Base\Panel_Fallback\DLLs\FMGS.dll Berichtskennung: c2aa406f-7213-4e75-9ba9-d6de14cd7cfc Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Anwendung: PREPAR3D.EXE Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 00007FFD9BD9E682
  12. Yeah, here it shows the same. Pretty different order of what i see in sim as i start SS with
  13. Hello again. I saw this topic here but its late and i cannot really read through all of it, it may be related. But i dont use any lorbySi addonmanager so i open a new topic. Hope thats fine. My problem is that SS constantly changes my order of the library, causing the sim to "break". THis break means that my mesh doesnt build like it should and that some scenery are overlapping with standard scenery. WSSS from Imaginesim is a good example. I try to explain... not so easy. Lets say i have my sim running fine and the Order looks like something like this (all Addon XML entries here at beginning) 1. KSFO 2. KPDX 3. KSDF 4. ... and so on Then i install a new airport, lets say WSSS (also over addonXML) When i open P3D the first time after install it happens what should happen (for my understanding) and it willl look like this: 1. WSSS 2. KSFO 3. KPDX 4. KSDF 5. ... and so on Then as soon i start SS it corrupts this order and suddenly WSSS comes somewhere in the middle of everything. Like this 1. KPDX 2. KSFO 3. WSSS 4. KSDF 5. ... and so on Now this would be a big problem but exactly this leads to my sim being broken. Now scenery of standard overlaps WSSS, despite it being still "somewhat" in the right position (above all standard scenery) and for 100% (im really sure on this one.... i know my sim very well) the mesh simply doesnt load anymore as it should be. Its very slow in building up and the sim is blurry like hell. Im known to have a beatiful sim where everything is unbelievable crisp. But when this happened i get blurries all over the place after short time of flying. What can that be? This is how it looks like right after install. When i start my sim now all is fine. No overlapping and all crisp and mesh builds as usual. But in Simstarter the WSSS stuff splits at first start of SS so the half of WSSS stays at top and the other 2 go somewhere below. A second start of SS causes all the WSS stuff goes below in the middle of it all, staying in the "right" order. With right order i mean the order of the WSSS stuff. It comes together again after the split in first start of SS, just not at the top anymore but somewhere inbetween. I can also not order it anymore by all means. When i try to bring WSSS up to position 1 and click ok it will end up below again. No way to order it.
  14. At least i have, yes. I saw that posts about the needed fps for flightmodel to update in other topics so this is also what i usually tell others when they experience problems. This problem is not related to a certain moment only. If it appears there is no way to revert from this state anymore. It happens with 40, 50 and 60 fps. Not something like the random weird behaviour when fps may be low. THis is different and its a broken state somewhere, of something. For example: i have mentioned i tried to manually get rid of the small speed value. For me it was always 192 kts where it reverted to when going into managed mode, despite i saw something like 0.76 there. Then i scrolled forward in the flightplan and i found this value, the 192 written next to the the T/D marker on the FMC flightplan. Where usually the speed is written like 0.77/320. Here this 192 was somehow hardcoded and no matter what i manually set on all waypoints below or after the T/D reverted to this value.
  15. Nope, i didnt use them and this same thing occured (see here, i reported with pictures) It also has nothing to do with FPS. When this occured i had 31 of 31 locked frames per sec.Like always, it usually doesnt drop below this if not in very heavy areas directly on the landing.
  • Create New...