Jump to content

daan_vb

Members
  • Content Count

    300
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by daan_vb


  1. AS is using the same cloud "textures" as what is provided by MSFS but its how the clouds are generated and depicted that is what is different. I agree that perhaps the AS depicton is perhaps a little too flat at times, but its not unrealsitic to see these type of clouds, whereas MSFS weather seems to go to the other side of the spectrum and gives a lot of puffy, fluffy clouds, which are probably more visually spectacular but not necessarily realistic in all situations. There have been many critisicms of MSFS weather but its funny how now all of a sudden its the best thing ever....AS has just been released so it will only improve i'm sure

    • Like 3
    • Upvote 1

  2.  Have they done the flight with MSFS and then used a replay tool to play it back with AS...in which case, would that actually work accurately? Also his description on the video is unnecessary. Seems like another troll rather than anything "scientific"

    • Like 1
    • Upvote 1

  3. 5 minutes ago, vortac said:

    I've purchased and did my first flight with ASFS. It's a good product overall, I would say.

    I notice very sudden change on the clouds durıng enroute. I did not change any default settings on ASFS. So, transition was 50 with 30 mins of download interval. When I was enroute, all clouds around were disappeared. Appx. 5 mins later new clouds started to inject slowly. Within this 5 mins time frame, everywhere was CAVOK. There was no change/affect on wind and temperature. They were both smooth and stable.

    Then I've reduced transition setting to 30. After this reduction, clouds were gone suddenly and re-appeared as before. But all clouds were OVC even the cloud radar shows somethıng BKN or SCT.

    I believe cloud transition or injection needs to be tuned as not disappeared and appeared suddenly. Or does anyone has any settings suggestion to make cloud injections more smooth?

    Thank you.

     

    Yes I'm seeing something similar

    • Like 1

  4. 3 hours ago, Damian Clark said:

    Thanks everyone for your support, feedback, encouragement and constructive criticism.  From my side, I've found that the vast majority of those who've actually tried ASFS are very favorable and positive (with some exceptions of course), while the vast majority of negative feedback is seemingly from those who haven't and won't, and it just looks like they are trying to influence others to stay away.  I'm personally focused on the feedback from those who've actually tried it and actually want further ASFS development, and there's a ton of great feedback there.  There's definitely some issues and adjustments we need to take care of, and we're working hard on that.  We're also working on lots of new features.  We have a big list of items we were hoping we'd get a chance to work on, and thanks to you, we've been given that chance.  It's clear that AS has successfully provided many with the features and solutions they've been looking for, and I wanted to thank everyone who's given it a try and given us an opportunity, once again, to continue further development.  Without your support, we simply could not continue.  Thank you so much for giving me and the HiFi team the opportunity to keep doing what we love.

    Remember that you can give us direct feedback, suggestions and bug reports at our forums (http://forums.hifisimtech.com) and our support helpdesk (http://hifisimtech.zendesk.com).  Thanks all!

    I did watch a couple of the streams and I thought the criticism was grossly unfair and it became mob mentality to attack the product that they didn't really know how to work and didn't give it a fair crack. It did leave a bit of a sour taste as I do like some those streamers. I have been flying with Active Sky since its release and I have to say its been great. Nicer variety of clouds, excellent turbulence effects, I like the public PIREP feature which I feel not many people know about. I'm really looking forward to further updates and can't wait to see what you have up your sleeve.

    I'm still tweaking the transition and update time to get it a bit  smoother as I sometimes see abrupt changes rather than smooth transitions so not sure if its a config thing or it needs to be tuned a bit. (I have update 15 mins/transition 50). Also I find that rain isn't always depicted even though its in the metar

    I think maybe a tutorial video to go through the configuration settings and features and demonstrate their effects might be useful. Also could we have an option to turn off the metar update reports in-sim please


  5. 2 minutes ago, Fiorentoni said:

    Turbulence effects are GREAT. Much better than RealTurb. The aircraft is slightly shaking on cruise, like a boat, very smooth and credible. Have not ever seen this kind of turbulence in MSFS (with or without RealTurb). AS is worth it alone for those effects, no matter if you want the actual weather depiction or not.

    This is something I have noted as well. All through the flight phases the turbulence effects are very well implemented

    • Like 3

  6. 15 minutes ago, Damian Clark said:

    Thank you for your support!

    Lots in the pipeline!  Firstly we have some post-release bugs found, working on that to post an update very, very soon.  From there, it's based on feedback!  What do you want to see changed or added?

    I think the product has great potential. I've used your products in FSX and XP11 so pleased to see it in MSFS. I was sat at an airport watching clouds rolling by and could see a large band of cloud moving towards me that was fun to watch.

    Is there a place to report bugs and issues. Couple things I have noticed is that rain/showers have been reported in the metar but there was no rain depicted. (EGCC today around 1800z.) I then went hunting for thunderstorms, ended up at KGLH and again no rain or thunderstorms...

    Also repeating cloud textures when at altitude giving a sort of grid style effect, would be nice if that can be improved

    Going forward i think an integrated weather radar we can use in 3rd part planes when using Active Sky Live weather would certainly put the cat amongst the pigeons. Whilst MSFS has advantages, it also has its drawbacks and this could certainly be a game changer.

    • Like 1

  7. Ah that's good news. There is probably a conflict in scenery packages somewhere

    You can move all your marketplace stuff out of the main fs folder (Your Drive Install:\Microsoft Flight Simulator 2020\Official\OneStore) and use addon linker with those as well.


  8. Are you sure you're using Addon Linker correctly. The crash report still has a lot of extra packages in use? Or are these from the market place?

     

    Also can see you are using the FSLTL injector, try doing these two steps to see if that helps(From the FSLTL website)

    • FSUIPC7: Fix as follows

      • Go into fsuipc folder

      • Find FSUIPC7.ini

      • Add "ProvideAIdata=No" without the quotations

    • FSLTL Injector location: Some users may experience CTDs if your FSLTL Injector and Base models are both in your community folder, fix...
      • Move the injector folder outside of MSFS Community.

  9. 46 minutes ago, Reset XPDR said:

    I have now matured the LOD Step Max functionality to a point where I am happy to put it out as a release version 0.3.5, which you can download here.

    Changes in my version 0.3.5 made since Fragtality's 0.3.2 release are summarised as follows:

    • LOD Step Max, when checked, will allow you to set a maximum change per second for LOD increases and decreases that can be set individually. Low values will minimise LOD changes that the MSFS rendering engine processes, and hence should improve smoothness transitioning between LOD levels. There is also an automated lead predictor for LOD changes based on your average climb/descent rate and LOD Step Max values whereby it will commence changing LOD as early as required to achieve the desired LOD very close to the next AGL threshold. This effectively removes the time delay in achieving new LOD values when low LOD Step Max values are used. When unchecked, LOD changes will change as abruptly as the LOD steps you make between LOD table settings, per original 0.3.2 functionality.
    • Cruise LOD Updates, when checked, will continue to update LODs in cruise but only if your AGL changes enough to put you at a new LOD table value and even then only if you cross it by a +- 5% null zone. This generally only activates when cruising at MSA over varying terrain and mostly lays dormant otherwise. Again, unchecked you will get original 0.3.2 functionality.
    • PC and VR LODs are changed at the same time, meaning it is not necessary to select whether a profile is PC or VR as LODs will change whether you are in PC or VR mode. As a result, the VR checkbox has been removed and an additional 3 profiles have been added, totaling 6, to give you more choice for the type of flying you do.
    • There are also a few fixes to fix minor issues I came across while digging through the code and testing and some small UI changes to accommodate the changed and removed features. 

    Screenshots of 0.3.5's UI, firstly with LOD Step Max disabled (default):

    spacer.png

    And with it enabled:

    spacer.png

    I hope you find the enhancements I have made useful. If not, with the exception of the setting of both PC and VR LODs together, they can all be turned off and are off by default anyway, so at the very least you'll get the bug fixes.

    Thank you so much for your efforts, its very much appreciated. 

    • Like 2

  10. Hi Mark,

    Untick all the airports/sceneries you're not flying to and you should see the amount of link's in the community folder decrease. Just test with departure and arrival airport first. Then slowly add more stuff back. Its a right pain and I've spent the last week trying to find out why my sim kept crashing.

    That's good there are no conflicts, one more thing to rule out

    The only other good push back module is GSX but it is paid. Adds lots of other stuff too like VDGS, refuelling, boarding passengers, cargo etc, Well worth the money but maybe try getting a stable system first before purchasing.

    Another thing to try is clearing your caches and the rolling cache in MSFS. Rolling cache can be deleted in MSFS and the other caches like shader cache I use this tool.

    FPS 4 MSFS - Simple FPS tweak tool for Microsoft Flight Simulator | MSFS

     


  11. Looking at your log you still have all your sceneries in the community folder. The idea behind behind Addon-Linker is that you move all your sceneries (and aircraft) out of the MSFS Community folder into a separate folder and/or drive and then in Addon-Linker only select the sceneries you are using for that session. Addon linker will create shortcut links in your community folder to those sceneries only and it keeps your community folder streamlined 

    Msfs2020*Addon linker guide for beginners*This is the BEST app to manage your addons Hands Down! (youtube.com)

    - I would suggest only selecting your departure and arrival airports

    - I also wouldn't use toolbar pushback, this has been known to cause crashes in the past.

    - Another thing to check is that the modellib.bgl file is unique with every scenery you use. If MSFS comes across two different instances of modellib.bgl it has a fit. There's a tool in Addon Linker in Tools > Modelilbs changer that will automatically rename the modellib file so they are all unique.


  12. I'm using AXIS_SPOILERS_SET that goes from -16384 to 16834.

    Can't see just a SPOILERS_SET unless the above is what you are referring too

    But currently at max extension, in dev mode it shows 0.99997 and fully retracted its 3.0518e-5. If i use the mouse or configure in MSFS it goes to 1 or 0 respectively


  13. Hello,

     

    I have a little issue with the spoiler axis in the inibuilds v2 Neo in SU14. I've assigned the spoiler to an axis on my HC Bravo, the axis works no problem, however when set in AAO, I have found that it doesn't quite set the axis to zero when in the fully up (retracted position) position, the value for the spoiler actually reads as 3e-3, so not quite 0 and so the aircraft interprets this as the spoiler still be extended, as its not a hard 0.

    I've tried setting the axis within MSFS and it works OK there, when i fully retract the spoiler handle there is no message on the ECAM and the output reads 0.

    Just wondering if anyone knows any tricks to get the handle to actually read zero when in the up position. I had a little play with centre and the margins but no joy so far.

     

    Thanks

    Dan


  14. 7 hours ago, Lorby_SI said:

    No. But the different values have different meanings for the hardware

    0 = off
    1 = on
    2 = blinking

    I can't look at the Behringer spec at the moment, but I think that those are it for the buttons. There are more options for the rotary encoder LEDs.

    Not sure why you would send the "3" in your example - this IMHO points to a general misunderstanding of how those scripts actually work. Can you describe in your own words why you would send the "3" in your els{ branch?

    This would be the correct script: "When the LVar is 0 then turn the LED off (send 0 to the Behringer device for this button). In all other cases (els{) turn the LED on (=send 1 to the button)"

    
    (L:CM1_audio_mic_adv1,·number)·0·==·if{·0·(>MIDI:4:NoteOn:1:2)·}·els{·1·(>MIDI:4:NoteOn:1:2)·}

    Probably because I am a dumbass...😞

    The script above from Daz worked. I was trying to write the script so when the Lvar is a 3 (as that is the "on" value), the light illuminates. i just wasn't sure in what part of the script that needed to be placed. I get it now. Thanks


  15. 13 hours ago, Dazzlercee23 said:

    Hi,

    Try:

    
    (L:CM1_audio_mic_adv1,·number)·3·==·if{·1·(>MIDI:4:NoteOn:1:2)}·els{·0·(>MIDI:4:NoteOn:1:2)}

    You send a 1 or a 0 to the LED based on the LVAR value. So if the LVAR = 3 then a 1 is sent to the LED, any other value and a 0 is sent.

    You can also control the LEDs on a per layer basis using channel 11 instead of 1:

    LAYER A
    Encoders 0 - 7
    Button top: 8 - 15
    Buttons bottom: 16 - 23

    LAYER B
    Encoder 
    Buttons top: 32  - 39
    Buttons bottom: 40 - 47

    The encoders cannot be controlled on a per layer basis, they are just 0 - 7 no matter which layer is selected.

    Regards,

    Daz

    Thank you, that worked! I get now how these work!


  16. Good evening,

    When trying to configure the LED's to illuminate on the XTouch Mini when a button is activated, can the script only contain a 1 or 0 for the on/off value? I have an Lvar that when active gives an on value of 3 and 0 when off. My script is as follows which unfortunately doesn't illuminate the button:

    (L:CM1_audio_mic_adv1,·number)·0·==·if{·0·(>MIDI:4:NoteOn:1:2)·}·els{·3·(>MIDI:4:NoteOn:1:2)·}

    Thanks

×
×
  • Create New...