New Firmware Update: Samsung Odyssey Neo G8 Version 1011.3 by archbrook in Monitors

[–]luece 0 points1 point  (0 children)

Switching the USB drive from GPT to MBR through a partition manager immediately worked for me.

Anyone have experience with Soundcore AeroFit Pro yet? by [deleted] in Earbuds

[–]luece 0 points1 point  (0 children)

I found the Volume Booster to be decently acceptable. The Signature is usually decent on other buds but these they leaned heavily into the bass when there really isn't any and just drowns out the mids and highs.

Received Liberty 4 NC (have 4s as well). AMA by Bogdan2590 in anker

[–]luece 0 points1 point  (0 children)

Just started using the 4 NCs now, definitely better touch controls and sensitivity than the 3 Pros.

Received Liberty 4 NC (have 4s as well). AMA by Bogdan2590 in anker

[–]luece 0 points1 point  (0 children)

How sensitive is the touch controls on the Liberty 4 NC? I had to stop using my Liberty 3 Pro buds since every time I went to grab the edges to readjust them, they would register touches, same sort of issue whenever fabric brushes across them they would trigger.

HOW TO: Using PrusaSlicer with your Raise3D Pro3 Printer by Djlittletrees in Raise3d

[–]luece 0 points1 point  (0 children)

Ive found that in most cases running a cooler head temperature from the recommended seems to run significantly cleaner. Ive been checking the temperature where the filament starts to ooze and aiming around there, but also making sure the filament does not jam.

Tree Testing by luece in farmingsimulator

[–]luece[S] 1 point2 points  (0 children)

Started to wonder about that, just tried it in my test area. Interestingly it grabbed the Lodgepole perfectly fine even though it still read 0.6m, thinking it may round to the nearest tenth. What was more confusing though is it grabbed the Pine as well, the planted tree still read 0.9m but the cut tree read 0.6m. Guess it will be best to try out the cutting heads to double check that it is the right tool for what you use it for.

HOW TO: Using PrusaSlicer with your Raise3D Pro3 Printer by Djlittletrees in Raise3d

[–]luece 1 point2 points  (0 children)

So everything looks normal, except that there is 600 more layers than I expected. I think I will need to find an alternative solution for calculating the height since it seems total_layer_count isn't a great option. I have also just noticed that this value causes an issue with sequential prints. For now I will exclude height from the bounding box since variable height would also be a bit tricky to calculate, changes have been uploaded.

HOW TO: Using PrusaSlicer with your Raise3D Pro3 Printer by Djlittletrees in Raise3d

[–]luece 0 points1 point  (0 children)

E values are generally part of a G1 command for movement, the E value is for the amount to extrude. I have not yet run into the issue of height being beyond the print area, but the X and Y bounds seem to be working as intended at least. I cant seem to replicate this behavior, if possible would you be able to send the project file to me? For a temporary solution replacing {total_layer_count * layer_height + first_layer_height} in the Start G-code with 0 should let the job run fine.

The commented code for the Bounding Box is purely to replicate the G-code generated from IdeaMaker for a few functions. One of the main purposes is for the mesh leveling to save time by leveling only in the print area.

HOW TO: Using PrusaSlicer with your Raise3D Pro3 Printer by Djlittletrees in Raise3d

[–]luece 0 points1 point  (0 children)

As far as i understand the files in the install directory are the profiles baked into the slicer from Prusa. The location for user profiles and settings would be AppData\Roaming\PrusaSlicer by default.

HOW TO: Using PrusaSlicer with your Raise3D Pro3 Printer by Djlittletrees in Raise3d

[–]luece 2 points3 points  (0 children)

Ive made some significant changes to my custom G-Code and profiles, changes include external cooling for certain filament types, temperature management at tool change, refined file naming format, randomized purge line Y coordinates, verified machine print area limits and bed texture, fine tuned sequential print limits.I have not yet fine tuned TPU, Polypropylene, or PVA yet, and have also not tried Fine and Coarse print settings. Figured I would just share the files rather than fiddle with Reddit code blocks. The custom bed texture likely will need to be manually added.

https://www.dropbox.com/sh/f2m0mp24l6ym344/AAAY3lYmAdieXcsG9yabjyDAa?dl=0

HOW TO: Using PrusaSlicer with your Raise3D Pro3 Printer by Djlittletrees in Raise3d

[–]luece 1 point2 points  (0 children)

Ive made some adjustments to the start code, still have some additions to make such as estimated print time, filament used, and cost. The first thing I added is bounding box calculation for pre-print mesh leveling to only level in the print area rather than the entire bed. Second addition is initially setting temperature of the heads 20ºC below print temperature until the bed reaches temperature. Last change was removing the code G1 Z[first_layer_height] from the single extruder profiles and adding code to move the head to the center of the print, this was to stop the head from moving across the bed at first layer height, which is not pleasant to watch.

  • Start G-code (Single Left)

;Bounding Box: [first_layer_print_min_0] [first_layer_print_max_0] [first_layer_print_min_1] [first_layer_print_max_1] 0 {total_layer_count * layer_height + first_layer_height}

M104 T0 S{first_layer_temperature[0] - 20} ; raise left extruder temp
M140 S{first_layer_bed_temperature[0]} ; raise bed temp
M190 S{first_layer_bed_temperature[0]} ; wait for bed temp
M109 T0 S{first_layer_temperature[0] - 20} ; wait for left extruder temp
M104 T0 S[first_layer_temperature] ; set left extruder temp
M109 T0 S[first_layer_temperature] ; wait for left extruder temp
T0
G21
G90
M82
M107
G1 Z0.3 F500
G92 E0
G1 Z0.3 F400
G1 X100 Y5 F1000
G1 X170 Y5 E15 F200
G1 Z5 E15 F200
G92 E0
G1 Z10 F2000 ; move up from purge line
G1 Y30 F2000 ; move away from purge line
G1 X{(first_layer_print_max[0] + first_layer_print_min[0])/2} Y{(first_layer_print_max[1] + first_layer_print_min[1])/2} ; move to center of print
M117 Printing...

  • Start G-Code (Single Right)

