# \[FMOD\] FMOD\_CHECKATTRIBUTES : Position vector goes infinite
**URL:** https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453
**Category:** FMOD Studio
**Created:** [December 25, 2024, 5:59pm UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453 "2024-12-25T17:59:19Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@Johanenglund](https://qa.fmod.com/u/Johanenglund)
#### Post date: [December 25, 2024, 5:59pm UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453/1 "2024-12-25T17:59:19Z")
Just starting to appear… I checked the referenced script, turned off the 3D settings just to have another event crop up… I disable that event… and then… und so weiter… The project is set to 7.1.4 and it’s Unity 6., latest FMOD update.
[FMOD] FMOD\_CHECKATTRIBUTES : Position vector { 1e+18, 1e+18, 1e+18 } is out of range.
UnityEngine.Debug:LogWarning (object)
FMODUnity.RuntimeUtils:DebugLogWarning (string) (at Assets/Plugins/FMOD/src/RuntimeUtils.cs:578)
FMODUnity.RuntimeManager:DEBUG\_CALLBACK (FMOD.DEBUG\_FLAGS,intptr,int,intptr,intptr) (at Assets/Plugins/FMOD/src/RuntimeManager.cs:108)
FMOD.Studio.EventInstance:set3DAttributes (FMOD.ATTRIBUTES\_3D) (at Assets/Plugins/FMOD/src/fmod\_studio.cs:1337)
FMODUnity.RuntimeManager:CreateInstance (FMOD.GUID) (at Assets/Plugins/FMOD/src/RuntimeManager.cs:1223)
FMODUnity.RuntimeManager:CreateInstance (FMODUnity.EventReference) (at Assets/Plugins/FMOD/src/RuntimeManager.cs:1190)
FMOD\_WaterDrop:OnTriggerEnter (UnityEngine.Collider) (at Assets/FMOD\_WaterDrop.cs:25)
---
### Author:  [@Andrew](https://qa.fmod.com/u/Andrew)
#### Post date: [December 26, 2024, 9:44pm UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453/2 "2024-12-26T21:44:05Z")
We recently added warnings (only in logging mode) for numbers which are out of range. Is it possible for you to clamp the values you’re sending to FMOD so they’re not out of range?
---
### Author:  [@RevenantX](https://qa.fmod.com/u/RevenantX)
#### Post date: [December 29, 2024, 12:19pm UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453/3 "2024-12-29T12:19:06Z")
Same warning after latest update (2.02.26). This is inside FMOD code
---
### Author:  [@Andrew](https://qa.fmod.com/u/Andrew)
#### Post date: [December 29, 2024, 11:26pm UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453/4 "2024-12-29T23:26:21Z")
Ah, of course, a position of 1e+18, 1e+18, 1e+18 means you haven’t called set3DAttributes on your event instance yet. Do you call set3DAttributes on your event instance immediately after creating it as specified in the docs here?
[https://www.fmod.com/docs/2.03/unity/api-runtimemanager.html#createinstance](https://www.fmod.com/docs/2.03/unity/api-runtimemanager.html#createinstance)
---
### Author:  [@RevenantX](https://qa.fmod.com/u/RevenantX)
#### Post date: [December 30, 2024, 12:19am UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453/5 "2024-12-30T00:19:05Z")
Problem that this warning shows in CreateInstance. surely i call set3dattributes after CreateInstance.
Look at attached callstack it shows problem directly
---
### Author:  [@Andrew](https://qa.fmod.com/u/Andrew)
#### Post date: [December 30, 2024, 3:02am UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453/6 "2024-12-30T03:02:22Z")
Oh, I see. Yes, that appears to be a problem on our end. Can you try this workaround please? Edit Assets\Plugins\FMOD\src\RuntimeManager.cs and change every instance of 1e+18F to be 1e+17F instead. There should be 7 places you need to make that change. Does that suppress the warning spam?
---
### Author:  [@RevenantX](https://qa.fmod.com/u/RevenantX)
#### Post date: [January 2, 2025, 2:49pm UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453/7 "2025-01-02T14:49:57Z")
Yes
---
### Author:  [@Johanenglund](https://qa.fmod.com/u/Johanenglund)
#### Post date: [January 2, 2025, 7:33pm UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453/8 "2025-01-02T19:33:11Z")
> [@Andrew](#):
>
> 1e+18F -\>17F
Thanks Andrew! This seems to indeed have solved the issue. I’ll not mark this as solved just yet though, as I’ve only had time to test this very briefly. However, if @RevenantX finds that this fixes it for them also I’d suggest changing this to solved.
---
### Author:  [@Andrew](https://qa.fmod.com/u/Andrew)
#### Post date: [January 6, 2025, 12:15am UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453/9 "2025-01-06T00:15:50Z")
Good to hear the workaround is working for you. We’ll fix it in our next release.
---
### Author:  [@zicovsky](https://qa.fmod.com/u/zicovsky)
#### Post date: [January 21, 2025, 2:51am UTC](https://qa.fmod.com/t/fmod-fmod-checkattributes-position-vector-goes-infinite/22453/10 "2025-01-21T02:51:20Z")
Thank you for this workaround fix. This error was driving me insane. I spent countless hours trying to figure out what was out of range. I’m glad I decided to look it up online and found this thread.
I applied the fix to my FMOD source files and it also fixed it.