gjf

I am pretty surprised that somebody (even with "developer" title) has experienced problems with FSD. I have used it more than 3 years and it is the first crash I have observed. And I have only one non-working feature - it is a weather, that doesn't work for well known reason. But maybe it is because I am the user, not coder or developer, and I enjoy a good interface and all good working features without trying to build some plugins to perform a flight to the Moon or learn how to code Lua scripts. Whatever, I am only user, and I love a good stuff like Fsd was, and I am not experienced enough to patch xex or build my own server. Yeah, nobody promised me jqe360.com will work forever and I didn't pay a cent for this - but when good coder decided to discontinue his product he usually makes it working - but without recent features those new product has. In our case we have problems with Fsd that can't be easily disabled - and Aurora that possibly (possibly!) will be better than Fsd, but lacks it's simple features at the present time. You think I am wrong? Just test how many requests are made on jqe360.com from Fsd and compare with Aurora ones. I believe Fed's are more. Now we have two products: the stable and very popular, but broken with latest server changes - and the one on beta stage. Is it a good move for developing process? I don't know, I am a simple user, but frankly speaking - I don't think so. Just to compare: Microsoft discontinued XP a long time ago, but they didn't broke it (they even made it free). As for smb-client - maybe I was wrong in terms. In Fsd I have a simple smb: folder in explorer so I can easily browse my router share (as well as shares of all PCs in my home network. There is no such feature in Aurora 0.6b, and I'll be honest - this is the main reason why I don't like Aurora. Yeah, maybe some latest version exists - one experienced guy in this thread recommended me to use Aurora 6.0b, but I didn't find it and I can't test this feature on it.

Damn, it's quite tricky way to push users to Aurora. One can either use FSD with flooding error logs (any way to disable it cause the error itself doesn't influence on the work?) or use beta of Aurora. Yes, it is not so bad, but I miss a user-friendly menu with separate games and apps, I really miss a normal smb-client so I can copy games from my router share (connectx does not support unicode symbols in folder names and quite unstable when copying in Aurora explorer). Damn it, really it is a bad move.

Just as I said before: it is clearly server-based error. I understand they changing servers for Aurora, but why it is necessary to break all good working FSD?

The logs are attached. Disabling plugins did not help. Logs.zip

Guys, I have Aurora installed, OK? I don't like it. Very poor interface in comparison with FSD, buggy downloading of covers - I. DON'T. LIKE. IT! If you have something to say on topic - I'd be happy. If not - please shut up. Thank you.

I love when newbies post some bullshit, but the problem was found. The constant connection is linking with 192.99.14.39 which is jqe360.com. I am pretty sure it is server-based issue.

Why should I move from stable and time-tested product to beta? I will think after official release without "b" in the name and without a number of bugs reported on this forum. Please don't flood with your stupid advertisement if you have nothing to tell on topic.

Update: the error exists only when network is connected. Also I constantly see "HTTP: 1 items left (0.00 kBps)". Looks like Xbox is trying to download something but with no success. How to stop it?

Hi All! I need a help with FSD. Starting today every time FSD boots it shows: "F3 Crash. Freestyle 3 crashed, what would you like to do? Restart F3 / Go back to NXE / Try to continue" When trying to restart the same error appears. I can "try to continue" and everything works, but the error appears again when moving in "Main settings" menu item. Xbox was not in use last month and everything was OK before. The only change was a IP range in router - it was 192.168.1.xx before and 192.168.111.xx now. What is the source of this problem and how to repair it without serious reinstalling everything in my Xbox?

Everyone can forget (at least - for now) about Weather in FSD. Yes, there is an updated unofficial rev.783 that supports APIv2, but WorldWeatherOnline stopped providing free keys and starts providing 2-months trial premium keys. The algorithm is different and premium does not work as free ones. So if you have old free key - you can use it at least till they will be obsolete at all. If you haven't - forget about the weather.

As for new APIv2 key support. Actually it works - but it doesn't. Possibly WorldWeatherOnline changed something - because I can see requests with my api key on their website - but I cannot find any city in FSD settings. Yeah, I could revert to 775 and use famous APIv1 keys, but actually TU improvement are better than weather So finally it should be said weather is not working in 783.

What is the second "default.rar" file with default.xex dated Nov 11, 2015 in the first post?

gavin_darkglider, Not exactly. Actually at dualnand it is not necessary (as I found during my own update) to update avatars at freeboot mode as they updates during retail mode update

felida, the reason was I didn't find a tutorial here exactly for dualnand. Swizzy, thanks, everything is OK, case's closed.

Dear guys, I am a user of dualnand Trinity. Now I would like to update the dash. I am using the tutorial that is here: http://www.xpgamesaves.com/threads/how-to-support-dual-nand-users-dashboard-17150-and-future-updates.119840/ So I have dumped the nand in freeboot mode using Simple 360 NAND Flasher by Swizzy v1.3 (please see the logs attached) and then transfer it on PC into xeBuild_GUI_2.098. All constants was loaded via Ethernet (Xbox was in Xell mode). Please see the screen attached. After that I have converted the dump into the new one using new 17511 kernel (please see logs attached). Are the following steps correct and will not lead to some troubles (banning in Live, breaking freeboot and/or retail mode, losing some features, problems with DVD etc): 1. Place the new udpflash.bin file at FAT32 formated empty USN stick. 2. Insert it into Xbox and boot it into Xell mode (the dualnand should be set in freeboot mode). Wait until reboot. 3. Power off the Xbox, then switch dualnand into retail mode, then power on. 4. Update the dash via Internet. Actually this is what was placed at initial tutorial, but I am afraid a little bit with numerous complains in Internet after updating dualnand. Simple 360 NAND Flasher 1.3b.log.zip xeBuild_GUI.zip