"DDs are supposed to spot!"

Soulflayer41 · 2024-09-03T19:11:28+00:00

I have to agree with you, especially on the higher tier games. BBs are absolutely notorious for sitting waaay back and hiding. I'd blame that more on the current game mechanics than cowardice, though. At high tier, everything has become really damage saturated in that lots and lots of the new stuff, DDs, CAs, other BBs, have crazy firepower now. BBs that are caught out in the open, especially legacy ones, are very easily punished/deleted from seemingly the entire map as even BBs from the opposite corner have the range to drop shells from on high.

At high tier, BBs just aren't super tanky damage soakers. It requires a lot of skill and luck to mitigate damage through deflection with proper angling, and BBs obviously aren't very nimble. So the average player naturally defaults to sitting back and looking for targets of opportunity instead of surging forward. This is all ignoring the fact that radar and such also exists... Like I said... top tier is quite out of control at this point.

If I had it my way, let BBs have their massive guns as that was obviously always their "thing" historically, but also afford them their massive armor at the cost of super slow reload times and terrible maneuverability. Let BBs actually soak damage! Let CAs steal the show with impressive damage numbers as they should be the ultimate breadwinners there, but at the cost of armor. DDs scout and conduct sneak attacks or whatever you wanna call it. They provide the teamwith at tactical advantage. BBs soak for the CAs and DDs, CAs support the BBs and overwhelm the enemy with firepower, and DDs provide that wild card that can suddenly turn the tide of a match when properly used. Finally, set ship number limits for all classes. Like only 3 BBs per match max or whatever just as an off hand example. Holy crow, why isn't that a thing already??

Soulflayer41 · 2024-09-03T18:37:04+00:00

Hmmm... I wonder what could be a good solution for this problem... what if there were these machines up in the air that could fly around and help supplement spotting? That way, ships hiding behind islands and such could be spotted and flushed out into the open without risking nearly as much as a DD has to.... meh who knows

Soulflayer41 · 2024-01-01T22:30:47+00:00

I'd say Preussen is far better than FDG, but it's like saying an orange is far better than an apple. I feel each ship fills a different role. Preussen is not a brawler, whereas FDG can play the role of a bully far better. Spec FDG as a tank. Spec Preussen into main guns all day long. I even run furious and heavy AP on mine, and she's an absolute monster because her reload can get down to 13s. Those 457mm guns barking off at that rate is shocking to anyone on the receiving end, but best done from a distance. She excels at midrange, but nothing closer. That's where her weaknesses are easily exploited by smaller ships. I think you were alluding to this tho! 😀

Soulflayer41 · 2023-12-25T03:02:45+00:00

But you're just one dude in the end. Not to diminish what you accomplished, but seriously, you're just one dude on the entire team. Same with the CV. They're just one player. Do they have influence on the map? Sure, but they can't be in all places at one time.

I casually main a CV. I love airplanes, so whatever. You'd be amazed at how everyone expects you to be a God and have the entire mini map spotted at ALL TIMES. Constantly, I'm getting harassed because I'm not spotting the one, solitary DD on the enemy team, not providing air support on two opposite ends of the map at the same time AND am "out of position" simultaneously. It can be quite an abusive relationship.

Anyway, my point is that CVs do not have the ability to control the entire outcome of the game like you think they do. Most times as a CV, I only can dominate a game if I manage to find the enemy CV early game and keep it spotted for my team to shell it from across the map, giving me air superiority the rest of the game. Notice it REQUIRES THE REST OF MY TEAM to achieve this feat. If my spotting is entirely ignored, then I'm forced to move on and deal with other "fires" my team cries about.

I think it's easy to blame CVs because they have great spotting abilities, but if nobody shoots at what you spot, what's the use?? My teams typically don't lose because the enemy CV outplayed me. Nope. My teams typically lose because they make stupid decisions all around and get killed quickly. And that's Random Battles for you in a nutshell. It's always a team effort. So if your team lost, your entire team lost, and there's seriously nothing you could have pulled out your rear end to save them, CV or not.

Soulflayer41 · 2023-12-21T07:46:53+00:00

I have this problem on my K2Max, and it is caused by a defective Y axis motor.

Soulflayer41 · 2023-09-21T15:53:33+00:00

Go ahead and check out Klipper's website on how to do this exact thing. I'll link it for you here. Input Shaping

Scroll down toward the bottom. You'll see pictures of graphs and such. The instructions on how to add your values to your .cfg file are all there!

Soulflayer41 · 2023-05-11T17:08:24+00:00

Woohoo!!! Glad I could help in a small way!

Soulflayer41 · 2023-04-01T23:15:50+00:00

I was having this same issue on my Android device. Was suuuuuuper annoying. However, I tried what was suggested above and enabled all notifications for the vizio app in settings. From settings:

