The TORCS Racing Board
Username: Password: Remember Me?
Lost Password Register
Author: firechief | Created: 2017-08-22 03:14:04
Subject: Mouse_2017 compile error
Visual Studio 2013 objects to line 35 in GenericAvoidance.cpp, with the error "operator =" is ambiguous

target = (avoid & Opponent::F_LEFT) ? 1 : -1;

target being a Vec2d - at a guess, I don't think it likes being assigned an integer value.
Last Edited: 2017-08-22 03:14:04 by firechief
    Author: phi | Created: 2017-08-22 03:36:41
    Subject: Re: Mouse_2017 compile error
    I do not have GenericAvoidance.cpp but rather Avoidance.cpp. In this file appears on lines 26, 75 and 82:

    target.x = (avoid & Opponent::F_LEFT) ? 1 : -1;
    Last Edited: 2017-08-22 03:36:41 by phi
      Author: firechief | Created: 2017-08-22 03:48:11
      Subject: Re: Mouse_2017 compile error
      Ah - my mistake! Thought I'd updated it properly but I hadn't. Nevermind :)
      Last Edited: 2017-08-22 03:48:11 by firechief
        Author: timfoden | Created: 2017-08-22 07:37:57
        Subject: Re: Mouse_2017 compile error
        Glad you got that sorted out :)

        However I've just compiled all the bots and run the qually, and my bots seem to be running far slower than I expected... So yes, I can't even get my own bots to work! :)

        Don't know yet what I've broken. Is it the same for you?
        Last Edited: 2017-08-22 07:37:57 by timfoden
          Author: firechief | Created: 2017-08-22 07:49:56
          Subject: Re: Mouse_2017 compile error
          Mouse seems pretty good (though obviously I don't know what your target laptimes were), but Tiger is uncharacteristically slow - enough so that I had to triple-check that I've installed everything correctly!

          Please let us know if you find what the mistake was. People were kind enough to forgive my pit-testing error on Hidden Valley, if its a simple error I'm sure it wouldn't be a problem including a fix. I know I'd prefer to see the most closely-contested race possible.
          Last Edited: 2017-08-22 07:50:58 by firechief
            Author: timfoden | Created: 2017-08-22 08:36:35
            Subject: Re: Mouse_2017 compile error
            That's wierd... for me both Tiger and Mouse were way too slow. But for you Mouse seems OK and Tiger is slow. From the slow times I got here, and the fast times I expect, I image that for you Tiger is about 7 or 8 seconds per lap slower than Mouse. I'd normally expect Tiger to be slightly faster than Mouse with correct setup.

            I only had a small amount of time to try to figure this out before I left for work this morning, but managed to run a debug version and check that the setups were actually being loaded. Also diffed the setups against my development versions and they looked OK. Still scratching my head on this one. I'll continue to look at it when I get home this evening.
            Last Edited: 2017-08-22 08:36:35 by timfoden
              Author: firechief | Created: 2017-08-22 08:42:48
              Subject: Re: Mouse_2017 compile error
              > I image that for you Tiger is about 7 or 8 seconds per lap slower than Mouse. I'd normally expect Tiger to be slightly faster than Mouse with correct setup.

              Yes, that was approximately the difference I saw, and yes, I'd expect Tiger to be quicker than Mouse as he's driving a quicker car.

              Hope you find the solution!
              Last Edited: 2017-08-22 08:42:48 by firechief
          Author: dummy | Created: 2017-08-22 09:57:47
          Subject: Re: Mouse_2017 compile error
          Same for me. Both teams are way of pace. I hope you can fix it. I really want to see the normal race.

          This could have happened to me as well. I just finished an acceptable performance for my teams 10 min before the deadline. This track was a much bigger challenge than I first thought.
          Last Edited: 2017-08-22 09:57:47 by dummy