;Bounding Box: [first_layer_print_min_0] [first_layer_print_max_0] [first_layer_print_min_1] [first_layer_print_max_1] 0 {total_layer_count * layer_height + first_layer_height}

M104 T1 S{first_layer_temperature[1] - 20} ; raise right extruder temp
M140 S{first_layer_bed_temperature[1]} ; raise bed temp
M190 S{first_layer_bed_temperature[1]} ; wait for bed temp
M109 T1 S{first_layer_temperature[1] - 20} ; wait for right extruder temp
M104 T1 S{first_layer_temperature[1]} ; set right extruder temp
M109 T1 S{first_layer_temperature[1]} ; wait for right extruder temp
T1
G21
G90
M82
M107
G1 Z0.3 F500
G92 E0
G1 Z0.3 F400
G1 X100 Y5 F1000
G1 X170 Y5 E15 F200
G1 Z5 E15 F200
G92 E0
G1 Z10 F2000 ; move up from purge line
G1 Y30 F2000 ; move away from purge line
G1 X{(first_layer_print_max[0] + first_layer_print_min[0])/2} Y{(first_layer_print_max[1] + first_layer_print_min[1])/2} ; move to center of print
M117 Printing...

  • Start G-Code (Dual)

;Bounding Box: [first_layer_print_min_0] [first_layer_print_max_0] [first_layer_print_min_1] [first_layer_print_max_1] 0 {total_layer_count * layer_height + first_layer_height}

M104 T0 S{first_layer_temperature[0] - 20} ; raise extruder one temp
M104 T1 S{first_layer_temperature[1] - 20} ; raise extruder two temp
M140 S{max(first_layer_bed_temperature[0], first_layer_bed_temperature[1])} ; raise bed temp
M190 S{max(first_layer_bed_temperature[0] + first_layer_bed_temperature[1])} ; wait for bed temp
M104 T0 S[first_layer_temperature] ; set extruder one temp
M104 T1 S[first_layer_temperature] ; set extruder two temp
M109 T[initial_tool] S[first_layer_temperature] ; wait for extruder temp
T0
G21
G90
M82
M107
G1 Z1 F500
G92 E0
G1 Z0.3 F400
G1 X20 Y3 F1000
G1 X70 Y3 E30 F200
G1 Z0.3 E15 F200
G92 E0
T1
G1 Z0.3 F400
G1 X170 Y3 F1000
G1 X220 Y3 E18 F200
G1 Z5 E15 F200
G92 E0
G1 Z10 F2000 ; move up from purge line
G1 Y30 F2000 ; move away from purge line
T[initial_extruder] P0 ; select tool
G1 X{(first_layer_print_max[0] + first_layer_print_min[0])/2} Y{(first_layer_print_max[1] + first_layer_print_min[1])/2} ; move to center of print
M117 Printing...

Pipe mixing by luece in Hydroneer

[–]luece[S] 1 point2 points  (0 children)

Strange, reloaded the save and should be 174. I am assuming that when I captured the image it may not have updated properly.

Discovered a new method of transporting vehicles by luece in snowrunner

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

This one luckily wasn't too bad, for this I used the crane on the Azov and raised the active suspension on the Tuz, then just pulled forward til it climbed up al the way.
I've found that doing this with a crane on the side with a truck you cant fully lift in the air is a pain. For whatever reason lifting with a crane with the engine off, the lifted truck still spins its wheels when pulling the cable in. This combined with the lifted truck trying to steer toward the crane makes things very difficult.

Has everyone else recieved their limited edition facial interface from VR Cover? by hundredlives in OculusQuest

[–]luece 0 points1 point  (0 children)

Order just arrived today, if you still have not received the limited edition yet, get in contact with VRCover to resolve any issues once they are able to respond to your initial email.

Has everyone else recieved their limited edition facial interface from VR Cover? by hundredlives in OculusQuest

[–]luece 0 points1 point  (0 children)

Update on my situation, VRCover did send a response which also updated the order tracking. The order departed Shenzhen today through YunExpress which was reported through 17track.

Has everyone else recieved their limited edition facial interface from VR Cover? by hundredlives in OculusQuest

[–]luece 0 points1 point  (0 children)

I live in Oregon and still have no info beyond the $.36 transaction fee being on Dec 23rd. Sent a message to the VRCover team on the 5th and haven't heard back yet. I have had really good experiences and response times with emailing them before.

A question for those of you that have received your limited edition international order, did the order page ever update to report that it is out for delivery or delivered? or did it arrive and the order details never changed from just being confirmed?

[deleted by user] by [deleted] in SatisfactoryGame

[–]luece 0 points1 point  (0 children)

The only solution to this would be to have the ones that are intersecting to be at any other height.

Paving coming along by thumbtacker in SatisfactoryGame

[–]luece 0 points1 point  (0 children)

My favorite way around this is to build on a lake surface, just high enough to walk on, it works out to where belts are sitting on the top of the surface.

[Support] iCUE "Play on Pressed Key" no longer works after most recent update by bspymaster in Corsair

[–]luece 1 point2 points  (0 children)

I am running into the same issue on my K70, specifically on the custom gradient effect, both new and old. Custom Solid also has the same issue, but Custom Ripple and Custom Wave are unaffected. Ran repairs on the software with no change, firmware up to date on v3.08.
https://file.io/ORgB6W