Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 06/27/22 in all areas

  1. Some more images. Note the decals here, fully sharp text that is only 1,2 cm high. Again, work in progress, things will change.
    15 points
  2. And finally for today, the last images of the cockpit, all work in progress! Again, work in progress, things will change.
    14 points
  3. Project is going well and is on schedule (famous last words). Here are some new images of the EFB (all work in progress!!) The background can be changed to any bitmap on your system. Again, work in progress, things will change.
    11 points
  4. I cant wait for this, it looks fantastic! My only worry is not getting time to fly. Since becoming a father my time is limited. I haven't even flown the Fenix yet! And as fantastic as these developers are, i don't think there much you can do for that! Last summer what i was doing was getting up a hour earlier while working from home, Taking off just before 8 and landing either at lunch or after 5. I may have to go back to this!
    5 points
  5. So it seems like the micro stutters came from this scenery in flightsim.to https://flightsim.to/file/10890/enkb-kristiansund-kvernberget Reported to developer.
    5 points
  6. As with all our internal products we believe that making our products available on all platforms is commercially absolutely vital. So this will be available in our stores (and our affiliated stores) and on Marketplace and will work on PC, Xbox and Cloud. That also affects the price, high prices simply do not work well on the Marketplace and DLC on Xbox at high prices simply will never sell. So our prices will be set so it will sell on these markets. Now the price is not set, but I would think something like 32 euro (plus vat when applicable) will be not far off. We'll see. =-=-=-=-=-=-=- Oh and before people start to worry about things being 'dumbed down' for Xbox. Just look at the images. The fact we want our products to perform good on PC, Xbox and Cloud only means we have to be very professional in our work and have to use every possible option the simulator offers us. MSFS has a very modern graphics engine, very much in line with other game engines. To me it is stunning that so many developers are still stuck at P3D standards and not invest time in learning what the sim has to offer. I know I keep hammering on it, but NONE of the images shared contains a texture larger then 2K. High definition textures are simply outdated when you can use decals. Adding a fully 3D interior to the external view (so you can see through the windows) is a massive waste of memory and framerates if you can use the windowbox methode the sim offers. Using these things make the model look better and will make sure they work fine on Xbox and Cloud.
    5 points
  7. What part of "Again, work in progress, things will change" did you miss? 🤔
    4 points
  8. There will be a hotfix coming to address this issue. First of all, I understand how frustrating this issue can be and we are looking to get this hotfix out as promptly as possible. Probably will not get it out this week yet unfortunately since there are so many moving parts when it comes to releasing even a quick hotfix that have to be taken into account. But we'll try to get it out latest by the end of next week.
    4 points
  9. I applaud your ability to self-diagnose this. It is almost always not the plane you are flying, regardless of plane. Good job! Be sure to let us know the addon. Be aware, it could be a liver or scenery too, even if it is not being used. When I do this, I start with only the aircraft I was in when I noticed, then add in utilities like pushbacks etc., then that leave liveries and sceneries. At that point I only add back in the livery I will use for a flight plus the two airports if they are addons. Rinse and repeat until the culprit is found. If you don't have it, MSFS Addons Linker makes this process very easy. It's on flightsim.to
    4 points
  10. Here is a great example of what we intend to add to the sim, not just ships but ships doing work: And one more vessel:
    4 points
  11. A bit offtopic, but would it perhaps be an option to take a bit of time every now and then, to go through some of the topics of the past that may have been checked/worked on, and giving some quick bits of feedback like this? As part of taking steps towards better communication about development. There are quite a few issues documented very clearly* that have never received any feedback other than that it is on the list somewhere (if even that at all). *(I do not count my own thread linked above among those, but for actual examples take a look at some issues posted by @KuntaKinte that rarely got any feedback despite being described in detail and with the correct behavior added for good measure)
    4 points
  12. Thanks for reporting. Something with default ATC indeed went wrong with the update that went unnoticed during testing. We have been able to recreate this issue and are looking further into it.
    4 points
  13. 4 points
  14. Bro they never made an A330 for FSX
    3 points
  15. No the First Officer's Audio Control Panel will remain inactivated for now. Otherwise it could cause potential conflicts between which channels are actually open. Take for example a situation where VHF2 Receive is OFF on captain's side and ON on FO's side. Or wise versa, ON of CAPT side and OFF on FO's side. Which side should it follow to make the actual receive variable itself ON or OFF in sim? We could make OR logic gate for it which would mean that the channel is open if it's open on either side. But that would then mean that you might need to fiddle with both panels when you want to make any changes (if channel is open on either one, it's open, so you need to close it on both panels for example). So in the end, there is only one ACP that controls a single audio device audio, just like in real life. Since most people fly from the Captain's seat we chose for the CAPT side as the functionable one. I understand that it's not optimal for the pilot's who like to fly from the FO's seat that they have to use ACP that the FO would never touch in real life. But after giving this some thought within the development team, we thought this is the simplest solution for now to avoid any confusion between which channels are actually open and when when trying to control single audio device through both panels. I want to clarify also that the audio control panel is different thing from the radio itself. Audio Control Panel only controls the channels that are open and closed for transmitting or receiving and their volumes. The COM2 radio on the FO side remains fully operable. It's just the Audio Control Panel on the FO's side that remains inactive because of the possible conflicts mentioned above. We might look into the possibility of selecting a role through the EFB as CAPT or FO, and that then determines which ACP is the functionable one. But this requires more time to investigate and implement, and we have not made a full decision on this yet.
    3 points
  16. yes,we will fix this issue in next version,caused pmdg has changed sdk format.btw pmdg not published the SDK for the msfs 737, currently connecting to the 737 is doing so using an SDK for P3D, the SDK must necessarily change in order to grasp greater functionality for end users.no worry we'll repair it as quickly as possible.
    3 points
  17. Hopefully that statement means both Captain's and FO's radio panels will be fully operative. Will they?
    3 points
  18. You forgot to bring us... ANOTHER SHRUBBERY.
    3 points
  19. Yes, we need a list! This way we, the customers, can take heed of the list and where issues are on the list and complain much if we are unhappy with the list. We shall meet every Thursday before the evening meal and talk of the list and move the items up and downward on the list. After discussion we shall complain again of the list and the changes made. Once we grow tired of the list, we will add to the list a demand for another list with a timeline. Aerosoft, stop wasting time working on the list and make a list of what you should have been working on for us to complain about! The customers demand it!
    3 points
  20. Ok, I asume animals are fully modelled, so that we can see and hear them during a low fly-by
    2 points
  21. VDGS support is available at the following airports and their versions: Brussels (EBBR) was added at initial release Trondheim (ENVA) was added at version 1.1.0.0 Cologne (EDDK) was added at 1.0.7.0 and adjusted at 1.0.8.0 Paderborn (EDLP) was added at version 1.0.8.0 Zagreb (LDZA) was added at version 2.0.0.0 Ben Gurion (LLBG) was added at version 1.1.0.0 and adjusted at version 1.1.1.0 sim-wings La Palma (GCLA) was added at version 1.1.0.0 sim-wings Gran Canaria (GCLP) was added at version 1.0.3.0 sim-wings Tenerife South(GCTS) was added at version 1.2.0.0 Information derived from the AS Store site and the list of active airports in [drive]\[MFS location]\Community\aerosoft-vdgs-driver\airports Edit: Added airports on July 3, 2022.
    2 points
  22. Steps I did to do this were as follows: Flight from KBFL to KDFW cold and dark on the ramp, after getting the APU started, started filling out the flight plan in the FMS. after that is all done, went to clear out a disco in the legs page, freezes at that, everytime I try to clear the disco just tried again, when clearing the disco's or at least trying to, it freezes up the game.
    2 points
  23. Hello together, at the moment I'm working on the text decals for the landing gear. Unfortunately, I still have a few unclear areas and it would be great if one of you guys could help. The most important thing about the references is that the text is legible. Everything else is secondary at the moment. Any help is very welcome These are the areas I need your help: ... the main gear ... the nose gear
    2 points
  24. Inspired by this month's screen comp "Final Approaches from the "flight-deck", I had a search for some shots.
    2 points
  25. There's no blame implied, it absolutely shouldn't crash - I'm just trying to establish what lead up to it so I can avoid doing it myself, if nothing else!
    2 points
  26. Lol, to be clear, two sides. We have not yet decided if they will be independent, depends on the load they cause and how that would affect use on different platforms.
    2 points
  27. Thanks I look for it after my short vacation David
    2 points
  28. I don’t have fsuipc7. I have in fact cleaned the community folder and the stutters are gone. Need to put back the mods piece by piece when I got time. I found out that I had an outdated Nool VDGS mod last night. It could be that mod causing the stutters. I will find out next time I log in.
    2 points
  29. Hi Andreas, it is indeed on the roadmap to switch to the native msfs menu system with a version 2.0, due sometime next year. This should automatically make it compatible with VR.
    2 points
  30. Right, That EXEC thing seems to be key indeed. I was now able to recreate the cases (and also the ESSA-EETN case from the other thread) when loading STAR before the arrival runway and not hitting EXEC in between. Hitting EXEC between selections or selecting the arrival runway before selecting the STAR (and enroute transition) seems to work fine. It is after all very special sequence of events that have to align right to get into this state. For now the advise is to EXEC the flight plan every once in a while. This in my opinion is a good habit anyways since if you make a mistake and have to cancel the mod, you'll lose all changes and have to start over again from scratch. We'll see what we can do but opening this code again and trying to get this fixed as well could easily turn into another cycle of issues we already had to deal with when getting majority of this to work correctly. And we want to get other areas fixed as well at some point. So it's a trade-off. We'll see. Also to add on the ESSA-EETN topic quickly. That was known to us and we tried to check that working as well but when I tested this case earlier I think I only tested with loading the runway and transition first before STAR which did not give the issue of duplicate waypoints.
    2 points
  31. another broken thing that was noted, but ignored
    2 points
  32. This is accurate (and verbatim from the FCOM no less). We train to this specific configuration and scenario during our Extended Envelope Training in the CRJ. I believe Aerosoft will address this eventually. They have higher priorities with the aircraft at the moment and that's ok. The majority of end users aren't testing the flight model and AP at the edges of the aircraft's flight envelope. I primarily brought this forward because I felt it might hold some additional information regarding other autopilot issues users have been experiencing lately.
    2 points
  33. Just bought the CRJ 550 and 700 and had been experiencing the following issues with ATC. Not hearing my own pilot's voice when communicating with ATC ATIS looping, repeating airport name or only first few words of ATIS Broken ATC communication during flight I saw Olaf B's posts explaining how to set the radio panel, and tried that. On the left Radio Panel I pushed in VHF 1, VHF 2 and INT SVC. I then set the selector dial to INT SVC. This fixed the issue with the ATIS looping, but I was still not hearing my own voice. I tried setting the RIGHT SIDE radio panel the same as the the LEFT side so that both panels have VHF 1, VHF 2 and INT SVC pushed in and the dial is on INT SVC . This has fixed the issue of not being able to hear my own replies or acknowledge ATC. I'm still not able to have my copilot communicate with ATC automatically, but this was a big improvement over not being able to hear/use the ATC properly. Hope this helps anyone who may be having similar issues.
    1 point
  34. Hi all, It is summer time and Chania airport is becoming one of Greece's busy airports, serving more than 50 flights per day. The destination also becomes more frequent for simmers, so it is time for the first update of the airport. Being a release using the first SDK available, LGSAv1.0.0 used the default lighting system of MSFS. At this updated version you will find a new package of custom-made taxi lights, runway lights, rail lights, and approach lights. The brightness of those lights is set to a more realistic value than the default ones along with light effects visible from a close distance. The aiport's main apron has been redesigned and reconstructed back in 2016. Six years later the concrete and the lines have a different view which is represented at the update. Moreover, the lines at the left and right side of the apron's intersections which were not there at the first release (and at the real airport) have been added. The NSA area has also been expanded to serve more military aircraft Almost all the vehicles at the apron and the parking area have been replaced with new (better) ones. Same applies for the taxi signs, the FOD bins and the fire extinguishers . Finally, all bugs reported by the users have been corrected. Here is the full update list: - improved ground textures at apron area. - improved and more detailed taxisigns. - custom runway, rail, taxiway and approach lights. - replacement of all apron and parking vehicles with new ones. - addition of new taxi lines at the apron area. - addition of the new apron taxilines and dynamic lighting at NSA area. Modification of the airport name signs at the terminal (blue instead of white with FRAPORT logo addition). - correction of few floating objects - correction of the position of military shelters - correction of the ATC instructions to include taxiway names and showing the correct taxi ribbon. The update will be shortly available for download. Regards, -=Manwlo=-
    1 point
  35. CRJ has alot of bug and issue.... if you go DIR to a waypoit the T/D will be gone and u have to manualy descent... ISSUE 2: Bad FPS in cockpit and very dark dome light
    1 point
  36. If so, that is a very low priority for us, we really focus on the cockpit.
    1 point
  37. My most anticipated aircraft since the release of MSFS. Cannot wait. Thanks for sharing the images!
    1 point
  38. From Beer & Bratwurst to Gyros & Ouzo. In other words, from Munich, Germany to Athens, Greece. [CLICK] to see the larger picture... Hopefully you enjoyed these pictures, commentary is greatly appreciated...Darryl
    1 point
  39. Amazing, the best looking VC in MSFS in my opinion…
    1 point
  40. fsuipc7 Should also cause this stuttering with autosave. I would still try to turn this off
    1 point
  41. I would be glad to invite you to the beta team if you think you can avoid painful issues like this!
    1 point
  42. This is nothing new for this update. The table with the speed calculations (original manufacturer data) becomes quite sketchy at altitudes at or above 6000ft, especially with high take off weights (Denver and Aspen are prime examples). Some airlines apparently have more complete tables but these include additional temperature limits ("38°/132") where the manufacturer tables just have a blank field. If we can get a hold of those, we will add them to a future update.
    1 point
  43. Once in a while? You are here every other day with posts...June.. 2nd, 3rd, 5th, 7th, 8th, 9th and 13th.... and all you do is complain to the manager..... for what the price of a couple decent pizzas?
    1 point
  44. Yeah, now we have to wait indefinite time for what was promised for launch
    1 point
  45. The marketing for this plane is so weird. It’s a casual experience but here’s a 100 page manual! Fuel pumps are too confusing but here’s a patch that totally changes the flight dynamics!
    1 point
  46. To be fair, the twotter is $35, not $25. At this price point you're sitting $5 less than the Milviz C310 that models errors at a very high level of detail. There are plenty of devs who model simple things like having to turn on fuel flow either by pump or petcock on much less expensive planes. In fact, I own one that I paid $10 for and I still have to turn on the fuel before the plane will start up. It's part of the checklist. Trying to push this off as a stupid error is just deflecting and comes off as disingenuous on your part. At the end of the day though, it's your plane to model however you want. In summary your position is that you're going to put forth nice looking models that are very simplistic in terms of care and feeding and should be easy to fly for the casual simmer who doesn't care about fidelity beyond controlling things like power and attitude. Easy enough.
    1 point
×
×
  • Create New...