diff --git a/DAILY_CHECKLIST.md b/DAILY_CHECKLIST.md
index 11a463b..fe3c0c1 100644
--- a/DAILY_CHECKLIST.md
+++ b/DAILY_CHECKLIST.md
@@ -1,23 +1,23 @@
 # Daily Checklist - Master's Thesis Completion
-**Deadline: February 10, 2026 | Days Remaining: 29**
+**Deadline: February 15, 2026**
 
 ---
 
-## 📅 Week 1: January 13-19 - PERFORMANCE DATA COLLECTION
+## 📅 Week 1: January 16-22 - PERFORMANCE DATA COLLECTION
 
-### Monday, January 13 (Day 1)
+### Friday, January 16 (Day 1)
 - [ ] Install/verify NVIDIA Nsight Graphics
-- [ ] Document test hardware specs (CPU, GPU, RAM, OS)
-- [ ] Create test scenario document (what you'll measure)
-- [ ] Run Unity game, capture 2-3 frames in Nsight
+- [ ] Document test hardware specs (run `./scripts/get_hardware_specs.sh`)
+- [ ] Review test scenario document (`./scripts/test_scenarios.md`)
+- [ ] Run Unity game, capture 2-3 frames in Nsight (or use `./scripts/run_unity_test.sh`)
 - [ ] Start expanding Chapter 4 methodology section
 
 **Goal**: Nsight working, first captures done, methodology started
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Tuesday, January 14 (Day 2)
+### Saturday, January 17 (Day 2)
 - [ ] Complete Unity game testing (5-10 frame captures total)
 - [ ] Capture at different difficulty levels (low/medium/high bullets)
 - [ ] Export key metrics from Nsight (frame time, draw calls, memory)
@@ -25,11 +25,11 @@
 - [ ] Continue Chapter 4 (methodology section)
 
 **Goal**: All Unity data collected, methodology 60% done
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Wednesday, January 15 (Day 3)
+### Sunday, January 18 (Day 3)
 - [ ] Run Unreal game, capture 2-3 frames in Nsight
 - [ ] Test at equivalent difficulty levels to Unity
 - [ ] Document any differences in testing approach
@@ -37,11 +37,11 @@
 - [ ] Compare data format from both engines
 
 **Goal**: Unreal testing started, initial comparison notes
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Thursday, January 16 (Day 4)
+### Monday, January 19 (Day 4)
 - [ ] Complete Unreal game testing (5-10 captures total)
 - [ ] Organize all captured data in spreadsheet/CSV
 - [ ] Create comparison tables (Unity vs Unreal)
@@ -53,7 +53,7 @@
 
 ---
 
-### Friday, January 17 (Day 5)
+### Tuesday, January 20 (Day 5)
 - [ ] Create graph 1: Frame time comparison
 - [ ] Create graph 2: GPU utilization comparison
 - [ ] Create graph 3: Memory usage comparison
@@ -61,11 +61,11 @@
 - [ ] Start creating LaTeX tables for results
 
 **Goal**: 4+ publication-quality graphs created
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-### Saturday, January 18 (Day 6)
+### Wednesday, January 21 (Day 6)
 - [ ] Create remaining graphs/visualizations
 - [ ] Finalize all comparison tables in LaTeX format
 - [ ] Save all figures to latex/tex/img/
@@ -73,11 +73,11 @@
 - [ ] Test that figures compile in LaTeX
 
 **Goal**: All visualizations ready, saved in correct format
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-### Sunday, January 19 (Day 7) - WEEK 1 CHECKPOINT
+### Thursday, January 22 (Day 7)
 - [ ] Write Chapter 5 Section 5.1 (Test methodology)
 - [ ] Write Chapter 5 Section 5.2 (Test scenarios)
 - [ ] Write Chapter 5 Section 5.3 (Results - Unity)
@@ -86,13 +86,13 @@
 - [ ] Insert all figures and tables with proper references
 
 **✅ WEEK 1 MILESTONE**: Chapter 5 complete (200+ lines), all data collected
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-## 📅 Week 2: January 20-26 - ANALYSIS & COMPARISON
+## 📅 Week 2: January 23-29 - ANALYSIS & COMPARISON
 
-### Monday, January 20 (Day 8)
+### Friday, January 23 (Day 8)
 - [ ] Chapter 6 Section 6.1: Graphics capabilities (Unity URP vs Unreal)
 - [ ] Chapter 6 Section 6.2: Shader systems comparison
 - [ ] Chapter 6 Section 6.3: Lighting and post-processing
@@ -100,11 +100,11 @@
 - [ ] Target: 60-80 new lines in Chapter 6
 
 **Goal**: Half of Chapter 6 capabilities analysis done
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Tuesday, January 21 (Day 9)
+### Saturday, January 24 (Day 9)
 - [ ] Chapter 6 Section 6.4: Physics engine comparison
 - [ ] Chapter 6 Section 6.5: Audio systems
 - [ ] Chapter 6 Section 6.6: Animation systems
@@ -112,11 +112,11 @@
 - [ ] Target: Chapter 6 complete (180+ lines total)
 
 **Goal**: Chapter 6 finished
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Wednesday, January 22 (Day 10)
+### Sunday, January 25 (Day 10)
 - [ ] Chapter 7 Section 7.1: Synthesis of performance results
 - [ ] Create master comparison table (all metrics)
 - [ ] Chapter 7 Section 7.2: Multi-criteria analysis
@@ -124,11 +124,11 @@
 - [ ] Target: 50% of Chapter 7 done
 
 **Goal**: Results synthesis and main comparison table
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Thursday, January 23 (Day 11)
+### Monday, January 26 (Day 11)
 - [ ] Chapter 7 Section 7.3: Use case recommendations (indie games)
 - [ ] Chapter 7 Section 7.3: Use case recommendations (mobile games)
 - [ ] Chapter 7 Section 7.3: Use case recommendations (AAA games)
@@ -140,7 +140,7 @@
 
 ---
 
-### Friday, January 24 (Day 12)
+### Tuesday, January 27 (Day 12)
 - [ ] Chapter 8 Section 8.1: Main research findings
 - [ ] Answer all research questions from introduction
 - [ ] Verify hypotheses (state which confirmed/rejected)
@@ -148,11 +148,11 @@
 - [ ] Target: 50% of Chapter 8 done
 
 **Goal**: Core conclusions written
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-### Saturday, January 25 (Day 13)
+### Wednesday, January 28 (Day 13)
 - [ ] Chapter 8 Section 8.3: Scientific contribution
 - [ ] Chapter 8 Section 8.4: Limitations and future work
 - [ ] Chapter 8 Section 8.5: Final reflections
@@ -160,11 +160,11 @@
 - [ ] Target: Chapter 8 complete (120+ lines)
 
 **Goal**: Conclusions chapter finished
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-### Sunday, January 26 (Day 14) - WEEK 2 CHECKPOINT
+### Thursday, January 29 (Day 14)
 - [ ] Review and expand Chapter 4 with final details
 - [ ] Ensure all methodology is reproducible
 - [ ] Add any statistical methods used
@@ -172,13 +172,13 @@
 - [ ] Fix any obvious issues
 
 **✅ WEEK 2 MILESTONE**: All core chapters complete (first draft)
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-## 📅 Week 3: January 27 - February 2 - POLISH & INTEGRATION
+## 📅 Week 3: January 30 - February 5 - POLISH & INTEGRATION
 
-### Monday, January 27 (Day 15)
+### Friday, January 30 (Day 15)
 - [ ] Review all citations in bibliografia.bib
 - [ ] Add missing references (Unity/Unreal docs, tools)
 - [ ] Verify citation format consistency
@@ -186,11 +186,11 @@
 - [ ] Add DOIs where available
 
 **Goal**: Bibliography complete and verified
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Tuesday, January 28 (Day 16)
+### Saturday, January 31 (Day 16)
 - [ ] Verify all figures are in tex/img/ directory
 - [ ] Check that all figures have proper captions
 - [ ] Ensure all tables have captions above them
@@ -198,11 +198,11 @@
 - [ ] Polish graph aesthetics (fonts, colors, labels)
 
 **Goal**: All figures and tables publication-ready
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Wednesday, January 29 (Day 17)
+### Sunday, February 01 (Day 17)
 - [ ] Create Appendix A: Interview question template
 - [ ] Create Appendix B: Detailed performance data tables
 - [ ] Create Appendix C: Test environment specifications
@@ -210,11 +210,11 @@
 - [ ] Update appendices list in main.tex
 
 **Goal**: Meaningful appendices created
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Thursday, January 30 (Day 18)
+### Monday, February 02 (Day 18)
 - [ ] Update list of figures (ensure auto-generated correctly)
 - [ ] Update list of tables
 - [ ] Update table of contents
@@ -226,7 +226,7 @@
 
 ---
 
-### Friday, January 31 (Day 19)
+### Tuesday, February 03 (Day 19)
 - [ ] Compile complete thesis (use Overleaf if local LaTeX issues)
 - [ ] Read entire thesis start to finish
 - [ ] Make notes of sections needing improvement
@@ -234,11 +234,11 @@
 - [ ] Create prioritized list of issues to fix
 
 **Goal**: Complete PDF generated, issue list created
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-### Saturday, February 1 (Day 20)
+### Wednesday, February 04 (Day 20)
 - [ ] Fix top 15 issues from review list
 - [ ] Improve transitions between chapters
 - [ ] Ensure terminology consistency
@@ -246,11 +246,11 @@
 - [ ] Polish abstract
 
 **Goal**: Major issues addressed
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-### Sunday, February 2 (Day 21) - WEEK 3 CHECKPOINT
+### Thursday, February 05 (Day 21)
 - [ ] Fix remaining issues from review list
 - [ ] Final polish pass on all chapters
 - [ ] Recompile thesis
@@ -258,13 +258,13 @@
 - [ ] Prepare to send to advisor
 
 **✅ WEEK 3 MILESTONE**: Complete, readable thesis ready for feedback
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-## 📅 Week 4: February 3-9 - FINAL POLISH & SUBMISSION
+## 📅 Week 4: February 6-15 - FINAL POLISH & SUBMISSION
 
-### Monday, February 3 (Day 22)
+### Friday, February 06 (Day 22)
 - [ ] Send thesis PDF to advisor (dr inż. Michał Chwesiuk)
 - [ ] Proofread abstract again (Polish)
 - [ ] Proofread abstract again (English)
@@ -272,11 +272,11 @@
 - [ ] Verify formatting against WUT requirements
 
 **Goal**: Thesis sent for review, self-review done
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Tuesday, February 4 (Day 23)
+### Saturday, February 07 (Day 23)
 - [ ] Continue proofreading (Chapters 1-3)
 - [ ] Check for typos and grammar errors
 - [ ] Verify technical terminology is correct
@@ -284,11 +284,11 @@
 - [ ] Wait for advisor feedback
 
 **Goal**: Thorough proofreading of early chapters
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Wednesday, February 5 (Day 24)
+### Sunday, February 08 (Day 24)
 - [ ] Incorporate advisor feedback (if received)
 - [ ] Continue proofreading (Chapters 4-6)
 - [ ] Check all code listings format correctly
@@ -296,11 +296,11 @@
 - [ ] Check footnotes
 
 **Goal**: Advisor feedback addressed, more proofreading
-**Target hours**: 4 hours
+**Target hours**: 8 hours
 
 ---
 
-### Thursday, February 6 (Day 25)
+### Monday, February 09 (Day 25)
 - [ ] Final proofreading (Chapters 7-8)
 - [ ] Check formatting requirements:
   - [ ] Margins correct
@@ -315,7 +315,7 @@
 
 ---
 
-### Friday, February 7 (Day 26)
+### Tuesday, February 10 (Day 26)
 - [ ] Compile final PDF
 - [ ] Verify all citations compile without errors
 - [ ] Check all figures render correctly
@@ -324,11 +324,11 @@
 - [ ] Run spell-check on English sections
 
 **Goal**: Final, clean PDF generated
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-### Saturday, February 8 (Day 27)
+### Wednesday, February 11 (Day 27)
 - [ ] Check WUT submission requirements (digital/print)
 - [ ] Print required number of copies (if needed)
 - [ ] Bind thesis at print shop (if needed)
@@ -336,11 +336,11 @@
 - [ ] Create backup of everything (thesis, source, data)
 
 **Goal**: Physical copies ready (if required)
-**Target hours**: 8 hours
+**Target hours**: 4 hours
 
 ---
 
-### Sunday, February 9 (Day 28) - BUFFER DAY
+### Thursday, February 12 (Day 28)
 - [ ] Final review of submission requirements
 - [ ] Prepare any additional documents needed
 - [ ] Triple-check deadline and submission process
@@ -348,11 +348,35 @@
 - [ ] Have submission checklist ready for tomorrow
 
 **Goal**: Ready for submission, peace of mind
+**Target hours**: 4 hours
+
+---
+
+### Friday, February 13 (Day 29)
+- [ ] Final review of submission requirements
+- [ ] Prepare any additional documents needed
+- [ ] Triple-check deadline and submission process
+- [ ] Have submission checklist ready
+- [ ] Prepare thesis files for upload
+
+**Goal**: All submission materials ready
 **Target hours**: 8 hours
 
 ---
 
-### Monday, February 10 (Day 29) - SUBMISSION DAY 🎯
+### Saturday, February 14 (Day 30)
+- [ ] Final final review of thesis PDF
+- [ ] Check all links and references work
+- [ ] Verify file sizes and formats
+- [ ] Test upload process if possible
+- [ ] Rest and prepare mentally
+
+**Goal**: Everything verified and ready
+**Target hours**: 8 hours
+
+---
+
+### Sunday, February 15 (Day 31) - SUBMISSION DAY 🎯
 - [ ] Submit thesis via required channels
 - [ ] Confirm submission received
 - [ ] Save confirmation email/receipt
diff --git a/DEADLINE_GAMEPLAN.md b/DEADLINE_GAMEPLAN.md
index 07a32f5..85fa360 100644
--- a/DEADLINE_GAMEPLAN.md
+++ b/DEADLINE_GAMEPLAN.md
@@ -1,5 +1,5 @@
 # Master's Thesis Completion Game Plan
-## Deadline: February 10, 2026 (29 days remaining as of January 12, 2026)
+## Deadline: February 15, 2026 (31 days remaining as of January 12, 2026)
 
 ---
 
@@ -31,10 +31,10 @@
 
 ## 🎯 Week-by-Week Game Plan
 
-### **Week 1: January 13-19 (Days 1-7)** - PERFORMANCE DATA COLLECTION
+### **Week 1: January 16-19 (Days 1-7)** - PERFORMANCE DATA COLLECTION
 **Goal**: Collect all performance metrics using NVIDIA Nsight
 
-#### **Monday-Tuesday, Jan 13-14** (Days 1-2): Nsight Setup & First Tests
+#### **Monday-Tuesday, Jan 16-14** (Days 1-2): Nsight Setup & First Tests
 - [ ] Install/verify NVIDIA Nsight Graphics on testing machine
 - [ ] Create standardized test scenarios for both Unity and Unreal games
 - [ ] Document hardware specifications and test environment
@@ -82,7 +82,7 @@
 
 ---
 
-### **Week 2: January 20-26 (Days 8-14)** - ANALYSIS & COMPARISON
+### **Week 2: January 23-29 (Days 8-14)** - ANALYSIS & COMPARISON
 **Goal**: Complete Chapters 6 and 7 with in-depth analysis
 
 #### **Monday-Tuesday, Jan 20-21** (Days 8-9): Capabilities Analysis (Chapter 6)
@@ -143,10 +143,10 @@
 
 ---
 
-### **Week 3: January 27 - February 2 (Days 15-21)** - POLISH & INTEGRATION
+### **Week 3: January 30 - February 5 (Days 15-21)** - POLISH & INTEGRATION
 **Goal**: Polish all chapters, add supporting materials, first full thesis review
 
-#### **Monday-Tuesday, Jan 27-28** (Days 15-16): Bibliography & Citations
+#### **Monday-Tuesday, Jan 30-28** (Days 15-16): Bibliography & Citations
 - [ ] Verify all citations in bibliografia.bib
 - [ ] Add missing references (especially for tools, Unity/Unreal documentation)
 - [ ] Ensure all figures and tables are cited in text
@@ -198,10 +198,10 @@
 
 ---
 
-### **Week 4: February 3-9 (Days 22-28)** - FINAL POLISH & SUBMISSION PREP
+### **Week 4: February 6-9 (Days 22-28)** - FINAL POLISH & SUBMISSION PREP
 **Goal**: Final refinements, proofreading, submission preparation
 
-#### **Monday-Tuesday, Feb 3-4** (Days 22-23): Advisor Review
+#### **Monday-Tuesday, Feb 6-4** (Days 22-23): Advisor Review
 - [ ] Send thesis to advisor (dr inż. Michał Chwesiuk)
 - [ ] While waiting, proofread abstract again
 - [ ] Check Polish language correctness (grammar, style)
@@ -254,7 +254,7 @@
 **Expected Output**:
 - Complete peace of mind
 
-#### **Monday, Feb 10** (Day 29): SUBMISSION DEADLINE
+#### **Monday, Feb 15** (Day 29): SUBMISSION DEADLINE
 - [ ] Submit thesis via required channels
 - [ ] Confirm receipt
 - [ ] Celebrate! 🎉
@@ -290,7 +290,7 @@
   - Mon-Thu: 4 hrs/day × 4 = 16 hours
   - Fri-Sat: 6 hrs/day × 2 = 12 hours
 
-**Total: 144 hours over 29 days (average 5.0 hrs/day)**
+**Total: 144 hours over 31 days (average 5.0 hrs/day)**
 
 ### Productivity Tips
 1. **Start each day by reviewing yesterday's progress**
@@ -310,7 +310,7 @@
 ### **Checkpoint 2: January 26** (End of Week 2)
 **Must have**: All core chapters (4-8) complete in first draft form
 
-### **Checkpoint 3: February 2** (End of Week 3)
+### **Checkpoint 3: February 5** (End of Week 3)
 **Must have**: Complete, reviewable thesis document
 
 ### **Checkpoint 4: February 9** (Day before deadline)
@@ -369,7 +369,7 @@ Tomorrow's priorities:
 
 ## 🎯 Success Criteria
 
-By February 10, you will have:
+By February 15, you will have:
 - ✅ A complete master's thesis (80-120 pages)
 - ✅ Original performance testing data comparing Unity and Unreal
 - ✅ 8 qualitative interviews analyzed
@@ -399,7 +399,7 @@ By February 10, you will have:
 - Interviews are done ✅
 - Most writing is drafted ✅
 
-The remaining 40% is systematic work that you can absolutely complete in 29 days if you:
+The remaining 40% is systematic work that you can absolutely complete in 31 days if you:
 - Follow this plan
 - Work consistently (not frantically)
 - Take care of yourself (sleep, food, breaks)
@@ -412,11 +412,11 @@ The remaining 40% is systematic work that you can absolutely complete in 29 days
 ## 📈 Visual Timeline
 
 ```
-Week 1 (Jan 13-19):  [████████░░░░░░░░] Performance Data Collection
-Week 2 (Jan 20-26):  [░░░░░░░░████████] Analysis & Comparison Writing  
-Week 3 (Jan 27-Feb2):[░░░░░░░░░░░░████] Polish & Integration
-Week 4 (Feb 3-9):    [░░░░░░░░░░░░░░██] Final Polish & Submission
-Feb 10:              [✓] SUBMIT!
+Week 1 (Jan 16-19):  [████████░░░░░░░░] Performance Data Collection
+Week 2 (Jan 23-29):  [░░░░░░░░████████] Analysis & Comparison Writing  
+Week 3 (Jan 30-Feb2):[░░░░░░░░░░░░████] Polish & Integration
+Week 4 (Feb 6-9):    [░░░░░░░░░░░░░░██] Final Polish & Submission
+Feb 15:              [✓] SUBMIT!
 ```
 
 ---
diff --git a/PLANNING_README.md b/PLANNING_README.md
index fcc6c55..3af6353 100644
--- a/PLANNING_README.md
+++ b/PLANNING_README.md
@@ -5,8 +5,8 @@
 **Faculty**: Electronics and Information Technology (EiTI)  
 **Thesis**: Comparison of performance and capabilities of modern computer game engines  
 **Advisor**: dr inż. Michał Chwesiuk  
-**Deadline**: February 10, 2026  
-**Days Remaining**: 29 days  
+**Deadline**: February 15, 2026  
+**Days Remaining**: 31 days  
 
 ---
 
@@ -38,7 +38,7 @@ This repository contains **6 comprehensive planning documents** to guide thesis
 **Purpose**: Day-by-day task breakdown  
 **When to use**: Check every morning  
 **Key content**:
-- Specific tasks for each of 29 days
+- Specific tasks for each of 31 days
 - Checkboxes for tracking completion
 - Daily hour targets
 - Next day priorities
@@ -58,7 +58,7 @@ This repository contains **6 comprehensive planning documents** to guide thesis
 **Purpose**: Daily progress tracking template  
 **When to use**: Fill out every evening  
 **Key content**:
-- Pre-filled log for all 29 days
+- Pre-filled log for all 31 days
 - Track hours, energy level, completions
 - Note blockers immediately
 - Plan tomorrow's top 3 priorities
@@ -69,7 +69,7 @@ This repository contains **6 comprehensive planning documents** to guide thesis
 **When to use**: Reference for big picture  
 **Key content**:
 - Week-by-week breakdown with goals
-- Total time commitment (144 hours over 29 days)
+- Total time commitment (144 hours over 31 days)
 - Risk mitigation strategies
 - Success criteria and checkpoints
 - Motivational content and tips
@@ -117,7 +117,7 @@ This repository contains **6 comprehensive planning documents** to guide thesis
 
 ```
 ┌───────────────────────────────────────────────────────────────┐
-│ Week 1 (Jan 13-19): PERFORMANCE DATA COLLECTION ⚡ CRITICAL   │
+│ Week 1 (Jan 16-19): PERFORMANCE DATA COLLECTION ⚡ CRITICAL   │
 ├───────────────────────────────────────────────────────────────┤
 │ • Install and use NVIDIA Nsight Graphics                     │
 │ • Run performance tests on Unity game (5-10 captures)        │
@@ -129,7 +129,7 @@ This repository contains **6 comprehensive planning documents** to guide thesis
 └───────────────────────────────────────────────────────────────┘
 
 ┌───────────────────────────────────────────────────────────────┐
-│ Week 2 (Jan 20-26): ANALYSIS & COMPARISON WRITING            │
+│ Week 2 (Jan 23-29): ANALYSIS & COMPARISON WRITING            │
 ├───────────────────────────────────────────────────────────────┤
 │ • Write Chapter 6: Capabilities (180+ lines)                 │
 │ • Write Chapter 7: Comparison (150+ lines)                   │
@@ -139,7 +139,7 @@ This repository contains **6 comprehensive planning documents** to guide thesis
 └───────────────────────────────────────────────────────────────┘
 
 ┌───────────────────────────────────────────────────────────────┐
-│ Week 3 (Jan 27-Feb 2): POLISH & INTEGRATION                  │
+│ Week 3 (Jan 30-Feb 5): POLISH & INTEGRATION                  │
 ├───────────────────────────────────────────────────────────────┤
 │ • Complete and verify bibliography                           │
 │ • Polish all figures and tables                              │
@@ -150,9 +150,9 @@ This repository contains **6 comprehensive planning documents** to guide thesis
 └───────────────────────────────────────────────────────────────┘
 
 ┌───────────────────────────────────────────────────────────────┐
-│ Week 4 (Feb 3-9): FINAL REVIEW & SUBMISSION                  │
+│ Week 4 (Feb 6-9): FINAL REVIEW & SUBMISSION                  │
 ├───────────────────────────────────────────────────────────────┤
-│ • Send to advisor (Feb 3)                                    │
+│ • Send to advisor (Feb 6)                                    │
 │ • Incorporate feedback                                       │
 │ • Final proofreading                                         │
 │ • Verify formatting                                          │
@@ -160,7 +160,7 @@ This repository contains **6 comprehensive planning documents** to guide thesis
 │ Target: 28 hours (4hrs Mon-Thu, 6hrs Fri-Sat)                │
 └───────────────────────────────────────────────────────────────┘
 
-🎯 Feb 10: SUBMIT THESIS!
+🎯 Feb 15: SUBMIT THESIS!
 ```
 
 ---
@@ -173,7 +173,7 @@ Without performance data from NVIDIA Nsight, there is no empirical thesis. Week
 ### 📊 Daily Consistency Beats Occasional Intensity
 - 4 hours/day on weekdays (Mon-Thu)
 - 8 hours/day on weekends (Fri-Sun)
-- Total: ~144 hours over 29 days (average 5.0 hrs/day)
+- Total: ~144 hours over 31 days (average 5.0 hrs/day)
 
 ### 📝 Use the Planning System
 - **Morning**: Check `DAILY_CHECKLIST.md` (3 min)
@@ -201,13 +201,13 @@ Without performance data from NVIDIA Nsight, there is no empirical thesis. Week
 - All core analysis and comparison written
 - Clear recommendations established
 
-**✅ Week 3 Success Criteria** (by Feb 2):
+**✅ Week 3 Success Criteria** (by Feb 5):
 - Complete thesis PDF compiled
 - Bibliography verified
 - Appendices created
 - Major issues identified and fixed
 
-**✅ Week 4 Success Criteria** (by Feb 10):
+**✅ Week 4 Success Criteria** (by Feb 15):
 - Advisor review completed
 - Final proofreading done
 - All formatting verified
@@ -233,7 +233,7 @@ Without performance data from NVIDIA Nsight, there is no empirical thesis. Week
 
 ## 📊 What You'll Produce
 
-By February 10, you will have created:
+By February 15, you will have created:
 
 ### Written Content:
 - 80-120 page master's thesis
@@ -274,7 +274,7 @@ By February 10, you will have created:
 
 1. **60% already complete** - Games built, interviews done, most chapters drafted
 2. **Clear plan** - Every day has specific, achievable tasks
-3. **Sufficient time** - 144 hours over 29 days is more than enough
+3. **Sufficient time** - 144 hours over 31 days is more than enough
 4. **Strong foundation** - Your research is solid, just needs final execution
 5. **Support system** - Advisor, planning docs, and your own determination
 
@@ -315,7 +315,7 @@ By February 10, you will have created:
 - Verify both games run correctly
 - Start Chapter 4 methodology section
 
-**TOMORROW** (Monday, Jan 13):
+**TOMORROW** (Monday, Jan 16):
 - Begin Week 1, Day 1 tasks from checklist
 - Run first Nsight captures
 - Continue Chapter 4 expansion
@@ -356,7 +356,7 @@ You have:
 - ✅ Completed interviews
 - ✅ Most chapters drafted
 - ✅ A clear, detailed plan
-- ✅ 29 days to execute
+- ✅ 31 days to execute
 
 What you need:
 - 🎯 Focus and consistency
@@ -364,7 +364,7 @@ What you need:
 - 📝 Follow the plan
 - 💪 Believe in yourself
 
-**On February 10, 2026, you will submit your master's thesis on time.**
+**On February 15, 2026, you will submit your master's thesis on time.**
 
 **Let's make it happen! 🚀**
 
diff --git a/PROGRESS_LOG.md b/PROGRESS_LOG.md
index d055521..f3736f5 100644
--- a/PROGRESS_LOG.md
+++ b/PROGRESS_LOG.md
@@ -1,7 +1,7 @@
 # Daily Progress Log - Master's Thesis
 
 **Start Date**: January 12, 2026
-**Deadline**: February 10, 2026
+**Deadline**: February 15, 2026
 **Days Remaining**: 29
 
 ---
@@ -15,7 +15,7 @@
 
 ---
 
-## Week 1: January 13-19 (Performance Data Collection)
+## Week 1: January 16-19 (Performance Data Collection)
 
 ### Sunday, January 12, 2026 (Pre-Week 1)
 **Hours worked**: _______
@@ -42,7 +42,7 @@
 
 ---
 
-### Monday, January 13, 2026 (Day 1)
+### Monday, January 16, 2026 (Day 1)
 **Hours worked**: _______
 **Energy level**: 😊 / 😐 / 😟
 
@@ -222,7 +222,7 @@ Major achievements:
 
 ---
 
-## Week 2: January 20-26 (Analysis & Comparison)
+## Week 2: January 23-29 (Analysis & Comparison)
 
 ### Monday, January 20, 2026 (Day 8)
 **Hours worked**: _______
@@ -402,9 +402,9 @@ Major achievements:
 
 ---
 
-## Week 3: January 27 - February 2 (Polish & Integration)
+## Week 3: January 30 - February 5 (Polish & Integration)
 
-### Monday, January 27, 2026 (Day 15)
+### Monday, January 30, 2026 (Day 15)
 **Hours worked**: _______
 **Energy level**: 😊 / 😐 / 😟
 
@@ -548,7 +548,7 @@ Major achievements:
 
 ---
 
-### Sunday, February 2, 2026 (Day 21) ✅ WEEK 3 CHECKPOINT
+### Sunday, February 5, 2026 (Day 21) ✅ WEEK 3 CHECKPOINT
 **Hours worked**: _______
 **Energy level**: 😊 / 😐 / 😟
 
@@ -582,9 +582,9 @@ Major achievements:
 
 ---
 
-## Week 4: February 3-9 (Final Polish & Submission)
+## Week 4: February 6-9 (Final Polish & Submission)
 
-### Monday, February 3, 2026 (Day 22)
+### Monday, February 6, 2026 (Day 22)
 **Hours worked**: _______
 **Energy level**: 😊 / 😐 / 😟
 
@@ -752,7 +752,7 @@ Major achievements:
 
 ---
 
-### Monday, February 10, 2026 (Day 29) 🎓 SUBMISSION DAY
+### Monday, February 15, 2026 (Day 29) 🎓 SUBMISSION DAY
 **Hours worked**: _______
 **Energy level**: 😊 / 😐 / 😟
 
diff --git a/README_START_HERE.md b/README_START_HERE.md
index 1496a7a..f8859fa 100644
--- a/README_START_HERE.md
+++ b/README_START_HERE.md
@@ -1,6 +1,6 @@
 # 🚀 QUICK START - Read This First!
 
-**Deadline**: February 10, 2026 (29 days from today, January 12)
+**Deadline**: February 15, 2026 (31 days from today, January 12)
 
 ---
 
@@ -29,7 +29,7 @@ You now have **3 comprehensive planning documents**. Here's how to use them:
 
 ## ⚡ START TODAY (Sunday, January 12)
 
-Even though the official "Day 1" is tomorrow (Monday, January 13), you can get a head start TODAY:
+Even though the official "Day 1" is tomorrow (Monday, January 16), you can get a head start TODAY:
 
 ### Today's Quick Wins (2-3 hours):
 - [ ] Read this entire quick start guide (5 min)
@@ -144,7 +144,7 @@ You should have:
 3. **Don't skip daily review** - Check DAILY_CHECKLIST.md every morning
 4. **Don't work 12+ hour days** - You'll burn out
 5. **Don't skip sleep/food** - Your brain needs fuel
-6. **Don't ignore advisor** - Send draft by Feb 3 at latest
+6. **Don't ignore advisor** - Send draft by Feb 6 at latest
 7. **Don't procrastinate Week 1** - It's the most critical
 
 ### ✅ DO:
@@ -264,7 +264,7 @@ dostępność materiałów edukacyjnych w języku polskim.
 - [ ] Verify Unity and Unreal games run
 - [ ] Start drafting Chapter 4 methodology section
 
-### Tomorrow (Monday, Jan 13) - Week 1, Day 1:
+### Tomorrow (Monday, Jan 16) - Week 1, Day 1:
 - [ ] Check DAILY_CHECKLIST.md morning
 - [ ] Open NVIDIA Nsight, familiarize with interface
 - [ ] Create test scenario document
@@ -311,7 +311,7 @@ Seriously, celebrate your progress! It helps motivation.
 
 ## 🔮 Final Thoughts
 
-**You can absolutely do this in 29 days.**
+**You can absolutely do this in 31 days.**
 
 You've already done 60% of the work:
 - ✅ Games are built
@@ -331,7 +331,7 @@ Each week has a clear goal. Each day has specific tasks. You just need to:
 3. Do the work
 
 **Consistency beats intensity.**
-5 hours average per day for 29 days = 144 hours of work
+5 hours average per day for 31 days = 144 hours of work
 That's MORE than enough to finish a master's thesis.
 
 ---
@@ -354,5 +354,5 @@ Before you close this document:
 ---
 
 *Last updated: January 12, 2026*
-*Days remaining: 29*
+*Days remaining: 31*
 *Let's make this happen!*
diff --git a/VISUAL_TRACKER.md b/VISUAL_TRACKER.md
index 6acd260..1242b4e 100644
--- a/VISUAL_TRACKER.md
+++ b/VISUAL_TRACKER.md
@@ -7,8 +7,8 @@
 ╚══════════════════════════════════════════════════════════════════════════════╝
 
 📅 Start Date:    January 12, 2026
-🎯 Deadline:      February 10, 2026
-⏰ Days Remaining: 29 days
+🎯 Deadline:      February 15, 2026
+⏰ Days Remaining: 31 days
 📈 Current Status: 60% Complete → Target: 100%
 ```
 
@@ -56,7 +56,7 @@ REMAINING WORK (40%):
 ```
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │                                                                             │
-│  WEEK 1: Jan 13-19        WEEK 2: Jan 20-26      WEEK 3: Jan 27-Feb 2      │
+│  WEEK 1: Jan 16-19        WEEK 2: Jan 23-29      WEEK 3: Jan 30-Feb 5      │
 │  ┌──────────────┐         ┌──────────────┐        ┌──────────────┐         │
 │  │ PERFORMANCE  │────────>│  ANALYSIS &  │───────>│   POLISH &   │────┐    │
 │  │     DATA     │         │  COMPARISON  │        │ INTEGRATION  │    │    │
@@ -64,7 +64,7 @@ REMAINING WORK (40%):
 │  └──────────────┘         └──────────────┘        └──────────────┘    │    │
 │       ⚡ CRITICAL!              ✍️ WRITE               🎨 POLISH       │    │
 │                                                                        │    │
-│  WEEK 4: Feb 3-9                                                       │    │
+│  WEEK 4: Feb 6-9                                                       │    │
 │  ┌──────────────┐                                                     │    │
 │  │    FINAL     │<────────────────────────────────────────────────────┘    │
 │  │   REVIEW &   │                                                          │
@@ -108,7 +108,7 @@ REMAINING WORK (40%):
 └──────────────────────────────────────────────────────────────┘
 
 ┌──────────────────────────────────────────────────────────────┐
-│ WEEK 3 CHECKPOINT - Sunday, Feb 2                            │
+│ WEEK 3 CHECKPOINT - Sunday, Feb 5                            │
 ├──────────────────────────────────────────────────────────────┤
 │ ☐ Bibliography complete and verified                        │
 │ ☐ All figures polished and in tex/img/                      │
@@ -123,9 +123,9 @@ REMAINING WORK (40%):
 └──────────────────────────────────────────────────────────────┘
 
 ┌──────────────────────────────────────────────────────────────┐
-│ WEEK 4 FINAL - Monday, Feb 10                                │
+│ WEEK 4 FINAL - Monday, Feb 15                                │
 ├──────────────────────────────────────────────────────────────┤
-│ ☐ Thesis sent to advisor by Feb 3                           │
+│ ☐ Thesis sent to advisor by Feb 6                           │
 │ ☐ Advisor feedback incorporated                             │
 │ ☐ Complete proofreading done (Polish + English)             │
 │ ☐ All formatting requirements verified                      │
@@ -141,35 +141,35 @@ REMAINING WORK (40%):
 ## 🎯 Daily Work Hour Targets
 
 ```
-Week 1 (Jan 13-19) - CRITICAL PERIOD
+Week 1 (Jan 16-19) - CRITICAL PERIOD
 ┌───┬───┬───┬───┬───┬───┬───┐
 │ M │ T │ W │ T │ F │ S │ S │
 ├───┼───┼───┼───┼───┼───┼───┤
 │ 4h│ 4h│ 4h│ 4h│ 8h│ 8h│ 8h│  Target: 40 hours
 └───┴───┴───┴───┴───┴───┴───┘
 
-Week 2 (Jan 20-26) - WRITING INTENSIVE
+Week 2 (Jan 23-29) - WRITING INTENSIVE
 ┌───┬───┬───┬───┬───┬───┬───┐
 │ M │ T │ W │ T │ F │ S │ S │
 ├───┼───┼───┼───┼───┼───┼───┤
 │ 4h│ 4h│ 4h│ 4h│ 8h│ 8h│ 8h│  Target: 40 hours
 └───┴───┴───┴───┴───┴───┴───┘
 
-Week 3 (Jan 27-Feb 2) - POLISH
+Week 3 (Jan 30-Feb 5) - POLISH
 ┌───┬───┬───┬───┬───┬───┬───┐
 │ M │ T │ W │ T │ F │ S │ S │
 ├───┼───┼───┼───┼───┼───┼───┤
 │ 4h│ 4h│ 4h│ 4h│ 8h│ 8h│ 4h│  Target: 36 hours
 └───┴───┴───┴───┴───┴───┴───┘
 
-Week 4 (Feb 3-9) - FINAL
+Week 4 (Feb 6-9) - FINAL
 ┌───┬───┬───┬───┬───┬───┬───┐
 │ M │ T │ W │ T │ F │ S │ S │
 ├───┼───┼───┼───┼───┼───┼───┤
 │ 4h│ 4h│ 4h│ 4h│ 6h│ 6h│ 0h│  Target: 28 hours
 └───┴───┴───┴───┴───┴───┴───┘
 
-Total target: 144 hours over 29 days
+Total target: 144 hours over 31 days
 Average: 5.0 hours/day
 ```
 
@@ -314,7 +314,7 @@ Average: 5.0 hours/day
 ## 🎯 Success Metrics
 
 ```
-By Feb 10, you will have:
+By Feb 15, you will have:
 ✅ Complete master's thesis (80-120 pages)
 ✅ Original performance data (Unity vs Unreal comparison)
 ✅ 8 qualitative interviews analyzed
diff --git a/scripts/README.md b/scripts/README.md
new file mode 100644
index 0000000..c4e34e3
--- /dev/null
+++ b/scripts/README.md
@@ -0,0 +1,129 @@
+# Scripts Directory
+
+This directory contains helper scripts for thesis work and data collection.
+
+---
+
+## Hardware Specs Script
+
+### `get_hardware_specs.sh`
+
+**Purpose**: Automatically retrieve hardware specifications and format them for LaTeX.
+
+**Usage**:
+```bash
+cd /home/runner/work/praca_magisterska/praca_magisterska/scripts
+./get_hardware_specs.sh
+```
+
+**Output**:
+- Creates `hardware_specs.tex` in the current directory
+- Contains LaTeX-formatted hardware information ready to copy into Chapter 4
+
+**What it captures**:
+- CPU model, cores, and threads
+- GPU model and memory (if NVIDIA GPU available)
+- RAM amount
+- Operating system and kernel version
+- Disk space
+
+**Next steps**:
+1. Run the script
+2. Review the generated `hardware_specs.tex` file
+3. Update Unity, Unreal Engine, and NVIDIA Nsight version numbers
+4. Copy the content to `latex/tex/4-metodologia.tex`
+
+---
+
+## Test Scenarios Document
+
+### `test_scenarios.md`
+
+**Purpose**: Comprehensive guide for performance testing methodology.
+
+**Contents**:
+- Detailed test scenarios (Low, Medium, High difficulty)
+- Performance metrics to capture
+- Step-by-step data collection procedure
+- Quality assurance checklist
+- Expected outputs and timeline
+
+**How to use**:
+1. Read through the entire document before starting tests
+2. Follow the procedure for each scenario
+3. Use as a checklist during testing
+4. Reference when writing Chapter 5 (Performance Tests)
+
+---
+
+## Unity Testing Helper
+
+### `run_unity_test.sh`
+
+**Purpose**: Interactive guide for running Unity performance tests with NVIDIA Nsight.
+
+**Usage**:
+```bash
+cd /home/runner/work/praca_magisterska/praca_magisterska/scripts
+./run_unity_test.sh
+```
+
+**Features**:
+- Interactive prompts for scenario selection (Low/Medium/High)
+- Pre-test checklist reminder
+- Timed prompts for frame captures at correct intervals
+- File naming conventions for organized data
+- Step-by-step guidance through the testing process
+
+**What it does**:
+1. Checks if NVIDIA Nsight is installed
+2. Prompts for scenario selection
+3. Guides through pre-test setup
+4. Provides timed reminders for 5 frame captures
+5. Reminds about exporting metrics and taking screenshots
+
+**Output organization**:
+- `unity_[scenario]_capture_[1-5].nsight` - Nsight capture files
+- `unity_[scenario]_capture_[1-5]_metrics.csv` - Exported metrics
+- `screenshots/unity/[scenario]/*.png` - Screenshots
+
+---
+
+## Creating Additional Scripts
+
+If you need to create more helper scripts, follow these conventions:
+
+1. **Naming**: Use lowercase with underscores (e.g., `analyze_results.sh`)
+2. **Permissions**: Make executable with `chmod +x script_name.sh`
+3. **Documentation**: Add a section to this README explaining the script
+4. **Error handling**: Include checks for required tools/files
+5. **Output**: Save generated files to appropriate directories
+
+---
+
+## Tips for Using Scripts
+
+1. **Run from repository root**: Most scripts assume you're in the main repository directory
+2. **Check dependencies**: Scripts may require `nvidia-smi`, `lscpu`, etc.
+3. **Review outputs**: Always review generated files before using them in the thesis
+4. **Customize as needed**: Scripts are templates - adjust for your specific setup
+
+---
+
+## Troubleshooting
+
+**"Command not found" errors**:
+- Ensure the script is executable: `chmod +x script_name.sh`
+- Run with explicit bash: `bash script_name.sh`
+
+**NVIDIA tools not found**:
+- Verify NVIDIA Nsight Graphics is installed
+- Add to PATH or use full path to executable
+
+**Permission denied**:
+- Scripts need execute permission: `chmod +x script_name.sh`
+- May need to run some system info commands with appropriate permissions
+
+---
+
+**Last updated**: January 14, 2026
diff --git a/scripts/get_hardware_specs.sh b/scripts/get_hardware_specs.sh
new file mode 100755
index 0000000..f80c449
--- /dev/null
+++ b/scripts/get_hardware_specs.sh
@@ -0,0 +1,108 @@
+#!/bin/bash
+# Script to retrieve hardware specifications and format for LaTeX
+
+echo "Gathering hardware specifications..."
+echo ""
+
+# Create output file
+OUTPUT_FILE="hardware_specs.tex"
+
+cat > "$OUTPUT_FILE" << 'LATEX_EOF'
+% Hardware Specifications for Thesis
+% Generated automatically - use in Chapter 4 Methodology
+
+\subsection{Środowisko testowe}
+\label{subsec:srodowisko-testowe}
+
+Wszystkie testy wydajnościowe przeprowadzono na komputerze o następującej specyfikacji:
+
+\begin{itemize}
+LATEX_EOF
+
+# Get CPU info
+echo "Retrieving CPU information..."
+CPU_MODEL=$(lscpu | grep "Model name" | cut -d':' -f2 | xargs)
+CPU_CORES=$(lscpu | grep "^CPU(s):" | cut -d':' -f2 | xargs)
+CPU_THREADS=$(lscpu | grep "Thread(s) per core" | cut -d':' -f2 | xargs)
+TOTAL_THREADS=$((CPU_CORES * CPU_THREADS))
+
+if [ -n "$CPU_MODEL" ]; then
+    echo "    \\item \\textbf{Procesor}: $CPU_MODEL ($CPU_CORES rdzeni, $TOTAL_THREADS wątków)" >> "$OUTPUT_FILE"
+fi
+
+# Get GPU info
+echo "Retrieving GPU information..."
+if command -v nvidia-smi &> /dev/null; then
+    GPU_MODEL=$(nvidia-smi --query-gpu=name --format=csv,noheader 2>/dev/null | head -1)
+    GPU_MEMORY=$(nvidia-smi --query-gpu=memory.total --format=csv,noheader,nounits 2>/dev/null | head -1)
+    DRIVER_VERSION=$(nvidia-smi --query-gpu=driver_version --format=csv,noheader 2>/dev/null | head -1)
+    
+    if [ -n "$GPU_MODEL" ]; then
+        echo "    \\item \\textbf{Karta graficzna}: NVIDIA $GPU_MODEL" >> "$OUTPUT_FILE"
+        if [ -n "$GPU_MEMORY" ]; then
+            GPU_MEMORY_GB=$((GPU_MEMORY / 1024))
+            echo "    \\item \\textbf{Pamięć GPU}: ${GPU_MEMORY_GB} GB GDDR" >> "$OUTPUT_FILE"
+        fi
+        if [ -n "$DRIVER_VERSION" ]; then
+            echo "    \\item \\textbf{Sterowniki NVIDIA}: wersja $DRIVER_VERSION" >> "$OUTPUT_FILE"
+        fi
+    fi
+else
+    echo "    \\item \\textbf{Karta graficzna}: [Uruchom skrypt z dostępem do nvidia-smi]" >> "$OUTPUT_FILE"
+fi
+
+# Get RAM info
+echo "Retrieving RAM information..."
+RAM_TOTAL=$(free -h | grep "Mem:" | awk '{print $2}')
+if [ -n "$RAM_TOTAL" ]; then
+    echo "    \\item \\textbf{Pamięć RAM}: $RAM_TOTAL" >> "$OUTPUT_FILE"
+fi
+
+# Get OS info
+echo "Retrieving OS information..."
+if [ -f /etc/os-release ]; then
+    OS_NAME=$(grep "^PRETTY_NAME=" /etc/os-release | cut -d'"' -f2)
+    KERNEL_VERSION=$(uname -r)
+    echo "    \\item \\textbf{System operacyjny}: $OS_NAME (jądro Linux $KERNEL_VERSION)" >> "$OUTPUT_FILE"
+fi
+
+# Get storage info
+echo "Retrieving storage information..."
+DISK_INFO=$(df -h / | tail -1 | awk '{print $2}')
+if [ -n "$DISK_INFO" ]; then
+    echo "    \\item \\textbf{Dysk}: $DISK_INFO całkowita pojemność" >> "$OUTPUT_FILE"
+fi
+
+# Close LaTeX itemize
+cat >> "$OUTPUT_FILE" << 'LATEX_EOF'
+\end{itemize}
+
+\subsubsection{Wersje oprogramowania}
+
+\begin{itemize}
+    \item \textbf{Unity}: [Wpisz wersję, np. 2022.3.15f1 LTS]
+    \item \textbf{Unreal Engine}: [Wpisz wersję, np. 5.3.2]
+    \item \textbf{NVIDIA Nsight Graphics}: [Wpisz wersję po instalacji]
+\end{itemize}
+
+\subsubsection{Konfiguracja testowa}
+
+Przed wykonaniem każdego testu:
+\begin{enumerate}
+    \item Zamknięto wszystkie aplikacje działające w tle
+    \item Wyłączono automatyczne aktualizacje systemu
+    \item Ustawiono tryb wydajności zasilania
+    \item Odczekano 5 minut na stabilizację systemu
+    \item Wykonano 3 pomiary dla każdego scenariusza testowego
+\end{enumerate}
+LATEX_EOF
+
+echo ""
+echo "✓ Hardware specifications saved to: $OUTPUT_FILE"
+echo ""
+echo "To use in your thesis:"
+echo "1. Review and update Unity/Unreal/Nsight versions"
+echo "2. Copy the content to latex/tex/4-metodologia.tex"
+echo "3. Adjust any details as needed"
+echo ""
+cat "$OUTPUT_FILE"
diff --git a/scripts/run_unity_test.sh b/scripts/run_unity_test.sh
new file mode 100755
index 0000000..26698d0
--- /dev/null
+++ b/scripts/run_unity_test.sh
@@ -0,0 +1,146 @@
+#!/bin/bash
+# Helper script to guide through Unity game testing with Nsight
+
+echo "======================================"
+echo "Unity Game + Nsight Testing Guide"
+echo "======================================"
+echo ""
+
+# Check if Nsight is installed
+if ! command -v nv-nsight-gfx &> /dev/null; then
+    echo "⚠️  NVIDIA Nsight Graphics not found in PATH"
+    echo ""
+    echo "To install:"
+    echo "1. Download from: https://developer.nvidia.com/nsight-graphics"
+    echo "2. Run the installer"
+    echo "3. Add to PATH or note installation directory"
+    echo ""
+    exit 1
+fi
+
+echo "✓ NVIDIA Nsight Graphics found"
+echo ""
+
+# Get scenario from user
+echo "Select test scenario:"
+echo "1) Low difficulty (50-100 bullets)"
+echo "2) Medium difficulty (200-300 bullets)"
+echo "3) High difficulty (500+ bullets)"
+read -p "Enter scenario number (1-3): " SCENARIO_NUM
+
+case $SCENARIO_NUM in
+    1)
+        SCENARIO="low"
+        SCENARIO_NAME="Low Difficulty"
+        ;;
+    2)
+        SCENARIO="medium"
+        SCENARIO_NAME="Medium Difficulty"
+        ;;
+    3)
+        SCENARIO="high"
+        SCENARIO_NAME="High Difficulty"
+        ;;
+    *)
+        echo "Invalid scenario number"
+        exit 1
+        ;;
+esac
+
+echo ""
+echo "Testing scenario: $SCENARIO_NAME"
+echo ""
+
+# Pre-test checklist
+echo "Pre-test checklist:"
+echo "- [ ] Close all background applications"
+echo "- [ ] Disable system updates"
+echo "- [ ] Set power mode to High Performance"
+echo "- [ ] Wait 5 minutes for system stabilization"
+echo ""
+read -p "Press Enter when ready to continue..."
+
+echo ""
+echo "Step 1: Launch Unity Game"
+echo "------------------------"
+echo "Navigate to the Unity bullet-hell game and launch it."
+echo "Select the '$SCENARIO_NAME' mode from the menu."
+echo ""
+read -p "Press Enter when Unity game is running..."
+
+echo ""
+echo "Step 2: Launch NVIDIA Nsight Graphics"
+echo "------------------------------------"
+echo "1. Open NVIDIA Nsight Graphics application"
+echo "2. Click 'Connect' or 'Attach to Process'"
+echo "3. Find the Unity process (usually 'Unity.exe' or similar)"
+echo "4. Click 'Attach'"
+echo ""
+read -p "Press Enter when Nsight is attached..."
+
+echo ""
+echo "Step 3: Start gameplay and capture frames"
+echo "----------------------------------------"
+echo "You will capture 5 frames at these time points:"
+echo "  - 5 seconds into gameplay"
+echo "  - 10 seconds into gameplay"
+echo "  - 15 seconds into gameplay"
+echo "  - 20 seconds into gameplay"
+echo "  - 25 seconds into gameplay"
+echo ""
+echo "For each capture:"
+echo "1. In Nsight, press F11 (or click 'Capture Frame')"
+echo "2. Save the capture with naming: unity_${SCENARIO}_capture_1.nsight"
+echo "   (increment number for each capture)"
+echo ""
+read -p "Press Enter to start timer..."
+
+# Timer for captures
+for i in {1..5}; do
+    TIME=$((i * 5))
+    echo ""
+    echo "Waiting for ${TIME} seconds..."
+    sleep 5
+    echo ">>> CAPTURE #${i} NOW! (Time: ${TIME}s) <<<"
+    echo "Press F11 in Nsight to capture"
+    echo "Save as: unity_${SCENARIO}_capture_${i}.nsight"
+    read -p "Press Enter when capture is saved..."
+done
+
+echo ""
+echo "Step 4: Export metrics"
+echo "---------------------"
+echo "In Nsight, for each capture:"
+echo "1. Open the capture file"
+echo "2. Go to GPU Trace or Performance view"
+echo "3. Export metrics to CSV"
+echo "4. Save as: unity_${SCENARIO}_capture_${i}_metrics.csv"
+echo ""
+read -p "Press Enter when exports are complete..."
+
+echo ""
+echo "Step 5: Take screenshots"
+echo "-----------------------"
+echo "Capture screenshots of:"
+echo "- GPU Timeline view"
+echo "- Memory analysis view"
+echo "- Any interesting performance bottlenecks"
+echo ""
+echo "Save screenshots to: screenshots/unity/${SCENARIO}/"
+echo ""
+read -p "Press Enter when screenshots are saved..."
+
+echo ""
+echo "✓ Testing complete for Unity - $SCENARIO_NAME"
+echo ""
+echo "Captured files:"
+echo "  - unity_${SCENARIO}_capture_1.nsight through unity_${SCENARIO}_capture_5.nsight"
+echo "  - unity_${SCENARIO}_capture_*_metrics.csv"
+echo "  - screenshots/unity/${SCENARIO}/*.png"
+echo ""
+echo "Next steps:"
+echo "1. Close Unity game"
+echo "2. Wait 2 minutes for system cooldown"
+echo "3. Run this script again or run: ./run_unreal_test.sh"
+echo "   to test the same scenario in Unreal Engine"
+echo ""
diff --git a/scripts/test_scenarios.md b/scripts/test_scenarios.md
new file mode 100644
index 0000000..2218101
--- /dev/null
+++ b/scripts/test_scenarios.md
@@ -0,0 +1,212 @@
+# Test Scenarios Document
+**Project**: Master's Thesis - Game Engine Performance Comparison  
+**Date**: January 16, 2026  
+**Author**: Krzysztof Rudnicki  
+
+---
+
+## Overview
+
+This document defines the test scenarios for comparing Unity and Unreal Engine performance using bullet-hell games and NVIDIA Nsight profiling.
+
+---
+
+## Test Hardware
+
+*[Auto-generated by running: `./scripts/get_hardware_specs.sh`]*
+
+- **CPU**: [Your CPU model]
+- **GPU**: [Your GPU model]
+- **RAM**: [Your RAM amount]
+- **OS**: [Your OS version]
+
+---
+
+## Test Methodology
+
+### Game: Bullet-Hell (Unity & Unreal implementations)
+
+Both games implement identical gameplay mechanics:
+- Player-controlled ship
+- Enemy spawning system with escalating difficulty
+- Bullet pattern generation
+- Collision detection
+- 90-second survival mode
+
+### Performance Metrics to Capture
+
+1. **Frame Time** (ms) - Time to render one frame
+2. **FPS** (frames per second) - Derived from frame time
+3. **GPU Utilization** (%) - Percentage of GPU capacity used
+4. **Memory Usage** (MB) - VRAM and system RAM consumption
+5. **Draw Calls** - Number of draw calls per frame
+6. **Vertex Count** - Total vertices rendered per frame
+
+---
+
+## Test Scenarios
+
+### Scenario 1: Low Difficulty (Baseline)
+**Objective**: Establish baseline performance with minimal load
+
+**Parameters**:
+- **Bullet count on screen**: 50-100 bullets
+- **Active enemies**: 2-3 enemies
+- **Duration**: 30 seconds of gameplay
+- **Captures**: 5 frame captures at different moments
+
+**Expected Outcomes**:
+- Stable frame rate (60 FPS target)
+- Low GPU utilization (<50%)
+- Minimal memory usage
+
+**Nsight Capture Points**:
+- 5 seconds into scenario
+- 10 seconds into scenario
+- 15 seconds into scenario
+- 20 seconds into scenario
+- 25 seconds into scenario
+
+---
+
+### Scenario 2: Medium Difficulty
+**Objective**: Test performance under moderate load
+
+**Parameters**:
+- **Bullet count on screen**: 200-300 bullets
+- **Active enemies**: 5-7 enemies
+- **Duration**: 30 seconds of gameplay
+- **Captures**: 5 frame captures at different moments
+
+**Expected Outcomes**:
+- Moderate GPU utilization (50-70%)
+- Frame rate may drop slightly
+- Increased memory usage
+
+**Nsight Capture Points**:
+- 5 seconds into scenario
+- 10 seconds into scenario
+- 15 seconds into scenario
+- 20 seconds into scenario
+- 25 seconds into scenario
+
+---
+
+### Scenario 3: High Difficulty (Stress Test)
+**Objective**: Test performance under maximum load
+
+**Parameters**:
+- **Bullet count on screen**: 500+ bullets
+- **Active enemies**: 10+ enemies
+- **Duration**: 30 seconds of gameplay
+- **Captures**: 5 frame captures at different moments
+
+**Expected Outcomes**:
+- High GPU utilization (>70%)
+- Potential frame drops
+- Maximum memory usage observed
+
+**Nsight Capture Points**:
+- 5 seconds into scenario (system stabilizing)
+- 10 seconds into scenario (peak load)
+- 15 seconds into scenario (sustained load)
+- 20 seconds into scenario (peak load)
+- 25 seconds into scenario (sustained load)
+
+---
+
+## Data Collection Procedure
+
+### For Each Scenario:
+
+1. **Pre-test Setup**:
+   - Close all background applications
+   - Disable system updates
+   - Set power mode to "High Performance"
+   - Wait 5 minutes for system stabilization
+   - Clear GPU/system caches
+
+2. **Unity Testing**:
+   - Launch Unity bullet-hell game
+   - Navigate to scenario (Low/Medium/High)
+   - Start NVIDIA Nsight Graphics
+   - Attach Nsight to Unity process
+   - Play scenario for 30 seconds
+   - Capture frames at designated time points (5 captures)
+   - Save capture data with naming: `unity_[scenario]_capture_[N].nsight`
+   - Export metrics to CSV: `unity_[scenario]_metrics.csv`
+
+3. **Unreal Testing**:
+   - Close Unity completely
+   - Wait 2 minutes for system cooldown
+   - Launch Unreal bullet-hell game
+   - Navigate to scenario (Low/Medium/High)
+   - Start NVIDIA Nsight Graphics
+   - Attach Nsight to Unreal process
+   - Play scenario for 30 seconds
+   - Capture frames at designated time points (5 captures)
+   - Save capture data with naming: `unreal_[scenario]_capture_[N].nsight`
+   - Export metrics to CSV: `unreal_[scenario]_metrics.csv`
+
+4. **Post-test Data Organization**:
+   - Organize captures in folders: `data/nsight/unity/` and `data/nsight/unreal/`
+   - Compile metrics into master spreadsheet: `performance_comparison.xlsx`
+   - Take screenshots of key Nsight analysis views
+   - Document any anomalies or issues observed
+
+---
+
+## Expected Data Outputs
+
+### Per Test Run (15 total: 3 scenarios × 5 captures):
+- Nsight capture file (.nsight)
+- Metrics CSV with frame time, FPS, GPU %, memory, draw calls, vertices
+- Screenshot of Nsight GPU trace
+- Screenshot of Nsight memory analysis
+
+### Aggregate Data:
+- Comparison table: Unity vs Unreal per scenario
+- Performance graphs showing all metrics
+- Statistical analysis (mean, std dev, min, max)
+
+---
+
+## Quality Assurance
+
+### Validation Checks:
+- [ ] All scenarios tested in both engines
+- [ ] 5 captures per scenario completed
+- [ ] All CSV metrics exported
+- [ ] Screenshots saved for all captures
+- [ ] Data organized in proper folder structure
+- [ ] No system crashes or anomalies during testing
+- [ ] Comparable conditions between Unity and Unreal runs
+
+### Data Integrity:
+- [ ] Frame times make sense (>0ms, <100ms typically)
+- [ ] GPU utilization in valid range (0-100%)
+- [ ] Memory values reasonable for game scope
+- [ ] No obvious outliers without explanation
+
+---
+
+## Timeline
+
+- **Day 1 (Thursday, Jan 16)**: Setup Nsight, run Scenario 1 on both engines
+- **Day 2 (Friday, Jan 17)**: Run Scenario 2 on both engines
+- **Day 3 (Saturday, Jan 18)**: Run Scenario 3 on both engines
+- **Day 4 (Sunday, Jan 19)**: Verify data, re-run any problematic captures, organize data
+
+---
+
+## Notes
+
+- If a capture fails, note the reason and retry
+- Document any differences in how scenarios are triggered in Unity vs Unreal
+- Pay attention to engine-specific optimizations that may affect results
+- Consider recording video of test runs for reference
+
+---
+
+**Status**: Ready for execution  
+**Next Action**: Run `./scripts/get_hardware_specs.sh` to generate hardware specs for Chapter 4