November 7, 201213 yr This error has started to occur every time I start up FSX. https://www.dropbox.com/sh/afu7lqsyujql06g/6UD7aQg2k8 It happens even when starting with default scenery. Any feedback much appreciated. Thanks Joaquin Blanco Intel Core i9-9900K at 5Ghz, Corsair Hydro H100i RGB PLATINUM CPU cooler, Asus ROG STRIX Z390-E,Motherboard, NVIDIA GeForce RTX 2080 Super 8GB GDDR6, G.Skill Trident Z RGB 32GB DDR4 3200MHz Memory, 500GB Samsung 970 EVO PLUS M.2 PCIe,2TB Samsung 860 QVO Solid State Drive, 2TB, 2 x Samsung 860 Evo 2TB, 1 x 1TB Samsung 860 Evo, Corsair RM650x 80 PLUS Gold 650W PSU.
November 7, 201213 yr Commercial Member Have you played with any of the .fx in the effects folder lately? I've seen that, it's very foggy, but I think it has to do with Lifetime=X.XX, X.XX and the error occurs when the first X.XX is a larger number than the second - or vice versa - can't remember. EDIT: Correction, this error appears to be associated with "Delay=X.XX, X.XX" and occurs when the first X.XX is a larger number than the second. Jim
November 7, 201213 yr The error says 1.0 is larger than 1000000000.0, which is odd until you consider that a number that big will probably end up as a negative number in the game. Don't need a delay of a billion no matter what. Make the number smaller and see if that helps. Hook Larry Hookins Oh! I have slipped the surly bonds of EarthAnd danced the skies on laughter-silvered wings;
November 7, 201213 yr Commercial Member The error says 1.0 is larger than 1000000000.0, which is odd until you consider that a number that big will probably end up as a negative number in the game. Don't need a delay of a billion no matter what. Make the number smaller and see if that helps. Hook I noticed that too, I'll venture a wild a$$ guess that 1000000000.0 is just (far) beyond the acceptable range and therefore the sim sees it as zero. Actually one hundred million is enough to make the sim throw that error. "The length of delay before the emitter begins emitting particles. Measured in seconds." says the SDK. One hundred million seconds is over 3 years, it'd take a pretty long flight to see those particles show up! :smile: Jim
November 7, 201213 yr Author Thank you guys.... it was an fx file. I installed a new scenery yesterday which had some fx files. After checking them all, noticed there were 2 files with similar names SBRFlamps0.fx & SBRFlamps0_.fx, - removed the first one and the error no longer there. What a relief! Never saw this error before and it never occurred to me an fx file could be the culprit. Regards Joaquin Blanco Intel Core i9-9900K at 5Ghz, Corsair Hydro H100i RGB PLATINUM CPU cooler, Asus ROG STRIX Z390-E,Motherboard, NVIDIA GeForce RTX 2080 Super 8GB GDDR6, G.Skill Trident Z RGB 32GB DDR4 3200MHz Memory, 500GB Samsung 970 EVO PLUS M.2 PCIe,2TB Samsung 860 QVO Solid State Drive, 2TB, 2 x Samsung 860 Evo 2TB, 1 x 1TB Samsung 860 Evo, Corsair RM650x 80 PLUS Gold 650W PSU.
November 7, 201213 yr You probably want to keep both files. You can edit them with notepad. Easiest way is to open an empty notpad and drag the file onto it. Hook Larry Hookins Oh! I have slipped the surly bonds of EarthAnd danced the skies on laughter-silvered wings;
Create an account or sign in to comment