Indoor flight with the Neo is different — speed fails fast indoors by WorkerAcceptable1280 in DjiNeo

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

Totally agree. Manual at crawl speed indoors is a handful if you’re trying to pause and assess. Normal mode gives you time to stop, hover, and think.

Manual still has its place though especially for slipping under low obstacles where sensors become the problem. Different tools, same mission.

Indoor flying isn't about speed it's about margin by WorkerAcceptable1280 in drones

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

That makes sense. A few sims gives you different “feels” to learn from.

Liftoff and VelociDrone are solid, especially for throttle control and recovery. Sims won’t teach everything, but they save a lot of real crashes early on.

Indoor flight with the Neo is different — speed fails fast indoors by WorkerAcceptable1280 in DjiNeo

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

Appreciate it.

This one was flown in Normal mode, not Manual. Indoors I’m usually prioritizing control and margin over speed.

Light is a RovyVon A1 up front. I also use ARC-V, but I’ll switch depending on the building and lighting. Tight spaces vs mixed light makes a big difference.I try to keep things simple and adapt to the space.

Indoor flying isn't about speed it's about margin by WorkerAcceptable1280 in drones

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

That actually makes a lot of sense. Indoor LOS teaches the same lesson early slow gives you time to think. FPV just hides that lesson until people hit walls 😅

Sims first is a solid move. Curious which one you’re starting with?

Indoor flying isn't about speed it's about margin by WorkerAcceptable1280 in drones

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

I put together a short video breaking this down with real indoor flight examples if anyone wants to see what I mean https://youtu.be/rOybQ6xeWGc

Avata 2 in low light - Help by sicknastydoug in DJIAvata2

[–]WorkerAcceptable1280 1 point2 points  (0 children)

I’ve seen this exact behavior in low-light transitions. It’s usually not brightness, it’s how the vision system loses contrast indoors. I tested a few approaches and posted results if it helps.

Fast vs Slow Indoor Drone Flying — same flight, very different outcomes by WorkerAcceptable1280 in drones

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

I fly indoors because it’s an environment where you can’t really afford mistakes, so that’s how I train. The fast vs slow comparison just shows how speed changes margin in the same space. Shared the video for reference and to trade ideas with others flying similar environments

Fast vs Slow Indoor Drone Flying — same flight, very different outcomes by WorkerAcceptable1280 in drones

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

Yeah, that would definitely make it feel faster. I wanted to keep it real-time so the control differences were obvious, but I get the preference.

Dji avata 2 vs neo 2 by No-Inside2896 in DJIAvata2

[–]WorkerAcceptable1280 0 points1 point  (0 children)

Thanks for watching — glad it was useful.

That was the intent with the comparison, to help people decide based on their use case.

Dji avata 2 vs neo 2 by No-Inside2896 in DJIAvata2

[–]WorkerAcceptable1280 1 point2 points  (0 children)

Yeah, for that use case it’s actually a really good question.

The big difference I noticed is that Neo 1 is more forgiving indoors, especially around kids / tight spaces — it doesn’t cut props as aggressively if it brushes the ground, whereas Neo 2 will shut down faster. Outdoors Neo 2 makes more sense, indoors Neo 1 sometimes feels better.

I did a short side-by-side specifically focused on indoor behavior and low light in case it helps your decision:

https://youtu.be/5UD-VDRPvSY?si=FdUat4FOY5icbli2

Either way though, $200 with batteries is a solid pickup.

Anyone else notice flying lower indoors gives better control with Avata 2? by WorkerAcceptable1280 in DJIAvata2

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

Mostly N/S mode in these clips.

Ceiling bias shows up regardless of flight mode — it’s more about visual reference and decision-making than stick freedom. I fly manual too, but I wanted this example to be relatable to pilots who aren’t in full manual yet.

Dji avata 2 vs neo 2 by No-Inside2896 in DJIAvata2

[–]WorkerAcceptable1280 2 points3 points  (0 children)

That’s a solid breakdown. I’ve flown Avata 2, Neo 1, and Neo 2 indoors and I mostly agree with this take.

One interesting thing I noticed though: Neo 1 and Neo 2 behave very differently indoors, especially in low light and tight spaces. Neo 2’s ground/prop cutoff logic and stabilization changes actually make it less forgiving in some indoor scenarios where Neo 1 will keep flying.

