## 5 Simulation Analysis
### Simulation Results and Analysis  
As shown in Figure 7, \(Delay_{Avg}\) decreases as node density increases. EAVARP achieves the lowest delay by using opportunistic forwarding to avoid routing-voids. Although APCDBR reduces delay through energy and power control, the lack of explicit void avoidance can lead to retransmissions. In contrast, APC-EEDBR introduces link energy stability and dynamic weight adjustment, resulting in more reliable paths and fewer required retransmissions. DBR's broadcast-based forwarding increases the delay, while EEDBR, although energy-aware, lacks adaptive path optimization. Figure 7: Influence of node density on \(Delay_{Avg}\). Figure 8 shows the impact of node density on \(L_{Avg}\), defined by the round when the first relay dies. APC-EEDBR achieves the longest lifetime by combining energy awareness, power control, and link stability to balance the load and reduce energy waste. DBR quickly depletes energy due to redundant broadcasts. Although EEDBR and EAVARP offer some improvement, they lack effective balancing in dense networks. APCDBR considers energy and power; however, without void avoidance, it may select inefficient next hops, leading to early failures. From Figure 9, it is evident that with a fixed node count, APC-EEDBR exhibits slower node death rates and more gradual network degradation due to its power adjustment and energy balancing mechanisms. In contrast, the APCDBR fails to avoid routing voids, causing broadcast storms that increase energy consumption and accelerate node death. Similarly, DBR suffers from severe node overload, which leads to rapid early node failure. EEDBR and EAVARP also experience accelerated node deaths in the later stages due to an uneven forwarding load distribution. Figure 8: Influence of number of nodes on \(L_{Avg}\). Figure 9: Node death progression with respect to simulation rounds. As presented in Figure 10, in low-speed or static scenarios, the APC-EEDBR achieves lower energy consumption through energy awareness and fine-grained relay selection, demonstrating strong energy control capabilities. However, in high-speed scenarios, EAVARP exhibits more stable energy consumption and better per-packet energy efficiency. This is mainly due to the use of a fixed candidate set and energy balancing mechanisms, which effectively reduce the number of retransmissions. In contrast, the energy efficiency advantage of APC-EEDBR diminishes at high speeds due to the increased control overhead and frequent path updates. Figure 11 shows that APC-EEDBR performs well at low speeds but degrades under high mobility due to control overhead and next-hop selection failures. DBR maintains a stable PDR owing to flooding, although it is energy inefficient. EAVARP and EEDBR both degrade rapidly due to rigid forwarder sets and weak link prediction. The APCDBR suffers from forwarding holes in the later rounds. These results highlight that all protocols face link instability under high mobility, and opportunistic routing could be a promising enhancement in such scenarios. Figure 11: Influence of node speed on PDR. Figure 10: Influence of node speed on \(E_{con}\). Figure 12 shows that as node speed increases, the \(Delay_{Avg}\) of APC-EEDBR shows a slight rise, indicating that it maintains good path adaptability and routing stability under dynamic topologies. DBR, which employs a stateless depth-based forwarding strategy, exhibits minimal delay fluctuations due to its low path maintenance overhead. However, it suffers from high redundancy and low efficiency. EAVARP maintains a relatively stable delay owing to its fixed path structure; however, it lacks a link quality feedback mechanism. In contrast, EEDBR experiences a significant increase in delay, reflecting the inefficiency of its path reselection mechanism under high-mobility conditions. The APCDBR exhibited moderate performance overall. However, due to the lack of explicit link void avoidance, it may trigger additional broadcast packets when voids occur, causing a slight increase in delay.