You ever look into the distance, and think there's something... missing?
This mod aims to add a Heat Haze-like effect into New Vegas. Honestly it's a bare-bones implementation, but an implementation nonetheless (the effect isn't scientifically correct in the slightest)
This took HEAVY inspiration from doodlum's Heat Haze mod, and has been expanded with a new meshe, texture, configuration options, and logic to match more realistic depictions of the effect.
The main goal of this was following the ESP-less trend of converting a mod; since I'm all for FOSS.
Plus i wanted to try my hand at New Vegas-specific modding for the first time that wasn't just "resolve X to work with Y" in FNVEdit.
- ESP-less implementation of a distance Heat Shimmer effect.
- Custom (albeit simple) mesh for displaying the haze effect (literally just a cylinder with custom textures).
- Configurable through MCM Extender (optional) or the INI:
- Distance (50-100m distances)
- Start / end times and the fade length in / out
- Speed of the effect (0.5x to 2.5x)
- Fallout 3 areas (Experimental, not fully tested)
- Debug options: Wireframe to show the distance, an Intensity Multiplier, and All Weathers / All Times to ignore the weather or time of day.
- TTW Compatible for the most part
- Draws a tall cylinder around the player
- Display the refraction texture effect on that cylinder
- Fades the effect at the start of the day, and out at the end.
- NVSE
- JIP LN NVSE
- Climate Control NVSE
- (Optional) MCM Extender
- Download the mod file on NexusMods
- Install using Vortex / MO2
- (Optional) download the .ini file as well so updating doesn't override it (don't merge the 2 mods when installing).
100% NOT COMPATIBLE WITH Heat Haze, this mod is doing similar to what that one does.
I have tested this specifically with the following mods, and it seems ok:
- NVR
- Desert Natural Weathers TTW I'm not 100% sure what will break this mod though... Maybe ENB?
Should work with any weather options that have been tagged as pleasant / don't have a wind value higher than 0.5
I'm not going to deny the usage of AI for working on this; although I wouldn't consider the project to be "one-shot" / "Vibe Coded" by a long stretch. I'd say collaborative rather than me acting as a manager (i'd like to think at least). AI isn't perfect, so it's been used more as a colaborative tool rather than a minion to do my bidding. I haven't committed anything that I blindly implemented or not understood.
I've been testing this on every commit; making sure it's still working as expected.
Ai was used in the following ways:
- Helping me find resources to port the logic over / researching how NVSE plugins are implemented
- Correcting my mistakes in implementation (i.e. reference fixes, reviewing, looking for anything specifically GECK/NVSE related that I didn't necessarily realise) + debugging nuances & figuring out engine quirks
- Helping me update / modify the Blender niftools addon to work with recent versions of Blender.
- Generating the GitHub release scripts /
build.pyscript
Model used: Claude Opus 5.5 (Formerly GPT-6.1 Sol)