a lot of problems..?

Home Forums AR Sandbox Forum a lot of problems..?

Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #124954
    s.bosschaart
    Participant

    Hi all,

    This project is a test project for us. We’re building this for the lessons geography.

    But i encounter some problems..
    When i run the sandbox, it goes all black.. i tried everything.
    It is inverted, and when i change the coordinates it still goes to black.
    i don’t know what kind of information i need to give, i will be active on the forum to react asap.

    (Located in The Netherlands, so timezones may vary on when i answer.)

    Kind Regards,

    Sebastiaan Bosschaart

    #124955
    ajy00
    Participant

    Hi

    Can you share your BoxLayout.txt file as that seems to be a common issue for this problem..

    Al

    #124959
    s.bosschaart
    Participant

    Hi there,

    I will share the file when the laptop is back from RMA.
    I was trying to see if the problem was the Kinect (v2 1520), so i switched it with a Kinect V1 1414, and then the laptop crashed and would not reboot..
    The warranty was until the 5th of December so i was lucky there.

    You will hear from me asap.

    Kind Regards

    #124978
    dantep
    Participant

    Hello,

    I am having the same problem with the inverted coloring of the sandbox. I cannot view anything with the -fpv argument. There appears to be an increasing amount of posts about this issue with know clear solution. Please let me know if you figure it out as I am stuck as well.

    #125030
    s.bosschaart
    Participant

    Hi all,

    The laptop is back from repair (had something to do with the battery)

    Here is the BoxLayout file
    https://www.dropbox.com/s/adh1mjte676vxal/BoxLayout.txt?dl=0

    I will be testing today with the V1 Kinect (adapter came in on last Friday)

    Hope to hear from you asap.

    Kind Regards,

    Sebastiaan

    #125031
    ajy00
    Participant

    Co-ords look backwards…

    Try:
    (-0.00823802, -0.0719482, -0.997374), -95
    ( -53.2262, -29.5305, -100.415)
    ( 44.401, -29.9039, -101.388)
    ( -52.5564, 42.5854, -95.7206)
    ( 47.0911, 42.1415, -95.6487)

    or alternatively (as I’m not sure about the first line positioning)
    ( -0.0719482, -0.00823802, -0.997374), -95
    ( -53.2262, -29.5305, -100.415)
    ( 44.401, -29.9039, -101.388)
    ( -52.5564, 42.5854, -95.7206)
    ( 47.0911, 42.1415, -95.6487)

    #125032
    s.bosschaart
    Participant

    Sadly both of these combinations dont seem to be working..
    Just getting a black screen 🙁
    when i remove the “-” that’s in front of the 95, i get spikes for a second, and then they fade away

    #125033
    s.bosschaart
    Participant
    #125034
    ajy00
    Participant

    I haven’t got the sandbox here set up at the moment so can’t give you a comparison image, however the “-95” value you talk about should be the distance of the base of the sandbox below the kinect … viz 95cm below the kinect. Your image looks like the kinect is possibly higher than that? I’d expect the box to fill most of the kinect field of view.
    When you did the setup, did you use a board over the top of the sandbox and then adjust by the depth of the box as described in the instruction text? (easy to miss the ‘add 10+cm value’ bit!)

    Optionally, if the kinect isn’t fixed in place, try raising/lowering when you are running the program to see if that makes a difference to the image

    #125037
    ajy00
    Participant

    Just noted that you’ve changed from a Kinect V2 to V1 … you’d need to have completely reconfigured for that too 🙂

    #125040
    s.bosschaart
    Participant

    The V1 doesnt seem to be recognized at all, in windows and ubuntu, so we will be switching back to the V2.
    Today i will be recalibrating all positions of the BoxLayout.
    I will be filming the process (in ubuntu that is) of how i am calibrating the sandbox

    #125042
    ajy00
    Participant

    If you are using ubuntu rather than Mint(mate) and a V2, I can’t emulate your issue … might be worth picking up on this thread which also had a V2 problem https://arsandbox.ucdavis.edu/forums/topic/fpv-in-startup-command-not-working/#post-125036.
    as a thought… you say your v1 isn’t recognised in windows either … are you running in a virtual environment?? if so then the sandbox will not work as it needs direct access to the gpu

    #125043
    s.bosschaart
    Participant

    If you say ubuntu might be the problem, i will gladly switch over to mint mate.
    Does it has to be version mentioned in the guide?

    I am not running in a virtual env. but i am however running on a laptop. (Asus TUF Gaming FX504GM)

    i thought the different version of linux shouldn’t be a problem.

    The link u posted told that the V2 is the problem here?
    We’ll need to see if our V1 is working on the xbox then.
    if not we need to order a new one..

    #125044
    ajy00
    Participant

    I’m running with Mint 19.3 (Mate). I’ve had no issues other than an initial frustration with power management/screensaver which insisted on blanking the screens every 10 minutes (resolved by deleting and reloading mint screensaver and setting everything to never!).
    Mint 20 seems to have caused some issues reading elsewhere in the forum, so best avoided for now.

    On the hardware, I’m no GPU expert, but the preference is for NVIDIA … again you’ll need to read elsewhere in the forum for guidance if yours is not.

    #125050
    Sean Robinson
    Participant

    The BoxLayout.txt file shown above looks very suspicious to me. I expect the Z coordinate to be positive. I’ve only used v1 Kinects (so maybe v2 have a different coord system?) and my calibration values have always been close to

    (X, Y, Z), offset
    (0.0, 0.0, 1.0), -100.0

    X and Y may be positive or negative, but will be very small. Z will be positive and close to 1.0. The offset is the distance, in cm, from the camera to the sandbox surface (with more negative meaning further away). As an example:

    (-0.0076185, 0.0271708, 0.99960), -98.0000

    is for the Kinect v1 on my desk, pointing at a convenient wall, for development.

Viewing 15 posts - 1 through 15 (of 15 total)
  • You must be logged in to reply to this topic.

Comments are closed.