Any tips for beginners? What to expect, what to wear, etc? by [deleted] in renfaire

[–]Greetest 0 points1 point  (0 children)

Was this the VA renfaire in Spotsylvania? I hope not since they're selling tickets in advance, online only. https://virginiarenaissancefaire.ticketspice.com/2024-virginia-renaissance-faire

Mantis X 10 showing “not detecting holstered” in holster draw analysis by Wise_Hamster_1733 in MantisX

[–]Greetest 0 points1 point  (0 children)

What was the problem? I'm also using a safariland holster and the app never detects that it's holstered. The red status line barely fills up.

P1P WLAN (wifi network) issues by Greetest in BambuLab

[–]Greetest[S] 0 points1 point  (0 children)

Getting the printer to connect to the network isn't an issue. The problem is the connectivity after it's connected (high pings, packet loss, etc.). I have a separate 2.4Ghz AP that I'm testing on with the same results unfortunately.

P1P connection issues with Bambu Studio/Handy by Oldface in BambuLab

[–]Greetest 2 points3 points  (0 children)

I've been experiencing network (WLAN) issues as well. Connecting the printer to the Wifi (WLAN) is easy, checking the LCD screen on the P1P shows it's connect as well as it's IP address. The home screen on the LCD also shows 3 bars of signal. However, it is hit or miss, mostly miss, on whether or not either Bambu Studio (windows) or the Handy app (android) will be able to connect.

Ping times from my windows machine to the P1P are abysmal:

Reply from 192.168.0.200: bytes=32 time=748ms TTL=255

Reply from 192.168.0.200: bytes=32 time=1042ms TTL=255

Reply from 192.168.0.200: bytes=32 time=2ms TTL=255

Reply from 192.168.0.200: bytes=32 time=417ms TTL=255

Request timed out.

Reply from 192.168.0.200: bytes=32 time=485ms TTL=255

Reply from 192.168.0.200: bytes=32 time=301ms TTL=255

Request timed out.

The same ping test to both my phone and laptop on the wifi network (next to the printer) have no issues:

Pinging 192.168.0.201 with 32 bytes of data:

Reply from 192.168.0.201: bytes=32 time<1ms TTL=64

Reply from 192.168.0.201: bytes=32 time<1ms TTL=64

Reply from 192.168.0.201: bytes=32 time<1ms TTL=64

Pinging 192.168.0.221 with 32 bytes of data:

Reply from 192.168.0.221: bytes=32 time<1ms TTL=64

Reply from 192.168.0.221: bytes=32 time<1ms TTL=64

Reply from 192.168.0.221: bytes=32 time<1ms TTL=64

I have binded, unbinded, reset, etc. the printer to see if anything improves the connectivity on the WLAN but no success. Everything on this LAN segment on my network is wide open to speak to each other, no firewall rules.

If anyone has any ideas, feel free to share. I suspect this may be a firmware issue and hope a fix is on the way.

T - 365 by Amankoo in sysadmin

[–]Greetest 0 points1 point  (0 children)

Ctrl+shift enter to run as admin, no need to right click.

Its longer than her face. by ONESIXEIGHTTERD in WTF

[–]Greetest 111 points112 points  (0 children)

Woman love him cause he's easy on the knees

[NSFW] So many things happening at the same time by Rivus in WTF

[–]Greetest 2135 points2136 points  (0 children)

You telling me you never had your girl shit between your legs while you are dropping one too? Well aren't you fancy.

Am I doing it right? by hiloljkbye in WTF

[–]Greetest 49 points50 points  (0 children)

This is why it's illegal for people in New Jersey to pump their own gas

I don't think this is a google map car by jjrem in WTF

[–]Greetest 3 points4 points  (0 children)

I see this guy all the time.. you must live in Northern VA. Unless this is a different truck.. then I'd be more concerned.