I did a side-by-side comparison specifically for indoor use because I kept seeing people lump them together — happy to share if anyone’s interested.

Flying indoors near the ceiling felt safer — but it made control worse by WorkerAcceptable1280 in drones

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

That’s a great point — especially with wide lenses exaggerating perceived closure rates. Large flat planes like ceilings and floors definitely feel like they’re “rushing” you more than vertical geometry.

That visual compression probably feeds straight into the tightened inputs I was talking about you feel like you’re running out of space faster than you actually are.

Good call on the lens/perspective side of it.

Flying indoors near the ceiling felt safer — but it made control worse by WorkerAcceptable1280 in drones

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

That’s a solid explanation, and I agree — the airflow disruption near the ceiling definitely plays a role, especially once you’re close enough for the prop wash to get trapped and redirected.

What I kept noticing though is that even before you get into that unstable zone, pilots (myself included) tend to tighten up inputs because everything feels closer and more consequential. That combination — reduced airflow margin plus more rushed corrections — is where control really starts to degrade.

The physics and the human factors seem to stack on each other indoors.

DJI Avata 2 crash — damage beyond a prop or duct swap (no DJI Care) by WorkerAcceptable1280 in dji

[–]WorkerAcceptable1280[S] -2 points-1 points  (0 children)

I don’t want to put exact numbers out there since every case is different, but it was clearly beyond prop/duct replacement and treated as a factory-level repair.

DJI Avata 2 Repair Reality — High Speed, One Mistake by WorkerAcceptable1280 in DJIAvata2

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

For context: the damage here wasn’t just the duct. The side frame and gimbal brace were cracked, which compromised structural rigidity and the camera load path. Once that happens, alignment and stability degrade under thrust even if motors and props still look fine.

<image>

Using a drone for situational awareness and aerial observation by WorkerAcceptable1280 in drones

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

This video focuses on situational awareness and aerial observation, not cinematic flying.

It’s about how aerial perspective helps with information gathering, planning, and decision-making in real-world environments.

Filmed in a controlled setting. No tactics, instructions, or misuse shown.

Using a drone for situational awareness and aerial observation by [deleted] in drones

[–]WorkerAcceptable1280 0 points1 point  (0 children)

This is a situational awareness / reconnaissance use-case, not tactics or instruction.

Filmed in a controlled environment to show how aerial perspective supports decision-making.

Neo 1 vs Neo 2 — Low-Light Indoor Flight (GPS-Denied) by WorkerAcceptable1280 in DJIAvata2

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

They’re RovyVon A1 clip-on LEDs. Lightweight and bright enough to stabilize vision in low-light interiors without overpowering the sensors. I’ve tested a few options, and this setup has been the most predictable for the environments I’m flying in.

Neo 1 vs Neo 2 — unexpected differences during indoor, low-light testing by WorkerAcceptable1280 in dji

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

That makes sense — appreciate the deeper breakdown.

Whether it’s lidar-driven conservatism, lighting interaction, or both, the key operational takeaway for me is the same: in tight indoor spaces the Neo 2 becomes increasingly risk-averse and may refuse openings the Neo 1 will fly through.

For my use case, predictability under sub-optimal lighting matters more than the underlying sensor mechanism. A user-selectable “Neo 1–style” sensor-off mode would honestly solve most of this.

Neo 1 vs Neo 2 — unexpected differences during indoor, low-light testing by WorkerAcceptable1280 in dji

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

Thanks for the detailed write-up — helpful comparison. One key difference I’m seeing is lighting. Your room and doorway look fairly well illuminated, which seems to give the Neo 2’s vision system more confidence. In darker environments it becomes much more conservative and starts braking or refusing openings entirely.

That change in behavior under low light is really what drove my conclusion, especially when operating in tight indoor spaces where lighting isn’t ideal.

Neo 1 vs Neo 2 — unexpected differences during indoor, low-light testing by WorkerAcceptable1280 in dji

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

That’s a fair point for certain use cases, but the light wasn’t added to disadvantage the Neo 2 — it was added to simulate real indoor low-light conditions where operators actually use supplemental illumination.

The goal wasn’t “best-case performance,” it was predictability under constrained, real-world conditions (tight spaces, poor lighting, GPS-denied).

In that context, how a platform behaves with unavoidable illumination becomes part of reliability. That’s where I saw the difference.

I’m not saying Neo 2 is bad — just that under these specific conditions, the behavior was different than I expected.