Cracking problem dd1
Hello everyone. I have a problem with my dd1. I have a crack in the base that comes into play. I had already had this problem at the beginning when my base was new. I had made a sav, base repaired but after three months my problem comes back. Does anyone have any idea of the problem? Thank you
Comments
yeah, but exact same issue caused also by firmware/software, i already reported kind off what may cause this
Hi. Okay, do you have a link from your post?
no, i talked about this with fanatec directly
i not know if that is exact same like yours, but it is very similar
also i not know how long it may take this fix for them, as i reported that kind off lately
Fanatec had changed my engine the first time apparently. That's what they told me anyway. I remade a ticket at fanatec but I don't want to do a sav every three months frankly. What did they tell you fanatec about this problem?
like i tell i not know if that is exact same issue but it looks very similar.
OK, thanks to you
does that thing happens with you all the time ? even when you not play?
Hi. When the base is turned on you feel like a bad interpolation of the magnets or something like that. But it's in games that I have this noise and crackling.
yeah, that might be the one what been talked with the Marcel Pfister privately
i not know when they fix this, but there exist this problem , some call this also like Sand is in base self
When I received my dd1 database three months ago, the base already had this problem at the beginning. The sav took it back from me and confirmed a problem. I wasn't too much explained to the repair but as long as it works I don't care. Except that three me after that starts again. I really hope they will solve the problem. I really like the fanatec ecosystem (I have the Porsche hub and the m4 gt3 wheel that I really love) but if they are not able to run my dd1 base properly I will definitely go elsewhere.
there is thing does this happens with all the games all the time ?
because by default it should not happen with every game.
I mainly play two games, and on these two games, I noticed this problem. But anyway, this is not normal. I had a csl dd before and no problem, I didn't think I was so bothered by passing on a podium basis. I'm really disgusted.
i to know that this issue exist, because some off the games what i play makes same thing, and no its not the game fault
Yes, I know it's not the fault of the game. What I wanted to say is that this thing amplifies when I'm in games. I hope that fanatec will change my dd1, I don't want to do a sav every three months, especially with this kind of equipment.
you stuff is not accurate tho, because something like this i seen also with my DD2 and with my csl dd i really doubt is base self fault
Wow that is a really bad sounding DD1, I would definitely want that fixed / replaced if it was mine doing that, the only time my DD1 sounded anything like that (Like gritty sand in motor) was with the settings in Fanatec Tuning menu being (FFB=70-100, INT=0, FEI=100 and FFS=Peak) and / or too much gain in game (Self aligning torque or Gain = 100), and only when racing in game, never just powered on with no game running.
Can't see any software or FW updates fixing that issue, as it isn't normal and as you said it was diagnosed by Fanatec and corrected previously as a fault and that you couldn't reproduce the problem with another CSL DD base setup.
This is a copy of my settings I run with most of my racing Games (Grid, Grid Autosport, Grid Legends, Dirt2, Dirt3, Dirt4, Dirt Rally, Dirt Rally 2, WRC7, WRC9, AC, ACC, etc). (FFB=65, FFS=Linear, NDP=25%, NFR=10%, NIN=0%, INT=1, FEI=100, FOR=100, SPR=100, DPR=100). Game gain = 50 - 65.
Yet the last time the base did this to me and fanatec took it to me in sav, she had a problem apparently.
Hi. Thank you for your feedback and your screenshot. I don't play with extreme parameters. I have been playing since the return of sav with the same parameters. The problem came back overnight like that after three months.
well, it could be at some cases the base self, but i know also how trigger that with my directx test app so for me it looks more like software issue