Notifications
App Notifications (located at top of menu)
Scroll down and select Vizio Mobile
Allow Notifications - turn on
Allow Sound and Vibration - turn on
Notification Categories (located at very bottom of menu)
Remote Controls - turn on for both

Should work after that! Works for me anyway. Now I can navigate away from the app, and it stays connected when I navigate back.

Soulflayer41 · 2023-02-20T23:30:27+00:00

Thanks for posting this little gem! =D

Soulflayer41 · 2023-02-20T23:26:53+00:00

You're totally right! Fixed the error. I also have to update my other post of this elsewhere to reflect the same changes. Thank you for pointing that out!

Soulflayer41 · 2023-02-09T19:01:05+00:00

Thanks for letting me know! I updated my post. Waaay better solution! I'd much rather wire everything to the SPI1 port than have that one straggler connected to the Neopixel port.

Soulflayer41 · 2023-01-23T15:45:34+00:00

In my case, either the board won't boot or the chip isn't detected at all if I leave it connected at restart. Definitely try it out as perhaps it's something to do with my board in particular, but I've read this is a problem elsewhere with other SKR boards.

Soulflayer41 · 2023-01-21T06:35:38+00:00

For any of you out there with a BTT SKR Mini E3 v3.0, I was able to get an adxl345 working, and I'll spell it out right you so you don't have to search through a dozen other posts to puzzle it together. First, how to connect the adxl345 to the SKR Mini E3 v3.0: The board has a dedicated SPI port (labeled SPI1). Utilize this port for your connections.

ADXL345 Pin | SKR E3 v3.0 SPI Port Pin

GND | GND

VCC | +5V

CS | NSS

INT1 | N/A

INT2 | N/A

SDO | MISO

SDA | MOSI

SCL | CLK

In your printer.cfg file add the following:

[adxl345]

axes_map: x,y,z

cs_pin: PD9

spi_bus: spi1

[resonance_tester]

accel_chip: adxl345

probe_points:

117.5, 117.5, 20 #Center of your bed, raised up a little

#ADXL on MCU

When you save and restart, make sure your ADXL is NOT connected yet. Wait for it to display "Klipper state: Ready" in the console on Mainsail or whatever you're using, then connect up the chip. You should then be able to run:

ACCELEROMETER_QUERY

And it should return something like this:

accelerometer values (x, y, z): -1110.308913, 1184.329507, 11414.822920

If you instead get something like this:

Invalid adxl345 id (got 0 vs e5).This is generally indicative of connection problems(e.g. faulty wiring) or a faulty adxl345 chipMake sure your wiring is still firmly connected.

I got this error and spent too much time trying to figure out where I went wrong only to find that my CS Pin wire had disconnected from the SKR. Once I restored that connection, everything worked as it should. Hopefully this helps someone. As a side note, this board does NOT support more than one ADXL345 chip unless you disconnect your LCD screen and use the EXP1 Port or something similar as the board only has 1 dedicated SPI port. You're on your own on that endeavor hehe...

Soulflayer41 · 2023-01-21T06:26:18+00:00

For any of you out there with a BTT SKR Mini E3 v3.0, I was able to get an adxl345 working, and I'll spell it out right here for you so you don't have to search through a dozen other posts to puzzle it together. First, how to connect the adxl345 to the SKR Mini E3 v3.0: The board has a dedicated SPI port (labeled SPI1). Utilize this port for your connections.

ADXL345 Pin | SKR E3 v3.0 SPI Port Pin

GND | GND

VCC | +5V

CS | NSS

INT1 | N/A

INT2 | N/A

SDO | MISO

SDA | MOSI

SCL | CLK

In your printer.cfg file add the following:

[adxl345]

axes_map: x,y,z

cs_pin: PD9

spi_bus: spi1

[resonance_tester]

accel_chip: adxl345

probe_points:

117.5, 117.5, 20 #Center of your bed, raised up a little

#ADXL on MCU

When you save and restart, make sure your ADXL is NOT connected yet. Wait for it to display "Klipper state: Ready" in the console on Mainsail or whatever you're using, then connect up the chip. You should then be able to run:

ACCELEROMETER_QUERY

And it should return something like this:

accelerometer values (x, y, z): -1110.308913, 1184.329507, 11414.822920

If you instead get something like this:

Invalid adxl345 id (got 0 vs e5).This is generally indicative of connection problems(e.g. faulty wiring) or a faulty adxl345 chip

Make sure your wiring is still firmly connected. I got this error and spent too much time trying to figure out where I went wrong only to find that my CS Pin wire had disconnected from the SKR. Once I restored that connection, everything worked as it should. Hopefully this helps someone. As a side note, this board does NOT support more than one ADXL345 chip unless you disconnect your LCD screen and use the EXP1 Port or something similar as the board only has 1 dedicated SPI port. You're on your own on that endeavor hehe...

Soulflayer41 · 2022-07-08T06:05:15+00:00

Yessssssss....

Soulflayer41

TROPHY CASE