@POTETOZ "Is there a date for the release of these fixes yet?"
We are planning on doing a release candidate final build early next week for all platforms, which will go live as soon as they're approved by their respective stores (ex: iOS App Store).
I really appreciate all the feedback/discussion going on here
I've read all the replies, and even if I don't reply soon after you post, I very well may come back later on with questions to help me better understand the situation.
"So this isn't actually a bug complain but I just have a question why was the beta 1.12.120 forum post on the front page like when Andrew makes a forum post?"
@MrShenanigansSP I'm not exactly sure what you're referring to, but we have two main types of posts that we do..."Blog Posts", and regular forum posts. Blog posts have an image associated with them, and will be discoverable from the blog dropdown.
I made these posts for v1.12.120/121 to be regular forum posts.
@Hedero Can you link to a craft which exhibits the issue, please? I'm sure its easy to replicate, but it's often simultaneously easy to mess up trying to replicate bugs as well. It would be a big help.
"WAIT You need a computer to play spvr with oculus quest?! Pls say no"
No. If you own a Quest, you can either play SimplePlanes VR on Steam (and therefore on a computer), or by buying the Oculus Quest version on Oculus Quest App Lab (you can wishlist it now to be notified when it releases).
If you buy it on Oculus Quest's App Lab, then it runs entirely on your Quest, and you won't need a computer. It's just like playing any other Quest game.
SimplePlanes VR is coming to Steam and Oculus Quest this year.
If you want to know when it’s released, you can wishlist SPVR on Steam here. If you plan on buying on Quest, a Steam wishlist is still a good way to be notified when it is available.
@switdog08 No, updates don't cost additional money. Are you sure that you're logged in? If so, you should probably email Humble support and figure out what is going on.
Do you maybe have a controller/joystick plugged in which is causing it? Try unplugging any that you have and see if that helps...if so they may need remapped.
@Ambarveis Good catch. It is primarily related to drag being capped, when it should be allowed to rise. It isn't as simple "don't cap it", though and would require some non-trivial time to fix. It would also impact all helicopters, not just ones like this. Unfortunately, I doubt it will be fixed with 1.8.
@Rsouissi Normally you just lean w/cyclic using your regular roll controls...you could also slightly tilt the main blades to have the correct amount of sideways thrust built into the system.
Click on the main blades, and adjust diamer to max.
Click on the tail blades, and adjust diameter to min.
Drag out a Blade T1000 (not connected to anything) and adjust to min
Select main helicopter blades, and adjust to min
Select T1000 and adjust to max.
Drag out a Blade T2000 (connect somewhere on heli) and adjust to max
Select main heli blades, adjust to
Select T2000 and adjust to min.
After doing all this, I'm still not seeing the issue. I'm assuming there is a problem, I'm just doing something differently and therefore it isn't showing up. If the problem does occur for you, which step? If you don't get any problems following these steps, could you give me similar steps to reproduce the error starting from an uploaded design?
@ThePrototype Can you verify which version you are using? You can find it from the first menu screen (with SimplePlanes log) under the "About" section. And, are you playing on iOS?
@CyberDays Are you on Google Play or Amazon? Amazon is still working through the process and has not been sent to devices yet...Google Play should be sending out to devices but might still take some time.
@ThePrototype I have not been able to reproduce this. Does it happen every time...does it happen even with a new prop engine that you pull out? Can you upload a design where it consistently occurs?
@PilotOfTheBoss Have you by any chance used both the Steam and Mac App store version? They store the files in different locations and could possibly get things messed up.
@WNP78 That's cool. Yeah in another life I was Lipoly :) Although I'd used gyros for r/c helis and quads, I wasn't familiar with PIDs until recently. I'd like to take a stab at using 'em to improve the AI, but some sort of auto-tuning might be difficult. It's been a while since I looked, but I think I'm essentially using a PD controller now, but since I didn't take a general approach, that code is comparatively messy, and obviously struggles with a lot of designs.
@PlanesAndThings2 Linkage speed is the time it takes for the tail rotor's linkages to physically move to their extents. If it is too slow you will have tail oscillations as it overshoots in either direction. Adjusting it just gives the tail a slightly different feel to allow you to dial in whatever tail response you're going for.
@JamesBoA Do you have AI Air Traffic turned on? A bug has been found and fixed, it is possible the game is trying to spawn aircraft with a T2000 engine and it is failing, causing fuselages to look like that.
@TMach5 & @Rub3n213 I've fixed the issue...thanks a lot! We'll get a new version out tomorrow most likely. Until then, avoid designs with a TBlade T2000 to not get this error.
@zAerospace That should be fixed now.
Just so you're aware; the experimental branch currently has undo support generally disabled to investigate lag-spikes in the designer.
@Nerfaddict It is in fact a bug, thanks for reporting it. Sorry about that, it should be fixed in the release next week.
@POTETOZ "Is there a date for the release of these fixes yet?"
We are planning on doing a release candidate final build early next week for all platforms, which will go live as soon as they're approved by their respective stores (ex: iOS App Store).
@MrShenanigansSP I'm not sure, I figured it was on the front page for a while, at least.
I really appreciate all the feedback/discussion going on here
I've read all the replies, and even if I don't reply soon after you post, I very well may come back later on with questions to help me better understand the situation.
Thanks for everyone's help :)
@xiaofootball That's a great point, I wonder if that's what Suica is referring to.
"So this isn't actually a bug complain but I just have a question why was the beta 1.12.120 forum post on the front page like when Andrew makes a forum post?"
@MrShenanigansSP I'm not exactly sure what you're referring to, but we have two main types of posts that we do..."Blog Posts", and regular forum posts. Blog posts have an image associated with them, and will be discoverable from the blog dropdown.
I made these posts for v1.12.120/121 to be regular forum posts.
@Suica I'm not totally following that description.
Which glass parts, and which wings are you referring to?
@POTETOZ That certainly demonstrates the bug well, thank you.
@Hedero Can you link to a craft which exhibits the issue, please? I'm sure its easy to replicate, but it's often simultaneously easy to mess up trying to replicate bugs as well. It would be a big help.
Edit
https://www.simpleplanes.com/a/JEhH78
https://www.simpleplanes.com/a/uSftx2
@Default4 We're targeting early next week, but it also depends on how quickly the update gets approved by Apple.
Thanks for all the feedback, everyone. We're still working on getting some bugs tracked down to prepare for the final release.
Next release timing: We're hoping to get new beta builds out tomorrow after some issues are addressed, but it's possible it will take a bit longer.
For all remaining bug reports, please use this post so we can track them a bit easier (I should've done that to begin with) .
Thanks! :)
@Merlin420069 There is no mod support on the Quest. You are trying to get the multiplayer mod working on the Quest, is that correct?
@Deethebeast420: "It says item is no longer available for quest store."
When is it saying that? Immediately after clicking the link?
@Gudboyyy, @klm747klm747
"WAIT You need a computer to play spvr with oculus quest?! Pls say no"
No. If you own a Quest, you can either play SimplePlanes VR on Steam (and therefore on a computer), or by buying the Oculus Quest version on Oculus Quest App Lab (you can wishlist it now to be notified when it releases).
If you buy it on Oculus Quest's App Lab, then it runs entirely on your Quest, and you won't need a computer. It's just like playing any other Quest game.
SimplePlanes VR is coming to Steam and Oculus Quest this year.
If you want to know when it’s released, you can wishlist SPVR on Steam here. If you plan on buying on Quest, a Steam wishlist is still a good way to be notified when it is available.
@Kyokutyo Try restarting Steam. It can sometimes take Steam a while to update otherwise.
Anyone interested should wishlist/follow on Steam so you get notified when it is released and when we post updates!
@hobbitfrog Thanks, I was able to reproduce the issue w/that craft, and fixed the bug.
Does this craft exhibit the cannon bug from your report, or do I need to make changes? I did not have any problems firing the cannon w/this craft.
Looks great. She's pretty quick of the line :)
@switdog08 No, updates don't cost additional money. Are you sure that you're logged in? If so, you should probably email Humble support and figure out what is going on.
@switdog08 HumbleStore should have the latest version...did you re-download it?
Do you maybe have a controller/joystick plugged in which is causing it? Try unplugging any that you have and see if that helps...if so they may need remapped.
@Ambarveis Good catch. It is primarily related to drag being capped, when it should be allowed to rise. It isn't as simple "don't cap it", though and would require some non-trivial time to fix. It would also impact all helicopters, not just ones like this. Unfortunately, I doubt it will be fixed with 1.8.
@Rsouissi Normally you just lean w/cyclic using your regular roll controls...you could also slightly tilt the main blades to have the correct amount of sideways thrust built into the system.
@sheepsblood That's good to hear!
Can you look at this?
@ThePrototype I've not yet been able to reproduce this. Can you do me a favor and go through these steps and see if it happens?
After doing all this, I'm still not seeing the issue. I'm assuming there is a problem, I'm just doing something differently and therefore it isn't showing up. If the problem does occur for you, which step? If you don't get any problems following these steps, could you give me similar steps to reproduce the error starting from an uploaded design?
I really appreciate the help, thanks!
@ThomasRoderick What device do you have, which is having issues w/the keyboard?
@ThePrototype Can you verify which version you are using? You can find it from the first menu screen (with SimplePlanes log) under the "About" section. And, are you playing on iOS?
@CyberDays Are you on Google Play or Amazon? Amazon is still working through the process and has not been sent to devices yet...Google Play should be sending out to devices but might still take some time.
@ThePrototype I have not been able to reproduce this. Does it happen every time...does it happen even with a new prop engine that you pull out? Can you upload a design where it consistently occurs?
@ThePrototype I will look into it...it is certainly not intentional for them to work that way.
Where did you download it from?
@PilotOfTheBoss Have you by any chance used both the Steam and Mac App store version? They store the files in different locations and could possibly get things messed up.
@Jacobdaniel It's officially out, but a patch is already in the works. No major features will be in the patch, though.
@dootdootbananabus Glad it's working...which mod was causing it?
@WNP78 That's cool. Yeah in another life I was Lipoly :) Although I'd used gyros for r/c helis and quads, I wasn't familiar with PIDs until recently. I'd like to take a stab at using 'em to improve the AI, but some sort of auto-tuning might be difficult. It's been a while since I looked, but I think I'm essentially using a PD controller now, but since I didn't take a general approach, that code is comparatively messy, and obviously struggles with a lot of designs.
@dootdootbananabus Are running the newest beta? What device are you using?
@TNTlord1 The new beta should be out for Android now. @AerialFighterSnakes Hopefully soon!
@Freerider2142 Thanks, glad 'ya like them :)
@PlanesAndThings2 Linkage speed is the time it takes for the tail rotor's linkages to physically move to their extents. If it is too slow you will have tail oscillations as it overshoots in either direction. Adjusting it just gives the tail a slightly different feel to allow you to dial in whatever tail response you're going for.
@Gestour Yep, there was a bug w/the T2000 engines, an update was just pushed about 30min ago w/a fix. Glad it worked for 'ya!
@DeathStalker627 Is the issue with Cleaver & Torpedo colliders new in the beta? Did you make a bug report?
@BurkeEnterprise Did you create a report about the bug you found w/magnets? What issue are you having?
@JamesBoA Do you have AI Air Traffic turned on? A bug has been found and fixed, it is possible the game is trying to spawn aircraft with a T2000 engine and it is failing, causing fuselages to look like that.
@TMach5 & @Rub3n213 I've fixed the issue...thanks a lot! We'll get a new version out tomorrow most likely. Until then, avoid designs with a TBlade T2000 to not get this error.
@TMach5 Thanks! I got the bug report and was able to reproduce it with the aircraft you uploaded.
@TMach5 Can you elaborate?
Can you upload the design which has this issue?