Gcode Viewer Model Info and Layer Info completely off compared to Slic3r

Hi All,
This is my first post!

Slic3r 2.3.3

What is the problem?
The estimated model size and print time do not match what is coming from Slic3r. The printer traverses the first layer profile but without any filament coming out. I am using a 0.8mm nozzle

What did you already try to solve it?
I activated verbose in Slic3r before exporting the Gcode.

Logs I cancelled the run when I saw that the extruder wasn't doing anything. The print file runs perfect directly from SD card. I want to use Octolapse for this print.

The log file is attached.

Example GCODE file Extract of Gcode file

; generated by PrusaSlicer 2.3.3+win64 on 2021-08-28 at 08:09:13 UTC


; external perimeters extrusion width = 1.00mm
; perimeters extrusion width = 1.00mm
; infill extrusion width = 0.90mm
; solid infill extrusion width = 0.90mm
; top infill extrusion width = 0.80mm
; first layer extrusion width = 0.90mm

M73 P0 R335
M73 Q0 S338
M201 X1000 Y1000 Z200 E5000 ; sets maximum accelerations, mm/sec^2
M203 X200 Y200 Z12 E120 ; sets maximum feedrates, mm/sec
M204 P1250 R1250 T1250 ; sets acceleration (P, T) and retract acceleration (R), mm/sec^2
M205 X8.00 Y8.00 Z0.40 E4.50 ; sets the jerk limits, mm/sec
M205 S0 T0 ; sets the minimum extruding and travel feed rate, mm/sec
M862.3 P "MK3S" ; printer model check
M115 U3.10.0 ; tell printer latest fw version
G90 ; use absolute coordinates
M83 ; extruder relative mode
M104 S220 ; set extruder temp
M140 S60 ; set bed temp
M190 S60 ; wait for bed temp
M109 S220 ; wait for extruder temp
G28 W ; home all without mesh bed level
G80 ; mesh bed leveling
G1 Y-3.0 F1000.0 ; go outside print area
G92 E0.0
G1 X60.0 E9.0 F1000.0 ; intro line
G1 X100.0 E12.5 F1000.0 ; intro line
G92 E0.0
M221 S95
G21 ; set units to millimeters
G90 ; use absolute coordinates
M83 ; use relative distances for extrusion
M900 K0.01 ; Filament gcode LA 1.5
; ; Filament gcode LA 1.0
G92 E0.0

G1 E-1.00000 F2100.000
G1 Z0.400 F10800.000
G1 X43.541 Y76.112
G1 Z0.300
G1 E1.00000 F2100.000
M204 S1000

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware...)

browser.user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36 Edg/92.0.902.78
connectivity.connection_ok: true
connectivity.enabled: true
connectivity.online: true
connectivity.resolution_check: octoprint.org
connectivity.resolution_ok: true
env.hardware.cores: 4
env.hardware.freq: 1500
env.hardware.ram: 3959984128
env.os.bits: 32
env.os.id: linux
env.os.platform: linux
env.plugins.pi_support.model: Raspberry Pi 4 Model B Rev 1.2
env.plugins.pi_support.octopi_version: 0.18.0
env.plugins.pi_support.throttle_state: 0x0
env.python.pip: 20.3.3
env.python.version: 3.7.3
env.python.virtualenv: true
octoprint.safe_mode: false
octoprint.version: 1.6.1
printer.firmware: Prusa-Firmware 3.10.0 based on Marlin
systeminfo.generator: systemapi
octoprint.log (17.1 KB)

Do you have test mode enabled in OctoLapse?

This is embarassing! Yes, it was enabled. I had completely forgotten about it. The first layer in test mode seems to be ok.
Thanks for the quick response!