Yeah I'm experiencing similar symptoms too.
I think you should slow down. Segregate your project into small bits. For example:
I'm now making my Ju 288 G-2 set to release after 1.9.2 is officially released. Now my build schedule looks like this:
Today: finish the instrument panel of the cockpit remake (which has been ongoing for a week)
Tomorrow: investigate the possibility of re-arranging nose shape
2 days later: make the new airbrake exterior
weekend: make the rear seat, radio stack
whole next week: make the turret, experiment with overspeed/engine overheat mechanism (which usually should only take 2 days)
Once you finished the objective of the day, close SP and do something else.
If you still feel stress, further reduce the load per day.
Speaking of which, how exactly does the mods determine your age?
I'm not native speaker of English but I'm 28, and I don't want to be deemed a primary schooler for a grammar error I made or something similar...
" when you spawn in the water make sure that your cockpit is submerged"
This makes the system determine that your build is DESTROYED. That's why the USS Beast fleet won't attack you.
tip: When making Japanese version of German planes, add more glass panes.
This is what happened with J8M Shusui, as Japanese glassmaking technique cannot match the German's.
@SnoWFLakE0s I don't know much about structure, but yeah, maybe starting from scratch would be easier than modifying current SP into something like that.
I am modifying one of my works now, and yes, modifying is really more painful than creating from the very start.
@SnoWFLakE0s Well I won't expect that, too, but IF they can do it, they can make SimplePlanes into the first "CAD software with playability", it's going to be great. It will turn SP from a decent game into a great game that will leave its name in history.
I think all we need to do is to add everything AutoCAD has... (extrude, subtract, rotate around given axis.... etc etc etc)
If something can't be made out of CAD (computer assisted design) commands then it doesn't exist.
Friendly reminder: there's only 45 stars.
The actual USA flag has 5-4-5-4-5-4-5-4-5-4-5 stars per row vertically.
i.e. there should be 6 rows with 5 stars each, with 5 rows with 5 stars each inserted between them, that would make 50 stars.
@WNP78 Yeah it seems to be a problem of "boolean" or "float".
It doesn't break 1.9.1 LG expressions but obviously it does break 1.9.202 (the version with reversed expression).
@goboygo1 I was talking about the bending right before breaking. It's beyond recovery point and should be irreversible.
Making wings flexible in normal use is another issue, and it would have some in-game issue (collision model management, control surface distortion, etc)
What actually WTFs me, is that some people are buying BULLETS as a means of coronavirus prevention. like, what, the, F.
It almost sounds like the Americans are enjoying this, like they've been "preppers" for decades only to wait for this day to happen....
I think the biggest problem is that when you look at the map from top down view, it looks very absurd and unnatural.
Snowstone is square, Wright and Krakabloa and Maywar are round, Skypark city is fully man-made.
A more naturally-looking terrain would be better.
If we all stop talking about it, it won’t be an issue.
This sounds like ignoring a problem.
The coronavirus IS an issue whether you talk about it or not.
its just that we don't necessarily have to react THAT much.
I would say it's probably worse than quite a lot of other stuff, but yes, please keep it off here.
It's just like in my country.
Everyone says politics is important, and tries to talk politics to me everywhere.
Well yes it is, but that doesn't mean you should only talk about politics anytime, anywhere.
@goboygo1 The problem of using rotator is that it would be reversible. I.e. if I went to the verge of wingtip breaking and came back to normal speed, the wingtip would bend then "come back".
I think I'll instead angle the detacher to make it come of with a spin
@ChiChiWerx @Numbers This is just a technology demonstrator, the full release version of this Ju 288 will be made with better detail and realism.
Engine overheating (which was a real problem for Ju 288 IRL), landing gear damage (also), renewed control surface (already done)... etc.
@SnoWFLakE0s Well, yeah... I plotted these coordinates for.... assumed navigation crosspoints. Just posted it because you said you haven't verified the distances yet.
For your reference, this is what I measured: (all are nearest "whole numbers" close to the center of the field, not spawn point)
Wright Airport: Lat -5200, Long 5900
Avalanche: Lat 140880, Long 6000
Yeager: Lat 53120 Long 26215
Skypark (Oval Office) Lat -31540 Long -1050
Maywar (Faroh's garden) Lat -33630 Long 76280
This is the data I used for my GPS build.
get a 1.9.203 beta and use smooth function.
Assume you want to activate it 5 seconds after AG1 is turned on, input this on the "inputid" or "input":
sign(smooth(Activate1, 0.2))
Another issue:
number of destructible entities:
Wright I.: 4 (USS Tiny and USS Beast Fleet)
Krakabloa: about 10 (two bridges and one convoy)
Snowstone: 4 (2 missile launchers and two laser turrets)
Maywar: I don't want to count (remember that wind farm? every wind turbine is destructible. And Maywar has its own convoy)
@asteroidbook345 I know.
I'm also investigating possibilities to enhance the function of these landing gears, so the update will come with the upgrade.
Bug report: (all contents of smooth function omitted)
a smooth function piston that takes the structure of:
smooth() < 0.99 & smooth() > 0.01 (in other words, extend the piston when smooth is > 0.01 and < 0.99)
would fail to function ONLY on the first time the smooth function was triggered.
2nd time and on it worked perfectly. I changed back to the old school sign(min(smooth() - 0.01, 0.99 - smooth())) and it worked first time, every time.
Not sure if the old bug report section on the 202 version post still works for 203 so I just posted it here.
@AndrewGarrison
@WNP78
@SnoWFLakE0s The point for this change is to make sure anything that FTed during 1.9.1 using LandingGear input still works in 1.9.203.
My stuff still does (improvement, they didn't in 202), but no guarantee everyone else's stuff does unless the LG input is the same as 1.9.1.
Since we took the trouble to invent the GearDown input for the "gear down light" purpose, why not just leave LandingGear the way it was in 1.9.1? that's the only way to ensure 1.9.1 planes still works perfectly without having to re-program.
...
my planes will continue to use LandingGear input because 0=down 1=up makes more sense mechanically (because 0 means initial state, and since planes are usually spawned on the ground, the initial state is "down".)
...
Either way I made 3 versions of my Ju 288.
One for 1.9.1 landing gear input, one for .202 beta input and one with .203 beta.
This "should" cover all probable circumstances.
LandingGear now acts exactly as it did before the previous beta
Uh, does it?
pre-beta it's -1 for off and 1 for on (that's why we can continue to use pre-202 beta FTs by reversing the sigh), in this version it seems to be 0 for off and 1 for on.
in other words:
Version<>down<>up
1.9.1xx<>-1<>1
1.9.202<>1<>-1
1.9.203<>0<>1
Because of this, my "fancy landing gear" has to be entirely re-programmed, rather than simply reverse the sign.
Please confirm whether this change is permenant, I have been forced to modify LG input twice, I really hope I don't have to do it a third time...
Yeah I'm experiencing similar symptoms too.
I think you should slow down. Segregate your project into small bits. For example:
I'm now making my Ju 288 G-2 set to release after 1.9.2 is officially released. Now my build schedule looks like this:
Today: finish the instrument panel of the cockpit remake (which has been ongoing for a week)
Tomorrow: investigate the possibility of re-arranging nose shape
2 days later: make the new airbrake exterior
weekend: make the rear seat, radio stack
whole next week: make the turret, experiment with overspeed/engine overheat mechanism (which usually should only take 2 days)
Once you finished the objective of the day, close SP and do something else.
+1If you still feel stress, further reduce the load per day.
I can't believe nobody did this:
+2'T'esla.
Speaking of which, how exactly does the mods determine your age?
+4I'm not native speaker of English but I'm 28, and I don't want to be deemed a primary schooler for a grammar error I made or something similar...
" when you spawn in the water make sure that your cockpit is submerged"
This makes the system determine that your build is DESTROYED. That's why the USS Beast fleet won't attack you.
Suggestion: Make a cosmetic wing and use a jet engine facing downwards (lol)
That's probably the easiest.
tip: When making Japanese version of German planes, add more glass panes.
This is what happened with J8M Shusui, as Japanese glassmaking technique cannot match the German's.
@SnoWFLakE0s I don't know much about structure, but yeah, maybe starting from scratch would be easier than modifying current SP into something like that.
+1I am modifying one of my works now, and yes, modifying is really more painful than creating from the very start.
@SnoWFLakE0s Well I won't expect that, too, but IF they can do it, they can make SimplePlanes into the first "CAD software with playability", it's going to be great. It will turn SP from a decent game into a great game that will leave its name in history.
+2I think all we need to do is to add everything AutoCAD has... (extrude, subtract, rotate around given axis.... etc etc etc)
+3If something can't be made out of CAD (computer assisted design) commands then it doesn't exist.
- set the thickness of the tip side to be 0 (not sure how that'll look though)
- put a fuselage cone (not going to fit perfectly if you have control surface)
+1and magnet effective ranges. Right now the effective range is nil.
+8I tried to make an "automatic compensating" turret that automatically shoots along your turning arc, it wasn't very useful though.
+1Don't actually detach it, link it with a very long winch or something.
Friendly reminder: there's only 45 stars.
+4The actual USA flag has 5-4-5-4-5-4-5-4-5-4-5 stars per row vertically.
i.e. there should be 6 rows with 5 stars each, with 5 rows with 5 stars each inserted between them, that would make 50 stars.
@WNP78 Yeah it seems to be a problem of "boolean" or "float".
It doesn't break 1.9.1 LG expressions but obviously it does break 1.9.202 (the version with reversed expression).
I love that leek tail.....
@Natedog120705 Don't worry, I do know that not every American is a prepper.
@goboygo1 I was talking about the bending right before breaking. It's beyond recovery point and should be irreversible.
Making wings flexible in normal use is another issue, and it would have some in-game issue (collision model management, control surface distortion, etc)
What actually WTFs me, is that some people are buying BULLETS as a means of coronavirus prevention. like, what, the, F.
It almost sounds like the Americans are enjoying this, like they've been "preppers" for decades only to wait for this day to happen....
I think the biggest problem is that when you look at the map from top down view, it looks very absurd and unnatural.
+3Snowstone is square, Wright and Krakabloa and Maywar are round, Skypark city is fully man-made.
A more naturally-looking terrain would be better.
If we all stop talking about it, it won’t be an issue.
This sounds like ignoring a problem.
The coronavirus IS an issue whether you talk about it or not.
its just that we don't necessarily have to react THAT much.
I would say it's probably worse than quite a lot of other stuff, but yes, please keep it off here.
It's just like in my country.
Everyone says politics is important, and tries to talk politics to me everywhere.
Well yes it is, but that doesn't mean you should only talk about politics anytime, anywhere.
@goboygo1 The problem of using rotator is that it would be reversible. I.e. if I went to the verge of wingtip breaking and came back to normal speed, the wingtip would bend then "come back".
I think I'll instead angle the detacher to make it come of with a spin
@ChiChiWerx @Numbers This is just a technology demonstrator, the full release version of this Ju 288 will be made with better detail and realism.
Engine overheating (which was a real problem for Ju 288 IRL), landing gear damage (also), renewed control surface (already done)... etc.
@SnoWFLakE0s Well, yeah... I plotted these coordinates for.... assumed navigation crosspoints. Just posted it because you said you haven't verified the distances yet.
For your reference, this is what I measured: (all are nearest "whole numbers" close to the center of the field, not spawn point)
+6Wright Airport: Lat -5200, Long 5900
Avalanche: Lat 140880, Long 6000
Yeager: Lat 53120 Long 26215
Skypark (Oval Office) Lat -31540 Long -1050
Maywar (Faroh's garden) Lat -33630 Long 76280
This is the data I used for my GPS build.
@asteroidbook345 Yo, a new version is up, I tagged you.
@asteroidbook345
@starxiao Did you choose a wrong beta option or something?
@UFNNICF5TF No, it directly reads your coordinate from the game engine. The game engine does the satellite part.
@UFNNICF5TF No, it directly reads your coordinate from the game engine. The game engine does the satellite part.
@BlackBoA Didn't find it. Only found an old post stating that there were a hoax about Snowstone convoy.
get a 1.9.203 beta and use smooth function.
+1Assume you want to activate it 5 seconds after AG1 is turned on, input this on the "inputid" or "input":
sign(smooth(Activate1, 0.2))
@BlackBoA !? WUT? Where? I never noticed!
Though I think I should've included USS Tiny Two fleet in Krakabloa...
Another issue:
+2number of destructible entities:
Wright I.: 4 (USS Tiny and USS Beast Fleet)
Krakabloa: about 10 (two bridges and one convoy)
Snowstone: 4 (2 missile launchers and two laser turrets)
Maywar: I don't want to count (remember that wind farm? every wind turbine is destructible. And Maywar has its own convoy)
Get well and stay safe, brother.
Feel free to contact me for tips about how to live a happy(ier) indoors life.
@SovietBun Which is why I have to introduce some new features. Just fixing the bugs is something everyone can do.
@asteroidbook345 I know.
I'm also investigating possibilities to enhance the function of these landing gears, so the update will come with the upgrade.
@SovietBun It will be more than just recoding so it will take a while.
+1Bug report: (all contents of smooth function omitted)
a smooth function piston that takes the structure of:
smooth() < 0.99 & smooth() > 0.01 (in other words, extend the piston when smooth is > 0.01 and < 0.99)
would fail to function ONLY on the first time the smooth function was triggered.
2nd time and on it worked perfectly. I changed back to the old school sign(min(smooth() - 0.01, 0.99 - smooth())) and it worked first time, every time.
Not sure if the old bug report section on the 202 version post still works for 203 so I just posted it here.
@AndrewGarrison
@WNP78
Hmm I didn't see the picture...
@robloxweponco Yes, we use what we call "biological retraction device" to produce power for the GPS system. lol.
@robloxweponco I'd say it's science, hehehe
I loled at the name.....
@SnoWFLakE0s The point for this change is to make sure anything that FTed during 1.9.1 using LandingGear input still works in 1.9.203.
+1My stuff still does (improvement, they didn't in 202), but no guarantee everyone else's stuff does unless the LG input is the same as 1.9.1.
Since we took the trouble to invent the GearDown input for the "gear down light" purpose, why not just leave LandingGear the way it was in 1.9.1? that's the only way to ensure 1.9.1 planes still works perfectly without having to re-program.
...
my planes will continue to use LandingGear input because 0=down 1=up makes more sense mechanically (because 0 means initial state, and since planes are usually spawned on the ground, the initial state is "down".)
...
Either way I made 3 versions of my Ju 288.
One for 1.9.1 landing gear input, one for .202 beta input and one with .203 beta.
This "should" cover all probable circumstances.
LandingGear now acts exactly as it did before the previous beta
Uh, does it?
pre-beta it's -1 for off and 1 for on (that's why we can continue to use pre-202 beta FTs by reversing the sigh), in this version it seems to be 0 for off and 1 for on.
in other words:
Version<>down<>up
1.9.1xx<>-1<>1
1.9.202<>1<>-1
1.9.203<>0<>1
Because of this, my "fancy landing gear" has to be entirely re-programmed, rather than simply reverse the sign.
Please confirm whether this change is permenant, I have been forced to modify LG input twice, I really hope I don't have to do it a third time...
@AndrewGarrison
@WNP78
Zuiun is good.
+1@SnoWFLakE0s Yeah I think I'm going to get a full list of all airports' coordinates, I'm probably gonna make a VOR/DME navigation system from that.
Wait wut?
+1Latitude and longitude!?
GPS is HERE!
@AndrewGarrison great, thanks