Packets seem to be created but any of them isn't sent or received.
Too little information to determine anything, but there are several possible causes.
1. lack of Tx power
If this is the cause, using the original scheduler should output the same result.
2.mistake of DCI to transmit
You don't have to disclose the contents of your scheduler here.
But if you've created it, then of course you must have edited the DCI as well.
Make sure the number of symbols and transport block size are large enough and that the MCS is not unnaturally low
■model/nr-mac-scheduler-ns3.cc
uint8_t
NrMacSchedulerNs3::DoScheduleDlData(PointInFTPlane* spoint,
uint32_t symAvail,
const ActiveUeMap& activeDl,
SlotAllocInfo* slotAlloc) const
{
...
std::shared_ptr<DciInfoElementTdma> dci =
CreateDlDci(spoint, ue.first, symPerBeam.at(GetBeam(beam)));
...
NS_LOG_DEBUG(" UE" << dci->m_rnti << " gets DL symbols "
<< static_cast<uint32_t>(dci->m_symStart) << "-"
<< static_cast<uint32_t>(dci->m_symStart + dci->m_numSym) << " tbs "
<< dci->m_tbSize << " mcs " << static_cast<uint32_t>(dci->m_mcs)
<< " harqId " << static_cast<uint32_t>(id) << " rv "
<< static_cast<uint32_t>(dci->m_rv));
3.mistake of result output
Just in case, the measurement of Rx packets and throughput may be broken although your algorithm is properly working.
Do you capture the other outputs like RxPacketTrace, DlDataSinrTrace or DlCtrlSinrTrace? Please share them if you have.