Jump to content

Senchay

Members
  • Content Count

    54
  • 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 wr
  2. LorbiSi addon organizer fixed it..by 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 P3
  4. Maybe a hint whats going on here https://www.avsim.com/forums/topic/549716-p3d-44-addon-autodiscovery-broken/ 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 multise
  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 scenery.....it 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.
  11. Same here. 4.4, AS320 CFM, Win 1809, RTX2080, i7700K Running as admin, installed patch over Manager. (Latest Experimental update 1.2.3.1 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: 4.4.16.27077, Zeitstempel: 0x5bfdbb35 Name des fehlerhaften Moduls: FMGS.dll, Version: 2.64.0.94, Zeitstempel: 0x5c5dbc2a Ausnahmecode: 0xc0000005 Fehleroffset
  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 en
  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
  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...