Thank you for your wonderful work here! I have made a release posting announcement over on our Steam page to show our appreciation of what you have achieved here; a payware quality helicopter in our opinion!
Posts by drhotwing1 (IPACS)
-
-
We haven't changed anything in a long time regarding distance loading but it was adjusted to improve performance back then.
Can you provide us with more information at to what you are seeing, and where its evident?
-
Please email us at mail@ipacs.de
We want to see what's causing the crashing with AMD cards. We will have you work internally with support to try to resolve this.
-
This post should be made to him in a PM and not on the forum.
-
Yes, but don't select it in this test.
-
We are not far enough along to mention anything on our to-do list. Please be patient and once we have something more to offer we will post in our development blog.
-
OK, can you both test again but please remove ALL user-scenery before flying. Then only fly with default scenery and aircraft again. If/when it crashes, immediately post your TM log here
-
Thank you for the updates. Let us research this a bit to see where the problem is.
-
We all work 7 days a week
-
Just hold off for now until we look into the problem. But naturally the better the GPU the better the experience. We are much more GPU bound than CPU and currently the best you can get is the 2080Ti. But please remember that we built the graphics engine so that even slower GPU's have good performance.
-
Once we reach 80% on a feature we will have enough information to let everyone know about that feature. What we are working on just isn't far enough into development to mention it yet.
-
We have stated a response to this many times before. It's not that we don't want to brag about what we are working on, the fact is that we change our plans a lot internally if we research and test a feature and it fails or doesn't work out how we would like it to. It would be unprofessional of us to publish a roadmap of features that everyone wants then later tell you that we had to change plans.
As you all know because we also state this a lot, we are a very small team so it places a lot of pressure on us to stick to a roadmap that may not work out in the end.
I can however promise you this, we have plans to release some very nice (and needed) features down the road a bit, and we will absolutely provide you with updates on progress once we are far enough in development to show you. We really want to show you what we are working on, just have some trust in us.
-
No problem. Give us some time to see what's going on here and we will get back to you.
Thank you for testing this for us.
-
Thank you
We will look into this
-
OK, thank you. This is helpful.
Go ahead and test more as it will help us with diagnosing the problem.
-
Jeff,
I'll do this this evening when I am back home. FYI, I'm not in VR, purely on a monitor in case that has any bearing.
No bearing in this.
-
It appears that both of you are experiencing crashes with AMD GPU's but at different times.
Please do this for us;
1. change to Vulkan rendering and run Aerofly
2. select a flight ONLY with default scenery and aircraft (Cessna and San Francisco)
3. Let me know if you still crash
4. Now set up a flight however you see the crash, then immediately after the crash attach the TM log.
-
thank you very much for update, if there is anything I can do to help or test, please let me know
Give us a little bit and we will see what can be done here to stop the crashing
-
I just replied to a different thread on the forum regarding this same issue. We will take a look to see what's going on here with these specific cards.
-
Our Vulkan engine is still being developed and optimized, however along with that there are some known issues with some AMD GPU's. We will look into this but it's the same issue with AMD that we have had for a while now that we haven't worked out just yet.